[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140826073055.GD15573@ulmo>
Date: Tue, 26 Aug 2014 09:31:03 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Doug Anderson <dianders@...omium.org>
Cc: Heiko Stübner <heiko@...ech.de>,
Caesar Wang <caesar.wang@...k-chips.com>,
Sonny Rao <sonnyrao@...omium.org>,
Olof Johansson <olof@...om.net>,
Eddie Cai <eddie.cai@...k-chips.com>,
Russell King <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Tomasz Figa <tomasz.figa@...il.com>
Subject: Re: [PATCH 1/4] ARM: rockchip: rk3288: Switch to use the proper PWM
IP
On Mon, Aug 25, 2014 at 04:40:57PM -0700, Doug Anderson wrote:
[...]
> I was doing some thinking about what to do, then. I wondered whether
> the right thing to do is not to make a "rk3288 syscon" driver that
> configures these bits, but rather to make a "rk3288" driver has access
> to the syscon. It could live in drivers/soc/rockchip/rk3288.c and we
> could give it a handle to the syscon. It could do the one-time
> initialization. It would also be a place to put special rk3288 APIs
> in cases where other drivers need similar things.
>
> What do you think?
Yes, that could work. There have been recent discussions about adding
such machine drivers that match on the top-level compatible string in
the DT.
I still think that subclassing syscon would be the cleanest solution,
though.
Thierry
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists