From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, Shawn Guo <shawnguo@kernel.org>
Cc: <leoyang.li@nxp.com>, <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <vabhav.sharma@nxp.com>,
<linux@armlinux.org.uk>
Subject: Re: [PATCH 1/1] arm64: dts: lx2160a: Normalize the compatible string of "arm, sbsa-uart"
Date: Tue, 15 Jun 2021 19:38:15 +0800 [thread overview]
Message-ID: <cba3a29f-92b5-072a-9a27-60240f072dad@huawei.com> (raw)
In-Reply-To: <56133c63c48700e7@bloch.sibelius.xs4all.nl>
On 2021/6/12 18:11, Mark Kettenis wrote:
>> Date: Sat, 12 Jun 2021 10:10:58 +0800
>> From: Shawn Guo <shawnguo@kernel.org>
>>
>> On Tue, May 25, 2021 at 10:00:30AM +0800, Leizhen (ThunderTown) wrote:
>>>
>>>
>>> On 2021/5/25 1:36, Mark Kettenis wrote:
>>>>> From: Zhen Lei <thunder.leizhen@huawei.com>
>>>>> Date: Mon, 24 May 2021 11:52:44 +0800
>>>>> Content-Type: text/plain; charset="us-ascii"
>>>>>
>>>>> The compatible string of ARM SBSA defined generic UART needs to contain
>>>>> only "arm,sbsa-uart" and does not need to contain "arm,pl011". Otherwise,
>>>>> the pl011.yaml will check it and falsely report many warnings similar to
>>>>> the following:
>>>>>
>>>>> arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-cx.dt.yaml:
>>>>> serial@21c0000: compatible:0: 'arm,pl011' was expected
>>>>> serial@21c0000: compatible:1: 'arm,primecell' was expected
>>>>>
>>>>> Delete the redundant "arm,pl011" to fix it.
>>>>
>>>> According to its reference manual, the LX2160A has a full PL011
>>>> implementation. So I think this is the wrong "fix".
>>>
>>> No, No, Please refer: https://www.spinics.net/lists/devicetree/msg424054.html
>>>
>>> Now the "arm,sbsa-uart" driver is mixed with amba-pl011.c,It's impossible
>>> "arm,pl011" is loaded but "arm,sbsa-uart" is not loaded. So it makes no sense
>>> to append "arm, pl011" to the end of the compatible string as an alternative
>>> driver.
>>>
>>> drivers/tty/serial/amba-pl011.c:2784: { .compatible = "arm,sbsa-uart", },
>>
>> I guess Mark is suggesting the following fix.
>>
>> uart0: serial@21c0000 {
>> - compatible = "arm,sbsa-uart","arm,pl011";
>> + compatible = "arm,pl011", "arm,primecell";
>> reg = <0x0 0x21c0000 0x0 0x1000>;
>> interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
>> - current-speed = <115200>;
>> status = "disabled";
>> };
>>
>> I copied some folks who might help clarify whether LX2160A UART is a SBSA
>> or a full PL011.
>
> Sorry, I missed Leizhen's original reply. But yes, that is what I
> meant. According to the NXP documentation, the LX2160A has a real
> PL011 UART, so the correct fix is what Shawn suggests above.
Okay, so I'll prepare v2 on the advice of Shawn.
>
> Cheers,
>
> Mark
>
>>>>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>>>>> ---
>>>>> arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 8 ++++----
>>>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
>>>>> index 4fcc869c21a4..417546616d85 100644
>>>>> --- a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
>>>>> +++ b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
>>>>> @@ -920,7 +920,7 @@
>>>>> };
>>>>>
>>>>> uart0: serial@21c0000 {
>>>>> - compatible = "arm,sbsa-uart","arm,pl011";
>>>>> + compatible = "arm,sbsa-uart";
>>>>> reg = <0x0 0x21c0000 0x0 0x1000>;
>>>>> interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
>>>>> current-speed = <115200>;
>>>>> @@ -928,7 +928,7 @@
>>>>> };
>>>>>
>>>>> uart1: serial@21d0000 {
>>>>> - compatible = "arm,sbsa-uart","arm,pl011";
>>>>> + compatible = "arm,sbsa-uart";
>>>>> reg = <0x0 0x21d0000 0x0 0x1000>;
>>>>> interrupts = <GIC_SPI 33 IRQ_TYPE_LEVEL_HIGH>;
>>>>> current-speed = <115200>;
>>>>> @@ -936,7 +936,7 @@
>>>>> };
>>>>>
>>>>> uart2: serial@21e0000 {
>>>>> - compatible = "arm,sbsa-uart","arm,pl011";
>>>>> + compatible = "arm,sbsa-uart";
>>>>> reg = <0x0 0x21e0000 0x0 0x1000>;
>>>>> interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
>>>>> current-speed = <115200>;
>>>>> @@ -944,7 +944,7 @@
>>>>> };
>>>>>
>>>>> uart3: serial@21f0000 {
>>>>> - compatible = "arm,sbsa-uart","arm,pl011";
>>>>> + compatible = "arm,sbsa-uart";
>>>>> reg = <0x0 0x21f0000 0x0 0x1000>;
>>>>> interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>;
>>>>> current-speed = <115200>;
>>>>> --
>>>>> 2.21.1
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> linux-arm-kernel mailing list
>>>>> linux-arm-kernel@lists.infradead.org
>>>>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>>>>
>>>>
>>>> .
>>>>
>>>
>>
>
> .
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-15 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 3:52 [PATCH 1/1] arm64: dts: lx2160a: Normalize the compatible string of "arm, sbsa-uart" Zhen Lei
2021-05-24 17:36 ` Mark Kettenis
2021-05-25 2:00 ` Leizhen (ThunderTown)
2021-06-12 2:10 ` Shawn Guo
2021-06-12 10:11 ` Mark Kettenis
2021-06-15 11:38 ` Leizhen (ThunderTown) [this message]
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=cba3a29f-92b5-072a-9a27-60240f072dad@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.kettenis@xs4all.nl \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vabhav.sharma@nxp.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).