[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YlVI4EAX5is25bqh@atomide.com>
Date: Tue, 12 Apr 2022 12:39:44 +0300
From: Tony Lindgren <tony@...mide.com>
To: Adam Ford <aford173@...il.com>
Cc: linux-omap@...r.kernel.org, aford@...conembedded.com,
BenoƮt Cousson <bcousson@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: am3517-evm: Fix misc pinmuxing
* Adam Ford <aford173@...il.com> [220226 23:47]:
> The bootloader for the AM3517 has previously done much of the pin
> muxing, but as the bootloader is moving more and more to a model
> based on the device tree, it may no longer automatically pux the
> pins, so it is necessary to add the pinmuxing to the Linux device
> trees so the respective peripherals can remain functional.
>
> Fixes: 6ed1d7997561 ("ARM: dts: am3517-evm: Add support for UI board and Audio")
> Signed-off-by: Adam Ford <aford173@...il.com>
> ---
> I put the fixes tag here, because I feel that the pinmuxing should not
> have depended on the bootloader, but if it's not appropriate, feel free
> to drop the fixes tag when applying or I can submit a subsequent patch
> with the fixes tag dropped.
Makes sense as a fix as confusing issues like this are annoying. So
applying into fixes fixes with s/pux/mux/ typo correction.
Regards,
Tony
Powered by blists - more mailing lists