[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181107210059.j2wd4v2uawsjniol@kahuna>
Date: Wed, 7 Nov 2018 15:00:59 -0600
From: Nishanth Menon <nm@...com>
To: "Vutla, Lokesh" <lokeshvutla@...com>
CC: "R, Vignesh" <vigneshr@...com>, "Kristo, Tero" <t-kristo@...com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: dts: k3-am65-wakeup: Fix wakeup_uart reg address
On 10:10-20181005, Vutla, Lokesh wrote:
>
>
> On Thursday 27 September 2018 10:31 AM, Vignesh R wrote:
> > cbass_wakeup interconnect which is the parent of wakeup_uart node
> > defines address-cells=1 and size-cells=1, therefore fix up reg property
> > of wakeup_uart node accordingly. Otherwise, this UART instance fails to
> > probe if enabled.
> >
> > Fixes: 4201af2544b3 ("arm64: dts: ti: am654: Add uart nodes")
> > Signed-off-by: Vignesh R <vigneshr@...com>
>
> Reviewed-by: Lokesh Vutla <lokeshvutla@...com>
Tero:
Could we pick this up for rc2? looks like $subject might be good to fix
up to:
arm64: dts: ti: k3-am65-wakeup: Fix wakeup_uart reg address
instead of
arm64: dts: k3-am65-wakeup: Fix wakeup_uart reg address
could be fixed locally.
--
Regards,
Nishanth Menon
Powered by blists - more mailing lists