From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
Rob Herring <robh@kernel.org>,
linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: clock: amlogic,gxbb-aoclkc: Update bindings
Date: Wed, 26 Jul 2017 22:07:14 +0200 [thread overview]
Message-ID: <1501099634.2401.37.camel@baylibre.com> (raw)
In-Reply-To: <20170726004830.GI2146@codeaurora.org>
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 ?
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] dt-bindings: clock: amlogic,gxbb-aoclkc: Update bindings
Date: Wed, 26 Jul 2017 22:07:14 +0200 [thread overview]
Message-ID: <1501099634.2401.37.camel@baylibre.com> (raw)
In-Reply-To: <20170726004830.GI2146@codeaurora.org>
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 ?
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 3/3] dt-bindings: clock: amlogic,gxbb-aoclkc: Update bindings
Date: Wed, 26 Jul 2017 22:07:14 +0200 [thread overview]
Message-ID: <1501099634.2401.37.camel@baylibre.com> (raw)
In-Reply-To: <20170726004830.GI2146@codeaurora.org>
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 ?
next prev parent reply other threads:[~2017-07-26 20:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 10:24 [PATCH 0/3] clk: meson: gxbb-aoclk: Add CEC 32k clock Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-06 10:24 ` [PATCH 1/3] dt-bindings: clock: " Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-06 10:24 ` [PATCH 2/3] clk: meson: " Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-06 10:24 ` [PATCH 3/3] dt-bindings: clock: amlogic,gxbb-aoclkc: Update bindings Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-06 10:24 ` Neil Armstrong
2017-07-10 3:50 ` Rob Herring
2017-07-10 3:50 ` Rob Herring
2017-07-10 3:50 ` Rob Herring
2017-07-10 3:50 ` Rob Herring
2017-07-21 20:44 ` Stephen Boyd
2017-07-21 20:44 ` Stephen Boyd
2017-07-21 20:44 ` Stephen Boyd
2017-07-21 20:44 ` Stephen Boyd
2017-07-24 11:47 ` Neil Armstrong
2017-07-24 11:47 ` Neil Armstrong
2017-07-24 11:47 ` Neil Armstrong
2017-07-24 11:47 ` Neil Armstrong
2017-07-24 12:00 ` Jerome Brunet
2017-07-24 12:00 ` Jerome Brunet
2017-07-24 12:00 ` Jerome Brunet
2017-07-26 0:48 ` Stephen Boyd
2017-07-26 0:48 ` Stephen Boyd
2017-07-26 0:48 ` Stephen Boyd
2017-07-26 20:07 ` Jerome Brunet [this message]
2017-07-26 20:07 ` Jerome Brunet
2017-07-26 20:07 ` Jerome Brunet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1501099634.2401.37.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.