Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-30 Thread Tony Lindgren 
* Heiko Schocher  [151117 00:25]:
> --- /dev/null
> +++ b/arch/arm/boot/dts/am335x-shc.dts
> + {
> + compatible = "ti,tps65217";
> + ti,pmic-shutdown-controller;
> +
> + regulators {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + dcdc1_reg: regulator@0 {
> + reg = <0>;
> + regulator-name = "vdds_dpr";
> + regulator-compatible = "dcdc1";
> + regulator-min-microvolt = <130>;
> + regulator-max-microvolt = <145>;
> + regulator-boot-on;
> + regulator-always-on;
> + };
> +
> + dcdc2_reg: regulator@1 {
> + reg = <1>;
> + /*
> +  * VDD_MPU voltage limits 0.95V - 1.26V with
> +  * +/-4% tolerance
> +  */
> + regulator-compatible = "dcdc2";
> + regulator-name = "vdd_mpu";
> + regulator-min-microvolt = <925000>;
> + regulator-max-microvolt = <1375000>;
> + regulator-boot-on;
> + regulator-always-on;
> + regulator-ramp-delay = <7>;
> + };
> +
> + dcdc3_reg: regulator@2 {
> + reg = <2>;
> + /*
> +  * VDD_CORE voltage limits 0.95V - 1.1V with
> +  * +/-4% tolerance
> +  */
> + regulator-name = "vdd_core";
> + regulator-compatible = "dcdc3";
> + regulator-min-microvolt = <925000>;
> + regulator-max-microvolt = <1125000>;
> + regulator-boot-on;
> + regulator-always-on;
> + };
> +
> + ldo1_reg: regulator@3 {
> + reg = <3>;
> + regulator-name = "vio,vrtc,vdds";
> + regulator-compatible = "ldo1";
> + regulator-min-microvolt = <100>;
> + regulator-max-microvolt = <180>;
> + regulator-always-on;
> + };
> +
> + ldo2_reg: regulator@4 {
> + reg = <4>;
> + regulator-name = "vdd_3v3aux";
> + regulator-compatible = "ldo2";
> + regulator-min-microvolt = <90>;
> + regulator-max-microvolt = <330>;
> + regulator-always-on;
> + };
> +
> + ldo3_reg: regulator@5 {
> + reg = <5>;
> + regulator-name = "vdd_1v8";
> + regulator-compatible = "ldo3";
> + regulator-min-microvolt = <90>;
> + regulator-max-microvolt = <180>;
> + regulator-always-on;
> + };
> +
> + ldo4_reg: regulator@6 {
> + reg = <6>;
> + regulator-name = "vdd_3v3a";
> + regulator-compatible = "ldo4";
> + regulator-min-microvolt = <180>;
> + regulator-max-microvolt = <330>;
> + regulator-always-on;
> + };
> + };
> +};

Applying this into omap-for-v4.5/dt.. But I'm getting concerned about this
"regulator-always-on" stuff and having multiple copies of the same thing.

I think we should have a common am33xx-tps65217.dtsi file that has the
regulators defined at one place and other then include it. And they are
controllable AFAIK..

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-30 Thread Tony Lindgren 
* Heiko Schocher  [151129 22:51]:
> Hello all,
> 
> Am 18.11.2015 um 09:24 schrieb Heiko Schocher:
> >Hello Dave,
> >
> >Am 17.11.2015 um 22:29 schrieb Dave Gerlach:
> >>Hi,
> >>On 11/17/2015 02:24 AM, Heiko Schocher wrote:
> >>>add support for the am335x based shc board.
> >>>
> >>>UART: 0-2 and 4
> >>>DRAM: 512 MiB
> >>>MMC:  OMAP SD/MMC: 0 @ 26 MHz
> >>>   OMAP SD/MMC: 1 @ 26 MHz
> >>>I2C:  at24 eeprom, pcf8563
> >>>USB:  USB1 (host)
> >>>
> >>>Signed-off-by: Heiko Schocher 
> >>>---
> >>>The following patches are needed to get all working
> >>>for the shc board:
> >>>- disable clkout on pcf8563
> >>>   accepted.
> >>>   http://www.spinics.net/lists/devicetree/msg98542.html
> >>>
> >>>- leds: leds-gpio: add shutdown function
> >>>   accepted.
> >>>   https://lkml.org/lkml/2015/10/13/169
> >>>
> >>>- net: phy: smsc: disable energy detect mode
> >>>   accepted
> >>>   [PATCH v2 2/2] net: phy: smsc: disable energy detect mode
> >>>   https://lkml.org/lkml/2015/10/17/2
> >>>   [PATCH v2 1/2] drivers: net: cpsw: add phy-handle parsing
> >>>   https://lkml.org/lkml/2015/10/17/4
> >>>
> >>>- ARM: OMAP2+: omap_hwmod: Introduce ti,no-init dt property
> >>>   
> >>> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/328204.html
> >>>   @Dave: What is the current state of this patch?
> >>>   I have the same problem here on this am335x based board
> >>>
> >>
> >>A different approach is being taken for resolving the issue of rtc hwmod on 
> >>am43x epos evm [1],
> >>which is what I was attempting to solve with the patch you have linked. We 
> >>decided to avoid changing
> >>omap_hwmod code and I haven't been pursuing the ti,no-init flag anymore.
> >
> >Maybe I overlook something, but I cannot see, how [1] solves the RTC
> >hwmod problem on am335x SoC based boards. Not all boards have this problem,
> >so the RTC hwmod cannot be disabled for all am335x boards ...
> >
> >It must be somehow configurable for boards ... I have am335x boards
> >which use the rtc from the SoC
> 
> gentle ping ...
> 
> No more comments on this patch? Is it Ok for mainline or are
> there more issues?

Looks OK to me, hoping to start applying the dts changes for v4.5 this
week.

Tony

> >>[1] http://www.spinics.net/lists/linux-omap/msg121987.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-30 Thread Heiko Schocher 

Hello Tony,

Am 30.11.2015 um 22:41 schrieb Tony Lindgren:

* Heiko Schocher  [151117 00:25]:

--- /dev/null
+++ b/arch/arm/boot/dts/am335x-shc.dts
+ {
+   compatible = "ti,tps65217";
+   ti,pmic-shutdown-controller;
+
+   regulators {
+   #address-cells = <1>;
+   #size-cells = <0>;
+
+   dcdc1_reg: regulator@0 {
+   reg = <0>;
+   regulator-name = "vdds_dpr";
+   regulator-compatible = "dcdc1";
+   regulator-min-microvolt = <130>;
+   regulator-max-microvolt = <145>;
+   regulator-boot-on;
+   regulator-always-on;
+   };
+
+   dcdc2_reg: regulator@1 {
+   reg = <1>;
+   /*
+* VDD_MPU voltage limits 0.95V - 1.26V with
+* +/-4% tolerance
+*/
+   regulator-compatible = "dcdc2";
+   regulator-name = "vdd_mpu";
+   regulator-min-microvolt = <925000>;
+   regulator-max-microvolt = <1375000>;
+   regulator-boot-on;
+   regulator-always-on;
+   regulator-ramp-delay = <7>;
+   };
+
+   dcdc3_reg: regulator@2 {
+   reg = <2>;
+   /*
+* VDD_CORE voltage limits 0.95V - 1.1V with
+* +/-4% tolerance
+*/
+   regulator-name = "vdd_core";
+   regulator-compatible = "dcdc3";
+   regulator-min-microvolt = <925000>;
+   regulator-max-microvolt = <1125000>;
+   regulator-boot-on;
+   regulator-always-on;
+   };
+
+   ldo1_reg: regulator@3 {
+   reg = <3>;
+   regulator-name = "vio,vrtc,vdds";
+   regulator-compatible = "ldo1";
+   regulator-min-microvolt = <100>;
+   regulator-max-microvolt = <180>;
+   regulator-always-on;
+   };
+
+   ldo2_reg: regulator@4 {
+   reg = <4>;
+   regulator-name = "vdd_3v3aux";
+   regulator-compatible = "ldo2";
+   regulator-min-microvolt = <90>;
+   regulator-max-microvolt = <330>;
+   regulator-always-on;
+   };
+
+   ldo3_reg: regulator@5 {
+   reg = <5>;
+   regulator-name = "vdd_1v8";
+   regulator-compatible = "ldo3";
+   regulator-min-microvolt = <90>;
+   regulator-max-microvolt = <180>;
+   regulator-always-on;
+   };
+
+   ldo4_reg: regulator@6 {
+   reg = <6>;
+   regulator-name = "vdd_3v3a";
+   regulator-compatible = "ldo4";
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <330>;
+   regulator-always-on;
+   };
+   };
+};


Applying this into omap-for-v4.5/dt.. But I'm getting concerned about this
"regulator-always-on" stuff and having multiple copies of the same thing.

I think we should have a common am33xx-tps65217.dtsi file that has the
regulators defined at one place and other then include it. And they are
controllable AFAIK..


Hmm... Mark Brown (added to Cc) suggested to move this regulator nodes
into the board DT file and remove such files [1].

bye,
Heiko

[1] https://lkml.org/lkml/2015/10/21/581
--
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-30 Thread Tony Lindgren 
* Heiko Schocher  [151130 21:21]:
> Hello Tony,
> 
> Am 30.11.2015 um 22:41 schrieb Tony Lindgren:
> >* Heiko Schocher  [151117 00:25]:
> >>--- /dev/null
> >>+++ b/arch/arm/boot/dts/am335x-shc.dts
> >>+ {
> >>+   compatible = "ti,tps65217";
> >>+   ti,pmic-shutdown-controller;
> >>+
> >>+   regulators {
> >>+   #address-cells = <1>;
> >>+   #size-cells = <0>;
> >>+
> >>+   dcdc1_reg: regulator@0 {
> >>+   reg = <0>;
> >>+   regulator-name = "vdds_dpr";
> >>+   regulator-compatible = "dcdc1";
> >>+   regulator-min-microvolt = <130>;
> >>+   regulator-max-microvolt = <145>;
> >>+   regulator-boot-on;
> >>+   regulator-always-on;
> >>+   };
> >>+
> >>+   dcdc2_reg: regulator@1 {
> >>+   reg = <1>;
> >>+   /*
> >>+* VDD_MPU voltage limits 0.95V - 1.26V with
> >>+* +/-4% tolerance
> >>+*/
> >>+   regulator-compatible = "dcdc2";
> >>+   regulator-name = "vdd_mpu";
> >>+   regulator-min-microvolt = <925000>;
> >>+   regulator-max-microvolt = <1375000>;
> >>+   regulator-boot-on;
> >>+   regulator-always-on;
> >>+   regulator-ramp-delay = <7>;
> >>+   };
> >>+
> >>+   dcdc3_reg: regulator@2 {
> >>+   reg = <2>;
> >>+   /*
> >>+* VDD_CORE voltage limits 0.95V - 1.1V with
> >>+* +/-4% tolerance
> >>+*/
> >>+   regulator-name = "vdd_core";
> >>+   regulator-compatible = "dcdc3";
> >>+   regulator-min-microvolt = <925000>;
> >>+   regulator-max-microvolt = <1125000>;
> >>+   regulator-boot-on;
> >>+   regulator-always-on;
> >>+   };
> >>+
> >>+   ldo1_reg: regulator@3 {
> >>+   reg = <3>;
> >>+   regulator-name = "vio,vrtc,vdds";
> >>+   regulator-compatible = "ldo1";
> >>+   regulator-min-microvolt = <100>;
> >>+   regulator-max-microvolt = <180>;
> >>+   regulator-always-on;
> >>+   };
> >>+
> >>+   ldo2_reg: regulator@4 {
> >>+   reg = <4>;
> >>+   regulator-name = "vdd_3v3aux";
> >>+   regulator-compatible = "ldo2";
> >>+   regulator-min-microvolt = <90>;
> >>+   regulator-max-microvolt = <330>;
> >>+   regulator-always-on;
> >>+   };
> >>+
> >>+   ldo3_reg: regulator@5 {
> >>+   reg = <5>;
> >>+   regulator-name = "vdd_1v8";
> >>+   regulator-compatible = "ldo3";
> >>+   regulator-min-microvolt = <90>;
> >>+   regulator-max-microvolt = <180>;
> >>+   regulator-always-on;
> >>+   };
> >>+
> >>+   ldo4_reg: regulator@6 {
> >>+   reg = <6>;
> >>+   regulator-name = "vdd_3v3a";
> >>+   regulator-compatible = "ldo4";
> >>+   regulator-min-microvolt = <180>;
> >>+   regulator-max-microvolt = <330>;
> >>+   regulator-always-on;
> >>+   };
> >>+   };
> >>+};
> >
> >Applying this into omap-for-v4.5/dt.. But I'm getting concerned about this
> >"regulator-always-on" stuff and having multiple copies of the same thing.
> >
> >I think we should have a common am33xx-tps65217.dtsi file that has the
> >regulators defined at one place and other then include it. And they are
> >controllable AFAIK..
> 
> Hmm... Mark Brown (added to Cc) suggested to move this regulator nodes
> into the board DT file and remove such files [1].

Hmm it was probably the name of that file causing confusion as it was not
am33xx specific. If we have many board variants using almost the same exact
regulators and configuration it totally makes sense to have a shared dtsi
file for them :)

It may actually be better to have it as am33xx-common.dtsi and I bet that
covers quite a few am33xx boards for the basic shared functionality.

Regards,

Tony


> [1] https://lkml.org/lkml/2015/10/21/581

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-30 Thread Heiko Schocher 

Hello Tony,

Am 01.12.2015 um 06:53 schrieb Tony Lindgren:

* Heiko Schocher  [151130 21:21]:

Hello Tony,

Am 30.11.2015 um 22:41 schrieb Tony Lindgren:

* Heiko Schocher  [151117 00:25]:

--- /dev/null
+++ b/arch/arm/boot/dts/am335x-shc.dts
+ {
+   compatible = "ti,tps65217";
+   ti,pmic-shutdown-controller;
+
+   regulators {
+   #address-cells = <1>;
+   #size-cells = <0>;
+
+   dcdc1_reg: regulator@0 {
+   reg = <0>;
+   regulator-name = "vdds_dpr";
+   regulator-compatible = "dcdc1";
+   regulator-min-microvolt = <130>;
+   regulator-max-microvolt = <145>;
+   regulator-boot-on;
+   regulator-always-on;
+   };
+
+   dcdc2_reg: regulator@1 {
+   reg = <1>;
+   /*
+* VDD_MPU voltage limits 0.95V - 1.26V with
+* +/-4% tolerance
+*/
+   regulator-compatible = "dcdc2";
+   regulator-name = "vdd_mpu";
+   regulator-min-microvolt = <925000>;
+   regulator-max-microvolt = <1375000>;
+   regulator-boot-on;
+   regulator-always-on;
+   regulator-ramp-delay = <7>;
+   };
+
+   dcdc3_reg: regulator@2 {
+   reg = <2>;
+   /*
+* VDD_CORE voltage limits 0.95V - 1.1V with
+* +/-4% tolerance
+*/
+   regulator-name = "vdd_core";
+   regulator-compatible = "dcdc3";
+   regulator-min-microvolt = <925000>;
+   regulator-max-microvolt = <1125000>;
+   regulator-boot-on;
+   regulator-always-on;
+   };
+
+   ldo1_reg: regulator@3 {
+   reg = <3>;
+   regulator-name = "vio,vrtc,vdds";
+   regulator-compatible = "ldo1";
+   regulator-min-microvolt = <100>;
+   regulator-max-microvolt = <180>;
+   regulator-always-on;
+   };
+
+   ldo2_reg: regulator@4 {
+   reg = <4>;
+   regulator-name = "vdd_3v3aux";
+   regulator-compatible = "ldo2";
+   regulator-min-microvolt = <90>;
+   regulator-max-microvolt = <330>;
+   regulator-always-on;
+   };
+
+   ldo3_reg: regulator@5 {
+   reg = <5>;
+   regulator-name = "vdd_1v8";
+   regulator-compatible = "ldo3";
+   regulator-min-microvolt = <90>;
+   regulator-max-microvolt = <180>;
+   regulator-always-on;
+   };
+
+   ldo4_reg: regulator@6 {
+   reg = <6>;
+   regulator-name = "vdd_3v3a";
+   regulator-compatible = "ldo4";
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <330>;
+   regulator-always-on;
+   };
+   };
+};


Applying this into omap-for-v4.5/dt.. But I'm getting concerned about this
"regulator-always-on" stuff and having multiple copies of the same thing.

I think we should have a common am33xx-tps65217.dtsi file that has the
regulators defined at one place and other then include it. And they are
controllable AFAIK..


Hmm... Mark Brown (added to Cc) suggested to move this regulator nodes
into the board DT file and remove such files [1].


Hmm it was probably the name of that file causing confusion as it was not
am33xx specific. If we have many board variants using almost the same exact
regulators and configuration it totally makes sense to have a shared dtsi
file for them :)


Ack.


It may actually be better to have it as am33xx-common.dtsi and I bet that
covers quite a few am33xx boards for the basic shared functionality.


I try to find some time to make such a patch...

bye,
Heiko


Regards,

Tony



[1] https://lkml.org/lkml/2015/10/21/581




--
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-29 Thread Heiko Schocher 

Hello all,

Am 18.11.2015 um 09:24 schrieb Heiko Schocher:

Hello Dave,

Am 17.11.2015 um 22:29 schrieb Dave Gerlach:

Hi,
On 11/17/2015 02:24 AM, Heiko Schocher wrote:

add support for the am335x based shc board.

UART: 0-2 and 4
DRAM: 512 MiB
MMC:  OMAP SD/MMC: 0 @ 26 MHz
   OMAP SD/MMC: 1 @ 26 MHz
I2C:  at24 eeprom, pcf8563
USB:  USB1 (host)

Signed-off-by: Heiko Schocher 
---
The following patches are needed to get all working
for the shc board:
- disable clkout on pcf8563
   accepted.
   http://www.spinics.net/lists/devicetree/msg98542.html

- leds: leds-gpio: add shutdown function
   accepted.
   https://lkml.org/lkml/2015/10/13/169

- net: phy: smsc: disable energy detect mode
   accepted
   [PATCH v2 2/2] net: phy: smsc: disable energy detect mode
   https://lkml.org/lkml/2015/10/17/2
   [PATCH v2 1/2] drivers: net: cpsw: add phy-handle parsing
   https://lkml.org/lkml/2015/10/17/4

- ARM: OMAP2+: omap_hwmod: Introduce ti,no-init dt property
   http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/328204.html
   @Dave: What is the current state of this patch?
   I have the same problem here on this am335x based board



A different approach is being taken for resolving the issue of rtc hwmod on 
am43x epos evm [1],
which is what I was attempting to solve with the patch you have linked. We 
decided to avoid changing
omap_hwmod code and I haven't been pursuing the ti,no-init flag anymore.


Maybe I overlook something, but I cannot see, how [1] solves the RTC
hwmod problem on am335x SoC based boards. Not all boards have this problem,
so the RTC hwmod cannot be disabled for all am335x boards ...

It must be somehow configurable for boards ... I have am335x boards
which use the rtc from the SoC


gentle ping ...

No more comments on this patch? Is it Ok for mainline or are
there more issues?

bye,
Heiko



Regards,
Dave

[1] http://www.spinics.net/lists/linux-omap/msg121987.html


bye,
Heiko


--
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-18 Thread Heiko Schocher 

Hello Dave,

Am 17.11.2015 um 22:29 schrieb Dave Gerlach:

Hi,
On 11/17/2015 02:24 AM, Heiko Schocher wrote:

add support for the am335x based shc board.

UART: 0-2 and 4
DRAM: 512 MiB
MMC:  OMAP SD/MMC: 0 @ 26 MHz
   OMAP SD/MMC: 1 @ 26 MHz
I2C:  at24 eeprom, pcf8563
USB:  USB1 (host)

Signed-off-by: Heiko Schocher 
---
The following patches are needed to get all working
for the shc board:
- disable clkout on pcf8563
   accepted.
   http://www.spinics.net/lists/devicetree/msg98542.html

- leds: leds-gpio: add shutdown function
   accepted.
   https://lkml.org/lkml/2015/10/13/169

- net: phy: smsc: disable energy detect mode
   accepted
   [PATCH v2 2/2] net: phy: smsc: disable energy detect mode
   https://lkml.org/lkml/2015/10/17/2
   [PATCH v2 1/2] drivers: net: cpsw: add phy-handle parsing
   https://lkml.org/lkml/2015/10/17/4

- ARM: OMAP2+: omap_hwmod: Introduce ti,no-init dt property
   http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/328204.html
   @Dave: What is the current state of this patch?
   I have the same problem here on this am335x based board



A different approach is being taken for resolving the issue of rtc hwmod on 
am43x epos evm [1],
which is what I was attempting to solve with the patch you have linked. We 
decided to avoid changing
omap_hwmod code and I haven't been pursuing the ti,no-init flag anymore.


Maybe I overlook something, but I cannot see, how [1] solves the RTC
hwmod problem on am335x SoC based boards. Not all boards have this problem,
so the RTC hwmod cannot be disabled for all am335x boards ...

It must be somehow configurable for boards ... I have am335x boards
which use the rtc from the SoC


Regards,
Dave

[1] http://www.spinics.net/lists/linux-omap/msg121987.html


bye,
Heiko
--
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] arm, am335x: add support for the bosch shc board

2015-11-17 Thread Dave Gerlach 

Hi,
On 11/17/2015 02:24 AM, Heiko Schocher wrote:

add support for the am335x based shc board.

UART: 0-2 and 4
DRAM: 512 MiB
MMC:  OMAP SD/MMC: 0 @ 26 MHz
   OMAP SD/MMC: 1 @ 26 MHz
I2C:  at24 eeprom, pcf8563
USB:  USB1 (host)

Signed-off-by: Heiko Schocher 
---
The following patches are needed to get all working
for the shc board:
- disable clkout on pcf8563
   accepted.
   http://www.spinics.net/lists/devicetree/msg98542.html

- leds: leds-gpio: add shutdown function
   accepted.
   https://lkml.org/lkml/2015/10/13/169

- net: phy: smsc: disable energy detect mode
   accepted
   [PATCH v2 2/2] net: phy: smsc: disable energy detect mode
   https://lkml.org/lkml/2015/10/17/2
   [PATCH v2 1/2] drivers: net: cpsw: add phy-handle parsing
   https://lkml.org/lkml/2015/10/17/4

- ARM: OMAP2+: omap_hwmod: Introduce ti,no-init dt property
   http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/328204.html
   @Dave: What is the current state of this patch?
   I have the same problem here on this am335x based board



A different approach is being taken for resolving the issue of rtc hwmod 
on am43x epos evm [1], which is what I was attempting to solve with the 
patch you have linked. We decided to avoid changing omap_hwmod code and 
I haven't been pursuing the ti,no-init flag anymore.


Regards,
Dave

[1] http://www.spinics.net/lists/linux-omap/msg121987.html


- [PATCH v2] regulator: tps65217: remove tps65217.dtsi file
   http://www.kernelhub.org/?msg=868907=2

- bootlog and automated tests:
   http://xeidos.ddns.net/buildbot/waterfall

Changes in v2:
- Use IOPAD pinmux macro as Robert Nelson
   suggested.

  arch/arm/boot/dts/Makefile   |   3 +-
  arch/arm/boot/dts/am335x-shc.dts | 577 +++
  2 files changed, 579 insertions(+), 1 deletion(-)
  create mode 100644 arch/arm/boot/dts/am335x-shc.dts

diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 30bbc37..65d750f 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -466,7 +466,8 @@ dtb-$(CONFIG_SOC_AM33XX) += \
am335x-pepper.dtb \
am335x-lxm.dtb \
am335x-chiliboard.dtb \
-   am335x-wega-rdk.dtb
+   am335x-wega-rdk.dtb \
+   am335x-shc.dtb
  dtb-$(CONFIG_ARCH_OMAP4) += \
omap4-duovero-parlor.dtb \
omap4-panda.dtb \
diff --git a/arch/arm/boot/dts/am335x-shc.dts b/arch/arm/boot/dts/am335x-shc.dts
new file mode 100644
index 000..1b5b044
--- /dev/null
+++ b/arch/arm/boot/dts/am335x-shc.dts
@@ -0,0 +1,577 @@
+/*
+ * support for the bosch am335x based shc c3 board
+ *
+ * Copyright, C) 2015 Heiko Schocher 
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+/dts-v1/;
+
+#include "am33xx.dtsi"
+#include 
+
+/ {
+   model = "Bosch SHC";
+   compatible = "ti,am335x-shc", "ti,am335x-bone", "ti,am33xx";
+
+   aliases {
+   mmcblk0 = 
+   mmcblk1 = 
+   };
+
+   cpus {
+   cpu@0 {
+   /*
+* To consider voltage drop between PMIC and SoC,
+* tolerance value is reduced to 2% from 4% and
+* voltage value is increased as a precaution.
+*/
+   operating-points = <
+   /* kHzuV */
+   594000  1225000
+   294000  1125000
+   >;
+   voltage-tolerance = <2>; /* 2 percentage */
+   cpu0-supply = <_reg>;
+   };
+   };
+
+   gpio_keys {
+   compatible = "gpio-keys";
+
+   back_button {
+   label = "Back Button";
+   gpios = < 29 GPIO_ACTIVE_HIGH>;
+   linux,code = ;
+   debounce-interval = <1000>;
+   gpio-key,wakeup;
+   };
+
+   front_button {
+   label = "Front Button";
+   gpios = < 25 GPIO_ACTIVE_HIGH>;
+   linux,code = ;
+   debounce-interval = <1000>;
+   gpio-key,wakeup;
+   };
+   };
+
+   leds {
+   pinctrl-names = "default";
+   pinctrl-0 = <_leds_s0>;
+
+   compatible = "gpio-leds";
+
+   led@1 {
+   label = "shc:power:red";
+   gpios = < 23 GPIO_ACTIVE_HIGH>;
+   default-state = "off";
+   };
+
+   led@2 {
+   label = "shc:power:bl";
+   gpios = < 22 GPIO_ACTIVE_HIGH>;
+   linux,default-trigger = "timer";
+