Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1259029 > unrolled thread

Re: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC

Started byArnd Bergmann <arnd@arndb.de>
First post2015-10-29 22:50 +0100
Last post2015-10-30 21:00 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC Arnd Bergmann <arnd@arndb.de> - 2015-10-29 22:50 +0100
    RE: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A  SoC Stuart Yoder <stuart.yoder@freescale.com> - 2015-10-30 17:40 +0100
      Re: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC Arnd Bergmann <arnd@arndb.de> - 2015-10-30 21:00 +0100

#1259029 — Re: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC

FromArnd Bergmann <arnd@arndb.de>
Date2015-10-29 22:50 +0100
SubjectRe: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC
Message-ID<qp3f4-5BD-5@gated-at.bofh.it>
On Wednesday 28 October 2015 16:09:44 J. German Rivera wrote:
> +       rst_ccsr: rstccsr@1E60000 {
> +               compatible = "syscon";
> +               reg = <0x0 0x1E60000 0x0 0x10000>;
> +       };
> +
> 

What does 'rstccsr' stand for? Is this by chance a reset controller?

If so, we probably want a real driver for it rather than just a
syscon.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1259611 — RE: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC

FromStuart Yoder <stuart.yoder@freescale.com>
Date2015-10-30 17:40 +0100
SubjectRE: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC
Message-ID<qpkSC-87y-11@gated-at.bofh.it>
In reply to#1259029

> -----Original Message-----
> From: Arnd Bergmann [mailto:arnd@arndb.de]
> Sent: Thursday, October 29, 2015 4:49 PM
> To: linux-arm-kernel@lists.infradead.org
> Cc: Rivera Jose-B46482; robh+dt@kernel.org; mark.rutland@arm.com; devicetree@vger.kernel.org; linux-
> kernel@vger.kernel.org; Sharma Bhupesh-B45370; Li Yang-Leo-R58472; Yoder Stuart-B08248
> Subject: Re: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC
> 
> On Wednesday 28 October 2015 16:09:44 J. German Rivera wrote:
> > +       rst_ccsr: rstccsr@1E60000 {
> > +               compatible = "syscon";
> > +               reg = <0x0 0x1E60000 0x0 0x10000>;
> > +       };
> > +
> >
> 
> What does 'rstccsr' stand for? Is this by chance a reset controller?

It is a region of some miscellaneous registers, some related to reset.
 
> If so, we probably want a real driver for it rather than just a
> syscon.

There is not other stuff in this region that to be exposed,
and so we really don't need a real driver.

My suggestion is to perhaps make that more explicit in the proposed
device tree node, by making the reg size "4" and naming it
as per the register name

       rstcr: rstcr@1E60000 {
               compatible = "syscon";
               reg = <0x0 0x1E60000 0x0 0x4>;
       };

The intent is really just to expose a single reset register
and use syscon-reboot until PSCI is available.

Thanks,
Stuart
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1259755

FromArnd Bergmann <arnd@arndb.de>
Date2015-10-30 21:00 +0100
Message-ID<qpo09-1wk-3@gated-at.bofh.it>
In reply to#1259611
On Friday 30 October 2015 16:34:26 Stuart Yoder wrote:
> My suggestion is to perhaps make that more explicit in the proposed
> device tree node, by making the reg size "4" and naming it
> as per the register name
> 
>        rstcr: rstcr@1E60000 {
>                compatible = "syscon";
>                reg = <0x0 0x1E60000 0x0 0x4>;
>        };
> 
> The intent is really just to expose a single reset register
> and use syscon-reboot until PSCI is available.

I would rather see a more specific compatible string here that describes
the actual name, e.g.

	compatible = "fsl,ls2085a-rstcr", "syscon";

this way we have the option of making it a real driver later on by matching
on the specific string, but using the fallback syscon string otherwise.

BTW, please change the address to lowercase letters in both the node name and
the reg property. I would also change the name to 'syscon' instead of 'rstcr',
making that

	rstcr: syscon@1e60000 {
		...
	};

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web