All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-omap@vger.kernel.org, aford@beaconembedded.com,
	"Benoît 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
Date: Tue, 12 Apr 2022 12:39:44 +0300	[thread overview]
Message-ID: <YlVI4EAX5is25bqh@atomide.com> (raw)
In-Reply-To: <20220226214820.747847-1-aford173@gmail.com>

* 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

      reply	other threads:[~2022-04-12 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26 21:48 [PATCH] ARM: dts: am3517-evm: Fix misc pinmuxing Adam Ford
2022-04-12  9:39 ` Tony Lindgren [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=YlVI4EAX5is25bqh@atomide.com \
    --to=tony@atomide.com \
    --cc=aford173@gmail.com \
    --cc=aford@beaconembedded.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.