From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] ARM: tegra: Drop reg-shift for Tegra HS UART
Date: Wed, 8 Dec 2021 18:04:45 +0300 [thread overview]
Message-ID: <97c48f01-1224-2538-9368-41d23b617bd2@gmail.com> (raw)
In-Reply-To: <YbDIYjlActbuTuyf@orome>
08.12.2021 17:59, Thierry Reding пишет:
> On Tue, Dec 07, 2021 at 05:41:52PM +0300, Dmitry Osipenko wrote:
>> 07.12.2021 17:19, Dmitry Osipenko пишет:
>>> 07.12.2021 13:13, Thierry Reding пишет:
>>>> From: Thierry Reding <treding@nvidia.com>
>>>>
>>>> When the Tegra High-Speed UART is used instead of the regular UART, the
>>>> reg-shift property is implied from the compatible string and should not
>>>> be explicitly listed.
>>>>
>>>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>>>> ---
>>>> arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 3 +++
>>>> arch/arm/boot/dts/tegra124-jetson-tk1.dts | 2 ++
>>>> arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi | 2 ++
>>>> arch/arm/boot/dts/tegra30-colibri.dtsi | 2 ++
>>>> 4 files changed, 9 insertions(+)
>>>
>>> What about Ouya?
>>>
>>
>> What about T20?
>
> I went through all of the above based on results from a dtbs_check run.
> I don't see these errors flagged for Ouya or any Tegra20 boards. I have
> no idea why and will need to look into it some more.
Alright, something is wrong then. The serial@70006200 node on Ouya is
exactly the same as on Nexus7, T20 Acer A500 is almost the same.
next prev parent reply other threads:[~2021-12-08 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 10:13 [PATCH] ARM: tegra: Drop reg-shift for Tegra HS UART Thierry Reding
2021-12-07 14:19 ` Dmitry Osipenko
2021-12-07 14:41 ` Dmitry Osipenko
2021-12-08 14:59 ` Thierry Reding
2021-12-08 15:04 ` Dmitry Osipenko [this message]
2021-12-08 15:12 ` Thierry Reding
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=97c48f01-1224-2538-9368-41d23b617bd2@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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