Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 12 Apr 2022 12:39:44 +0300
From:   Tony Lindgren <tony@atomide.com>
To:     Adam Ford <aford173@gmail.com>
Cc:     linux-omap@vger.kernel.org, aford@beaconembedded.com,
        =?utf-8?Q?Beno=C3=AEt?= Cousson <bcousson@baylibre.com>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: am3517-evm: Fix misc pinmuxing
Message-ID: <YlVI4EAX5is25bqh@atomide.com>
References: <20220226214820.747847-1-aford173@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220226214820.747847-1-aford173@gmail.com>
Precedence: bulk

* Adam Ford <aford173@gmail.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@gmail.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