From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms+renesas@verge.net.au>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andy Gross <agross@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Kaneko <ykaneko0929@gmail.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 3/3] arm64: dts: qcom: msm8996: Update simple-pm-bus node name to 'bus'
Date: Tue, 24 Sep 2019 13:15:49 +0300 [thread overview]
Message-ID: <3d9dcd04-b34d-957e-6269-cf39a15b4b27@cogentembedded.com> (raw)
In-Reply-To: <20190924093609.22895-4-horms+renesas@verge.net.au>
Hello!
On 09/24/2019 12:36 PM, Simon Horman wrote:
> Update simple-pm-bus node name from 'agnoc' to 'bus' reflecting the
> proposed binding description in json-schema which in turn reflects the ePAR
It's ePAPR. BTW, you can now refer to DT spec itself instead -- it was based
on ePAPR...
> standard - "the name of a node should be somewhat generic, reflecting the
> function of the device and not its precise programming model."
>
> Also drop the unit address as there is neither a reg property nor
> non-empty ranges.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
[...]
MBR, Sergei
next prev parent reply other threads:[~2019-09-24 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 9:36 [PATCH v3 0/3] dt-bindings: bus: simple-pm-bus, renesas-bsc: convert bindings to json-schema Simon Horman
2019-09-24 9:36 ` [PATCH v3 1/3] dt-bindings: bus: simple-pm-bus: " Simon Horman
2019-09-27 18:38 ` Rob Herring
2019-09-30 11:31 ` Simon Horman
2019-09-24 9:36 ` [PATCH v3 2/3] dt-bindings: bus: renesas-bsc: " Simon Horman
2019-09-24 9:36 ` [PATCH v3 3/3] arm64: dts: qcom: msm8996: Update simple-pm-bus node name to 'bus' Simon Horman
2019-09-24 10:15 ` Sergei Shtylyov [this message]
2019-09-24 10:18 ` Sergei Shtylyov
2019-09-26 8:32 ` Simon Horman
2019-09-26 8:38 ` Sergei Shtylyov
2019-09-26 11:58 ` Geert Uytterhoeven
2019-09-30 11:29 ` Simon Horman
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=3d9dcd04-b34d-957e-6269-cf39a15b4b27@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ykaneko0929@gmail.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).