On Tue, Nov 15, 2016 at 09:35:15AM -0800, Tony Lindgren wrote:
> * Cor Peters <cpeters@xxxxxxxxxxxxxxxxx> [161115 01:00]:
> > This patch adds the PRM_DEV as a syscon compatible device to
> > am33xx.dtsi. This is needed for the watchdog bootstatus patch.
>
> We somehow need to see the bootreason for sure.. But we need to
> check with Tero on the reset driver work too.
>
Another problem is that the boot reason bit is not well defined and,
if I understand correctly, can change with different SoCs. So this
would also need a means to select the actual register bit to use.
Thanks,
Guenter
> Tero, does setting up of PRM_DEVICE as syscon cause issues for
> your reset driver work?
>
> Regards,
>
> Tony
>
> >
> > Signed-off-by: Cor Peters <cpeters@xxxxxxxxxxxxxxxxx>
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 194d884..e8faf19 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -115,6 +115,7 @@
> > prcm: prcm@200000 {
> > compatible = "ti,am3-prcm";
> > reg = <0x200000 0x4000>;
> > + ranges = <0 0x200000 0x4000>;
> >
> > prcm_clocks: clocks {
> > #address-cells = <1>;
> > @@ -123,6 +124,11 @@
> >
> > prcm_clockdomains: clockdomains {
> > };
> > +
> > + prcm_wkup: prcm-wkup@f00 {
> > + compatible = "ti,omap3-prcm-dev", "syscon";
> > + reg = <0xf00 0xff>;
> > + };
> > };
> >
> > scm: scm@210000 {
> > --
> > 1.9.1
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
