| Message ID | 1310554762-10743-1-git-send-email-j.weitzel@phytec.de (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hello. On 13-07-2011 14:59, Jan Weitzel wrote: > vusim is not used. > Signed-off-by: Jan Weitzel<j.weitzel@phytec.de> > --- > arch/arm/mach-omap2/board-omap4pcm049.c | 16 +--------------- > 1 files changed, 1 insertions(+), 15 deletions(-) > diff --git a/arch/arm/mach-omap2/board-omap4pcm049.c b/arch/arm/mach-omap2/board-omap4pcm049.c > index ad8cb46..85193ec 100644 > --- a/arch/arm/mach-omap2/board-omap4pcm049.c > +++ b/arch/arm/mach-omap2/board-omap4pcm049.c [...] > @@ -318,9 +306,7 @@ static struct i2c_board_info __initdata pcm049_i2c_4_boardinfo[] = { > } > }; > > -static struct twl4030_platform_data pcm049_twldata = { > - .vusim =&pcm049_vusim, > -}; > +static struct twl4030_platform_data pcm049_twldatai; Have you added that 'i' at the end intentionally? WBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov: > > Have you added that 'i' at the end intentionally? > Thank you. It was a tribute to vim. Jan -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
* Jan Weitzel <J.Weitzel@phytec.de> [110713 05:51]: > Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov: > > > > > Have you added that 'i' at the end intentionally? > > > Thank you. It was a tribute to vim. :i) I'll fold the fixed patch into your original patch. Will also keep the new board files in testing-board because of the code coalescing and device tree conversion effort. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am Donnerstag, den 14.07.2011, 00:34 -0700 schrieb Tony Lindgren: > * Jan Weitzel <J.Weitzel@phytec.de> [110713 05:51]: > > Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov: > > > > > > > > Have you added that 'i' at the end intentionally? > > > > > Thank you. It was a tribute to vim. > > :i) > > I'll fold the fixed patch into your original patch. Will also > keep the new board files in testing-board because of the code > coalescing and device tree conversion effort. So there is no way to get the board mainline yet? Jan > Tony > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
* Jan Weitzel <J.Weitzel@phytec.de> [110714 01:34]: > Am Donnerstag, den 14.07.2011, 00:34 -0700 schrieb Tony Lindgren: > > * Jan Weitzel <J.Weitzel@phytec.de> [110713 05:51]: > > > Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov: > > > > > > > > > > > Have you added that 'i' at the end intentionally? > > > > > > > Thank you. It was a tribute to vim. > > > > :i) > > > > I'll fold the fixed patch into your original patch. Will also > > keep the new board files in testing-board because of the code > > coalescing and device tree conversion effort. > > So there is no way to get the board mainline yet? Well we can add it even before device tree support if it makes sense from code coalescing point of view. In this case it would mean creating board-panda-common.c or similar so the code can be shared amongst the panda variants. It seems that some GPIO pins are different and there are some difference in devices connected, but big parts of the code can be shared. Adding the pending boards without combining code would be adding code that will be going away for most part with the device tree support. And most likely the beagle and panda based boards will be the first ones to work with device tree. So anything we can do to have common board init code will also help with this effort. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi, On Fri, Jul 15, 2011 at 12:50:24AM -0700, Tony Lindgren wrote: > * Jan Weitzel <J.Weitzel@phytec.de> [110714 01:34]: > > Am Donnerstag, den 14.07.2011, 00:34 -0700 schrieb Tony Lindgren: > > > * Jan Weitzel <J.Weitzel@phytec.de> [110713 05:51]: > > > > Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov: > > > > > > > > > > > > > > Have you added that 'i' at the end intentionally? > > > > > > > > > Thank you. It was a tribute to vim. > > > > > > :i) > > > > > > I'll fold the fixed patch into your original patch. Will also > > > keep the new board files in testing-board because of the code > > > coalescing and device tree conversion effort. > > > > So there is no way to get the board mainline yet? > > Well we can add it even before device tree support if it makes > sense from code coalescing point of view. In this case it would > mean creating board-panda-common.c or similar so the code can > be shared amongst the panda variants. > > It seems that some GPIO pins are different and there are some > difference in devices connected, but big parts of the code can be > shared. isn't it easier than to just add a few if (machine_is_xxxx()) checks and another MACHINE_START() to board-omap4panda.c rather than creating a new file, shuffling code around and then adding a new board file ??
* Felipe Balbi <balbi@ti.com> [110715 00:53]: > Hi, > > On Fri, Jul 15, 2011 at 12:50:24AM -0700, Tony Lindgren wrote: > > * Jan Weitzel <J.Weitzel@phytec.de> [110714 01:34]: > > > Am Donnerstag, den 14.07.2011, 00:34 -0700 schrieb Tony Lindgren: > > > > * Jan Weitzel <J.Weitzel@phytec.de> [110713 05:51]: > > > > > Am Mittwoch, den 13.07.2011, 16:13 +0400 schrieb Sergei Shtylyov: > > > > > > > > > > > > > > > > > Have you added that 'i' at the end intentionally? > > > > > > > > > > > Thank you. It was a tribute to vim. > > > > > > > > :i) > > > > > > > > I'll fold the fixed patch into your original patch. Will also > > > > keep the new board files in testing-board because of the code > > > > coalescing and device tree conversion effort. > > > > > > So there is no way to get the board mainline yet? > > > > Well we can add it even before device tree support if it makes > > sense from code coalescing point of view. In this case it would > > mean creating board-panda-common.c or similar so the code can > > be shared amongst the panda variants. > > > > It seems that some GPIO pins are different and there are some > > difference in devices connected, but big parts of the code can be > > shared. > > isn't it easier than to just add a few if (machine_is_xxxx()) checks and > another MACHINE_START() to board-omap4panda.c rather than creating a new > file, shuffling code around and then adding a new board file ?? That works too if the init_machine does not get too complicated. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am Freitag, den 15.07.2011, 00:50 -0700 schrieb Tony Lindgren: > Well we can add it even before device tree support if it makes > sense from code coalescing point of view. In this case it would > mean creating board-panda-common.c or similar so the code can > be shared amongst the panda variants. > > It seems that some GPIO pins are different and there are some > difference in devices connected, but big parts of the code can be > shared. > > Adding the pending boards without combining code would be adding code > that will be going away for most part with the device tree support. > > And most likely the beagle and panda based boards will be the first > ones to work with device tree. So anything we can do to have common > board init code will also help with this effort. > > Regards, > > Tony pcm049 and panda board have some more different devices. I am working on patches to add NAND support and using tlv320aic3x audio codec which need regulators in platformcode. I need a hack to controll usb otg by gpio (controlling a external power circuit). The patches are not mainline ready by now. If using machine_is_xxxx() in board-omap4panda.c then also is good way, I could provide our board as patches on top of board-omap4panda.c. When will pandaboard use device tree to boot? Kind Regards, Jan -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
* Jan Weitzel <J.Weitzel@phytec.de> [110715 02:42]: > Am Freitag, den 15.07.2011, 00:50 -0700 schrieb Tony Lindgren: > > Well we can add it even before device tree support if it makes > > sense from code coalescing point of view. In this case it would > > mean creating board-panda-common.c or similar so the code can > > be shared amongst the panda variants. > > > > It seems that some GPIO pins are different and there are some > > difference in devices connected, but big parts of the code can be > > shared. > > > > Adding the pending boards without combining code would be adding code > > that will be going away for most part with the device tree support. > > > > And most likely the beagle and panda based boards will be the first > > ones to work with device tree. So anything we can do to have common > > board init code will also help with this effort. > > > > Regards, > > > > Tony > pcm049 and panda board have some more different devices. > I am working on patches to add NAND support and using tlv320aic3x audio > codec which need regulators in platformcode. I need a hack to controll > usb otg by gpio (controlling a external power circuit). The patches are > not mainline ready by now. OK, let's figure out how we can add the basic support first then. > If using machine_is_xxxx() in board-omap4panda.c then also is good way, > I could provide our board as patches on top of board-omap4panda.c. > When will pandaboard use device tree to boot? Yes, but it would better just to use separate .init_machine entries to initialize thing. Gpio entries can be initialized along the lines of the recent beagle commit 5fe8b4c19dc24e3bb873daf9e96a2439a83bbd79 that adds support for beagl xm board. Except you already have a separate machine_id, so no runtime detection is needed. That avoids adding the machine_is entries all over the place that tend to cause problems when some other panda variant is added as it requires patching in multiple places. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
First try to join both boards. Only compile testet. basis for discusson Jan Weitzel (2): omap4: board-omap4panda: prepare for join omap4: board-omap4panda: join Phytec phyCORE-OMAP4 arch/arm/mach-omap2/Kconfig | 6 + arch/arm/mach-omap2/board-omap4panda.c | 817 +++++++++++++++++++------- arch/arm/plat-omap/include/plat/uncompress.h | 1 + 3 files changed, 616 insertions(+), 208 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
* Jan Weitzel <j.weitzel@phytec.de> [110715 09:01]: > First try to join both boards. Only compile testet. > basis for discusson > > Jan Weitzel (2): > omap4: board-omap4panda: prepare for join > omap4: board-omap4panda: join Phytec phyCORE-OMAP4 > > arch/arm/mach-omap2/Kconfig | 6 + > arch/arm/mach-omap2/board-omap4panda.c | 817 +++++++++++++++++++------- > arch/arm/plat-omap/include/plat/uncompress.h | 1 + > 3 files changed, 616 insertions(+), 208 deletions(-) Thanks for working on this. To me it seems that it might be more readable to have board-panda-common.c file instead of having everything in one file. Then from the board specific files you could just call panda_common_init(&omap4_panda_config). Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Try to join both boards. Only compile testet. basis for discusson Jan Weitzel (2): omap4: board-omap4panda: prepare for join omap4: board-omap4pcm049: add Phytec phyCORE-OMAP4 arch/arm/mach-omap2/Kconfig | 6 + arch/arm/mach-omap2/Makefile | 5 + arch/arm/mach-omap2/board-omap4panda-common.c | 380 ++++++++++++++++++++++ arch/arm/mach-omap2/board-omap4panda-common.h | 39 +++ arch/arm/mach-omap2/board-omap4panda.c | 421 +++++-------------------- arch/arm/mach-omap2/board-omap4pcm049.c | 368 +++++++++++++++++++++ arch/arm/plat-omap/include/plat/uncompress.h | 1 + 7 files changed, 875 insertions(+), 345 deletions(-) create mode 100644 arch/arm/mach-omap2/board-omap4panda-common.c create mode 100644 arch/arm/mach-omap2/board-omap4panda-common.h create mode 100644 arch/arm/mach-omap2/board-omap4pcm049.c -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/arch/arm/mach-omap2/board-omap4pcm049.c b/arch/arm/mach-omap2/board-omap4pcm049.c index ad8cb46..85193ec 100644 --- a/arch/arm/mach-omap2/board-omap4pcm049.c +++ b/arch/arm/mach-omap2/board-omap4pcm049.c @@ -227,18 +227,6 @@ static struct platform_device pcm049_vcc_3v3_device = { }, }; -static struct regulator_init_data pcm049_vusim = { - .constraints = { - .min_uV = 1800000, - .max_uV = 3300000, - .apply_uV = true, - .valid_modes_mask = REGULATOR_MODE_NORMAL - | REGULATOR_MODE_STANDBY, - .valid_ops_mask = REGULATOR_CHANGE_MODE - | REGULATOR_CHANGE_STATUS, - }, -}; - static struct at24_platform_data board_eeprom = { .byte_len = 4096, .page_size = 32, @@ -318,9 +306,7 @@ static struct i2c_board_info __initdata pcm049_i2c_4_boardinfo[] = { } }; -static struct twl4030_platform_data pcm049_twldata = { - .vusim = &pcm049_vusim, -}; +static struct twl4030_platform_data pcm049_twldatai; static int __init pcm049_i2c_init(void) {
vusim is not used. Signed-off-by: Jan Weitzel <j.weitzel@phytec.de> --- arch/arm/mach-omap2/board-omap4pcm049.c | 16 +--------------- 1 files changed, 1 insertions(+), 15 deletions(-)