From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/2] dt-bindings: tegra: Remove 0, prefix from unit-addresses
Date: Fri, 15 Apr 2016 15:41:02 +0200 [thread overview]
Message-ID: <20160415134102.GB3472@ulmo.ba.sec> (raw)
In-Reply-To: <1460473656-27209-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
On Tue, Apr 12, 2016 at 05:07:35PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> When Tegra124 support was first merged the unit-addresses of all devices
> were listed with a "0," prefix to encode the reg property's second cell.
> It turns out that this notation is not correct, and the "," separator is
> only used to separate fields in the unit address (such as the device and
> function number in PCI devices), not individual cells for addresses
> with more than one cell.
>
> Acked-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> Signed-off-by: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> ---
> Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.txt | 2 +-
> Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt | 2 +-
> .../devicetree/bindings/memory-controllers/nvidia,tegra-mc.txt | 6 +++---
> Documentation/devicetree/bindings/memory-controllers/tegra-emc.txt | 4 ++--
> .../devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt | 6 +++---
> Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.txt | 2 +-
> Documentation/devicetree/bindings/thermal/tegra-soctherm.txt | 2 +-
> 7 files changed, 12 insertions(+), 12 deletions(-)
Hi Rob,
Is this (and patch 2/2) something that you could pick up into the DT
tree, or would you rather have me take it through the Tegra tree?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-15 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 15:07 [PATCH v2 1/2] dt-bindings: tegra: Remove 0, prefix from unit-addresses Thierry Reding
[not found] ` <1460473656-27209-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-12 15:07 ` [PATCH v2 2/2] dt-bindings: tegra: Rename some bindings for consistency Thierry Reding
[not found] ` <1460473656-27209-2-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-19 22:24 ` Rob Herring
2016-04-15 13:41 ` Thierry Reding [this message]
[not found] ` <20160415134102.GB3472-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2016-04-15 16:46 ` [PATCH v2 1/2] dt-bindings: tegra: Remove 0, prefix from unit-addresses Rob Herring
2016-04-19 22:24 ` Rob Herring
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=20160415134102.GB3472@ulmo.ba.sec \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox