From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"pierre.gondois@arm.com" <pierre.gondois@arm.com>,
"vadym.kochan@plvision.eu" <vadym.kochan@plvision.eu>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: marvell: AC5/AC5X: Fix address for UART1
Date: Tue, 10 Jan 2023 10:29:30 +0100 [thread overview]
Message-ID: <87y1qahh51.fsf@BL-laptop> (raw)
In-Reply-To: <70fb6048-848e-e558-a1b9-3d74aca8ec01@alliedtelesis.co.nz>
Chris Packham <Chris.Packham@alliedtelesis.co.nz> writes:
> Hi All,
>
> On 15/12/22 15:54, Chris Packham wrote:
>> The correct address offset is 0x12100.
>>
>> Fixes: 31be791e26cf ("arm64: dts: marvell: Add UART1-3 for AC5/AC5X")
>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
>> ---
>> Not sure how this happened. I only noticed when I had a conflict in some
>> local patches I was rebasing against upstream. So I obviously had it
>> right at one point but then managed to break it in the process of
>> cleaning things up for submission.
>
> I know people have probably been away with various holidays but I think
> it's been long enough so....
>
> ping?
Applied on mvebu/fixes
Thanks,
Gregory
>
>>
>> arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
>> index 7308f7b6b22c..8bce64069138 100644
>> --- a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
>> +++ b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
>> @@ -98,7 +98,7 @@ uart0: serial@12000 {
>>
>> uart1: serial@12100 {
>> compatible = "snps,dw-apb-uart";
>> - reg = <0x11000 0x100>;
>> + reg = <0x12100 0x100>;
>> reg-shift = <2>;
>> interrupts = <GIC_SPI 84 IRQ_TYPE_LEVEL_HIGH>;
>> reg-io-width = <1>;
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2023-01-10 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 2:54 [PATCH] arm64: dts: marvell: AC5/AC5X: Fix address for UART1 Chris Packham
2023-01-10 3:34 ` Chris Packham
2023-01-10 9:29 ` Gregory CLEMENT [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=87y1qahh51.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--cc=robh+dt@kernel.org \
--cc=vadym.kochan@plvision.eu \
/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).