[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1501099634.2401.37.camel@baylibre.com>
Date: Wed, 26 Jul 2017 22:07:14 +0200
From: Jerome Brunet <jbrunet@...libre.com>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Neil Armstrong <narmstrong@...libre.com>,
Rob Herring <robh@...nel.org>, linux-clk@...r.kernel.org,
linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: clock: amlogic,gxbb-aoclkc: Update
bindings
On Tue, 2017-07-25 at 17:48 -0700, Stephen Boyd wrote:
> >
> > Maybe it is time to investigate having the regmap clock from qcom available
> > to
> > every other platform ?
>
> I think we have regmap clk duplicated a couple times in the
> drivers/clk/ directory now.
Which is why we may start thinking of common and generic "regmap" compatible
solution in the CCF, at least for things like gates, dividers and muxes
The approach used in qcom with regmap clocks could be a candidate for this,
don't you think ?
> Not sure how this is related, except
> for that there looks to be a desire to use a syscon binding here
> and that forces regmap on drivers?
Syscon has been created exactly for this case where you want to create an mfd
just for sharing a register region between several, otherwise well separated,
devices, isn't it ?
Powered by blists - more mailing lists