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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35
Date: Tue, 12 Apr 2022 12:40:41 +0300 [thread overview]
Message-ID: <YlVJGYeT95eL7ZHt@atomide.com> (raw)
In-Reply-To: <20220303171818.11060-1-aford173@gmail.com>
* Adam Ford <aford173@gmail.com> [220303 19:17]:
> The pinout of the OMAP35 and DM37 variants of the SOM-LV are the
> same, but the macros which define the pinmuxing are different
> between OMAP3530 and DM3730. The pinmuxing was correct for
> for the DM3730, but wrong for the OMAP3530. Since the boot loader
> was correctly pin-muxing the pins, this was not obvious. As the
> bootloader not guaranteed to pinmux all the pins any more, this
> causes an issue, so the pinmux needs to be moved from a common
> file to their respective board files.
>
> Fixes: f8a2e3ff7103 ("ARM: dts: Add minimal support for LogicPD OMAP35xx SOM-LV devkit")
> Signed-off-by: Adam Ford <aford173@gmail.com>
Applying this too to fixes to avoid confusion with the bootloader
version.
Regards,
Tony
prev parent reply other threads:[~2022-04-12 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 17:18 [PATCH 1/2] ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 Adam Ford
2022-03-03 17:18 ` [PATCH 2/2] ARM: dts: logicpd-som-lv: Move pinmuxing to peripheral nodes Adam Ford
2022-04-21 10:48 ` Tony Lindgren
2022-04-12 9:40 ` 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=YlVJGYeT95eL7ZHt@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--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.