[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c94494a-19a5-c62d-7a38-a79dfdd5692c@canonical.com>
Date: Wed, 2 Mar 2022 20:32:52 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Ashish Mhetre <amhetre@...dia.com>, robh+dt@...nel.org,
thierry.reding@...il.com, jonathanh@...dia.com, digetx@...il.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org
Cc: vdumpa@...dia.com, Snikam@...dia.com
Subject: Re: [Patch v4 1/4] arm64: tegra: Add memory controller channels
On 02/03/2022 09:43, Ashish Mhetre wrote:
> From tegra186 onwards, memory controller support multiple channels.
> During the error interrupts from memory controller, corresponding
> channels need to be accessed for logging error info and clearing the
> interrupt.
> So add address and size of these channels in device tree node of
> tegra186, tegra194 and tegra234 memory controller.
>
> Signed-off-by: Ashish Mhetre <amhetre@...dia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 7 ++++++-
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 21 ++++++++++++++++++---
> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 21 ++++++++++++++++++---
> 3 files changed, 42 insertions(+), 7 deletions(-)
>
You send DTS patch before, which is wrong order and actually it points
my attention to probably ABI break.
DTS goes always separately from driver changes so it is not only ABI
break, but also non-bisectable.
Best regards,
Krzysztof
Powered by blists - more mailing lists