From: Ryder Lee <ryder.lee@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Sean Wang <sean.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: mt7622: update a clock property for UART0
Date: Mon, 16 Jul 2018 23:04:36 +0800 [thread overview]
Message-ID: <1531753476.7842.1.camel@mtkswgap22> (raw)
In-Reply-To: <a4f0c6db-b88f-4c54-827a-e160bebae62b@gmail.com>
Hi,
On Mon, 2018-07-16 at 15:55 +0200, Matthias Brugger wrote:
> Hi Ryder,
>
> On 10/07/18 09:55, Ryder Lee wrote:
> > The input clock of UART0 should be CLK_PERI_UART0_PD.
> >
> > Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
>
> Can you provide a "Fixes" tag with the commit id of the commit that broke this?
>
> Thanks,
> Matthias
I've sent a new one with a "Fixes" tag.
Ryder
>
> > ---
> > arch/arm64/boot/dts/mediatek/mt7622.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> > index 8cdec52..4caa9b4 100644
> > --- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> > +++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> > @@ -367,7 +367,7 @@
> > reg = <0 0x11002000 0 0x400>;
> > interrupts = <GIC_SPI 91 IRQ_TYPE_LEVEL_LOW>;
> > clocks = <&topckgen CLK_TOP_UART_SEL>,
> > - <&pericfg CLK_PERI_UART1_PD>;
> > + <&pericfg CLK_PERI_UART0_PD>;
> > clock-names = "baud", "bus";
> > status = "disabled";
> > };
> >
prev parent reply other threads:[~2018-07-16 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 7:55 [PATCH 1/2] arm64: dts: mt7622: add some misc device nodes Ryder Lee
2018-07-10 7:55 ` [PATCH 2/2] arm64: dts: mt7622: update a clock property for UART0 Ryder Lee
2018-07-16 13:55 ` Matthias Brugger
2018-07-16 15:04 ` Ryder Lee [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=1531753476.7842.1.camel@mtkswgap22 \
--to=ryder.lee@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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).