ARM: OMAP: add corrected DSS regulator supplies
Subsystems (3)
cover ARM: OMAP: add corrected DSS regulator supplies
Hi Tony,
Here are a few patches adding corrected DSS regulator supplies. The current ones in the board files are not really correct, although the dss driver works ok with them.
So these patches add new regulator supply entries. When these are merged, I'll change omapdss driver to use the new ones, instead of the old ones. After that, we can remove the old ones from the board files.
Note that these patches were also present in the big DSS series I sent yesterday. There's no reason for these patches to be there, so I'm sending them separately, and will drop these from my DSS series.
Tomi
Tomi Valkeinen (3):
ARM: OMAP: fix dsi regulator names
ARM: OMAP: add vdds_dsi supply for omapdss_dpi.0
ARM: OMAP: add vdds_sdi supply for omapdss_sdi.0
arch/arm/mach-omap2/board-cm-t35.c | 3 ++- arch/arm/mach-omap2/board-devkit8000.c | 1 + arch/arm/mach-omap2/board-ldp.c | 3 ++- arch/arm/mach-omap2/board-omap3pandora.c | 1 + arch/arm/mach-omap2/board-rx51-peripherals.c | 1 + arch/arm/mach-omap2/twl-common.c | 1 + 6 files changed, 8 insertions(+), 2 deletions(-)
Signature · 1 line
1.8.1.2
PATCH 1/3 ARM: OMAP: fix dsi regulator names
board-cm-t35.c and board-ldp.c contain regulator supply entries for vdds_dsi. However, the given device name is wrong.
This patch fixes the device name from omapdss_dsi1 to omapdss_dsi.0.
Note that as far as I know, DSI driver is not used on these boards, so this should not have caused any problems. The DSI block can be used to generate clock for DPI, though, but that's not enabled for omap3 boards currently.
--- arch/arm/mach-omap2/board-cm-t35.c | 2 +- arch/arm/mach-omap2/board-ldp.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
arch/arm/mach-omap2/board-cm-t35.c +1 -1
@@ -293,7 +293,7 @@ static struct regulator_consumer_supply cm_t35_vsim_supply[] = {static struct regulator_consumer_supply cm_t35_vio_supplies[] = {REGULATOR_SUPPLY ("vcc" ,"spi1.0" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), -REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi1" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), };/* VMMC1 for MMC1 pins CMD, CLK, DAT0..DAT3 (20 mA, plus card == max 220 mA) */
arch/arm/mach-omap2/board-ldp.c +1 -1
@@ -272,7 +272,7 @@ static struct regulator_init_data ldp_vaux1 = {static struct regulator_consumer_supply ldp_vpll2_supplies[] = {REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), -REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi1" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), };static struct regulator_init_data ldp_vpll2 = {
Signature · 1 line
1.8.1.2
PATCH 2/3 ARM: OMAP: add vdds_dsi supply for omapdss_dpi.0
In reply to Tomi ValkeinenDPI driver gets currently the vdds_dsi regulator via omapdss device. This is not correct, and we'll change the DPI driver to get the regulator directly via omapdss_dpi.0 device.
This patch changes the relevant board files to add vdds_dsi supply for omapdss_dpi.0 device.
Note that the vdds_dsi supply for omapdss device is still left there, as the current display driver uses it. When both the board files and the display driver has been changed, we can remove the unused supply.
--- arch/arm/mach-omap2/board-cm-t35.c | 1 + arch/arm/mach-omap2/board-devkit8000.c | 1 + arch/arm/mach-omap2/board-ldp.c | 1 + arch/arm/mach-omap2/board-omap3pandora.c | 1 + arch/arm/mach-omap2/twl-common.c | 1 + 5 files changed, 5 insertions(+)
arch/arm/mach-omap2/board-cm-t35.c +1 -0
@@ -293,6 +293,7 @@ static struct regulator_consumer_supply cm_t35_vsim_supply[] = {static struct regulator_consumer_supply cm_t35_vio_supplies[] = {REGULATOR_SUPPLY ("vcc" ,"spi1.0" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dpi.0" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), };
arch/arm/mach-omap2/board-devkit8000.c +1 -0
@@ -222,6 +222,7 @@ static struct twl4030_gpio_platform_data devkit8000_gpio_data = {static struct regulator_consumer_supply devkit8000_vpll1_supplies[] = {REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dpi.0" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), };
arch/arm/mach-omap2/board-ldp.c +1 -0
@@ -272,6 +272,7 @@ static struct regulator_init_data ldp_vaux1 = {static struct regulator_consumer_supply ldp_vpll2_supplies[] = {REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dpi.0" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), };
arch/arm/mach-omap2/board-omap3pandora.c +1 -0
@@ -343,6 +343,7 @@ static struct regulator_consumer_supply pandora_vmmc3_supply[] = {static struct regulator_consumer_supply pandora_vdds_supplies[] = {REGULATOR_SUPPLY ("vdds_sdi" ,"omapdss" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dpi.0" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), };
arch/arm/mach-omap2/twl-common.c +1 -0
@@ -140,6 +140,7 @@ static struct regulator_init_data omap3_vdac_idata = {static struct regulator_consumer_supply omap3_vpll2_supplies[] = {REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dpi.0" ),REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), };
Signature · 1 line
1.8.1.2
PATCH 3/3 ARM: OMAP: add vdds_sdi supply for omapdss_sdi.0
In reply to Tomi ValkeinenSDI driver gets currently the vdds_sdi regulator via omapdss device. This is not correct, and we'll change the SDI driver to get the regulator directly via omapdss_sdi.0 device.
This patch changes the rx51 board file to add vdds_dsi supply for omapdss_sdi.0 device.
Note that the vdds_sdi supply for omapdss device is still left there, as the current display driver uses it. When both the board files and the display driver has been changed, we can remove the unused supply.
--- arch/arm/mach-omap2/board-rx51-peripherals.c | 1 + 1 file changed, 1 insertion(+)
arch/arm/mach-omap2/board-rx51-peripherals.c +1 -0
@@ -553,6 +553,7 @@ static struct regulator_consumer_supply rx51_vio_supplies[] = {static struct regulator_consumer_supply rx51_vaux1_consumers[] = {REGULATOR_SUPPLY ("vdds_sdi" ,"omapdss" ), +REGULATOR_SUPPLY ("vdds_sdi" ,"omapdss_sdi.0" ),/* Si4713 supply */ REGULATOR_SUPPLY ("vdd" ,"2-0063" ),/* lis3lv02d */
Signature · 1 line
1.8.1.2
cover ARM: OMAP: add corrected DSS regulator supplies
In reply to Tomi ValkeinenQuoted 6 lines · Tomi Valkeinen
Hi Tony,
Here are a few patches adding corrected DSS regulator supplies. The current ones in the board files are not really correct, although the dss driver works ok with them.
Quoted 7 lines
So these patches add new regulator supply entries. When these are merged, I'll change omapdss driver to use the new ones, instead of the old ones. After that, we can remove the old ones from the board files.
Note that these patches were also present in the big DSS series I sent yesterday. There's no reason for these patches to be there, so I'm sending them separately, and will drop these from my DSS series.
Ping.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130612/9d11bedf/attachment.sig>
Tony Lindgren
maintainercover ARM: OMAP: add corrected DSS regulator supplies
Quoted 11 lines · Tomi Valkeinen
Quoted 10 lines · Tomi Valkeinen
Hi Tony,
Here are a few patches adding corrected DSS regulator supplies. The current ones in the board files are not really correct, although the dss driver works ok with them.
So these patches add new regulator supply entries. When these are merged, I'll change omapdss driver to use the new ones, instead of the old ones. After that, we can remove the old ones from the board files.
Quoted 5 lines
Quoted 3 lines
Note that these patches were also present in the big DSS series I sent yesterday. There's no reason for these patches to be there, so I'm sending them separately, and will drop these from my DSS series.
Ping.
Thanks, applying into omap-for-v.311/fixes-non-critical.
Regards,
Tony