[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <542ABC90.7010900@pengutronix.de>
Date: Tue, 30 Sep 2014 16:22:08 +0200
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Wolfram Sang <wsa@...-dreams.de>, Roger Quadros <rogerq@...com>
CC: wg@...ndegger.com, tony@...mide.com, tglx@...utronix.de,
mugunthanvnm@...com, george.cherian@...com, balbi@...com,
nsekhar@...com, nm@...com, sergei.shtylyov@...entembedded.com,
linux-omap@...r.kernel.org, linux-can@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH v2 2/3] net: can: c_can: Add syscon/regmap RAMINIT mechanism
On 09/30/2014 04:19 PM, Wolfram Sang wrote:
>
>> As just TI is using this out of band RAMINIT mechanism, should it be "ti,syscon" or just "syscon"?
>
> Yes, only TI uses this out-of-band RAMINIT (currently, at least). So, we
> need an (optional) way to describe that. However, accessing syscon
> registers in general is not TI specific and a generic way to do this
> should be used. Which looks to me like the "syscon" property to allow
> access to the register. Still, we should ask DT maintainers about it,
> maybe they prefer a more precise property like "syscon-raminit" to allow
> for further syscon extensions later or something...
What do you think about putting the bit information in the
syscon-raminit phandle as additional arguments?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists