From: Philipp Zabel <p.zabel@pengutronix.de>
To: Jun Nie <jun.nie@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
sboyd@kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Wei Xu <xuwei5@hisilicon.com>,
opensource@jilayne.com, swinslow@gmail.com, allison@lohutok.net,
yuehaibing@huawei.com, tglx@linutronix.de,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, xuejiancheng@hisilicon.com
Subject: Re: [PATCH 1/3] dt-bindings: clock: Update Hisilicon reset doc
Date: Tue, 03 Dec 2019 15:12:53 +0100 [thread overview]
Message-ID: <0aec80383d4deea2574a016c8a8b370bcc006c8e.camel@pengutronix.de> (raw)
In-Reply-To: <CABymUCOoTZ0MAmtb9O2N+KZj+XF=073C9=BxBgbL9RXwMCuuMA@mail.gmail.com>
On Tue, 2019-12-03 at 11:11 +0800, Jun Nie wrote:
> Philipp Zabel <p.zabel@pengutronix.de> 于2019年12月3日周二 上午1:04写道:
> > Hi Jun,
> >
> > I have a few questions and comments about these patches. I notice that
> > the changed device trees only use the default setting. Are these new
> > features something that is required for the present SoCs, or is this in
> > preparation for a new SoC?
>
> Yes, this patch set is prepared for new SoC.
>
> > On Mon, 2019-12-02 at 22:45 +0800, Jun Nie wrote:
> > > Document the update of Hisilicon reset operation extension.
> > >
> > > Signed-off-by: Jun Nie <jun.nie@linaro.org>
> > > ---
> > > .../devicetree/bindings/clock/hisi-crg.txt | 12 ++++----
> > > include/dt-bindings/reset/hisilicon-resets.h | 28 +++++++++++++++++++
> > > 2 files changed, 35 insertions(+), 5 deletions(-)
> > > create mode 100644 include/dt-bindings/reset/hisilicon-resets.h
> > >
> > > diff --git a/Documentation/devicetree/bindings/clock/hisi-crg.txt b/Documentation/devicetree/bindings/clock/hisi-crg.txt
> > > index cc60b3d423f3..fd8b0a964806 100644
> > > --- a/Documentation/devicetree/bindings/clock/hisi-crg.txt
> > > +++ b/Documentation/devicetree/bindings/clock/hisi-crg.txt
> > > @@ -26,19 +26,21 @@ to specify the clock which they consume.
> > >
> > > All these identifier could be found in <dt-bindings/clock/hi3519-clock.h>.
> > >
> > > -- #reset-cells: should be 2.
> > > +- #reset-cells: should be 3.
If this is only needed for a new SoC, you should introduce a new
compatible and leave #reset-cells = <2> for the old compatible. The new
compatible can require #reset-cells = <3>. Wit this, the current device
trees don't have to be changed at all.
regards
Philipp
next prev parent reply other threads:[~2019-12-03 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 14:45 [PATCH 0/3] Extend Hisilicon reset type Jun Nie
2019-12-02 14:45 ` [PATCH 1/3] dt-bindings: clock: Update Hisilicon reset doc Jun Nie
2019-12-02 17:04 ` Philipp Zabel
2019-12-03 3:11 ` Jun Nie
2019-12-03 14:12 ` Philipp Zabel [this message]
2019-12-02 14:45 ` [PATCH 2/3] reset: hisilicon: Extend reset operation type Jun Nie
2019-12-02 17:04 ` Philipp Zabel
2019-12-03 3:53 ` Jun Nie
2019-12-03 14:15 ` Philipp Zabel
2019-12-04 6:09 ` Jun Nie
2019-12-02 14:45 ` [PATCH 3/3] ARM: dts: Update reset for hi3519 and hi3798cv200 Jun Nie
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=0aec80383d4deea2574a016c8a8b370bcc006c8e.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=allison@lohutok.net \
--cc=devicetree@vger.kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=opensource@jilayne.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=swinslow@gmail.com \
--cc=tglx@linutronix.de \
--cc=xuejiancheng@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=yuehaibing@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).