From: Colin Foster <colin.foster@in-advantage.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: "Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
soc@kernel.org, "Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>, "Andrew Davis" <afd@ti.com>
Subject: [PATCH v4 0/2] add support for Phytec PCM-049 and PCM-959
Date: Wed, 22 Feb 2023 12:38:45 -0800 [thread overview]
Message-ID: <20230222203847.2664903-1-colin.foster@in-advantage.com> (raw)
As should be clear for the title and patch title, this is adding initial
support for the OMAP 4460 SOM and dev kit for Phytec's PCM959 evaluation
kit.
The PCM049 is a legacy SOM offered by Phytec:
https://www.phytec.com/legacy-soms/
There was a vendor BSP offered by Phytec, but that never entered the
Device Tree era. This patch is meant to change that.
My development bootloader has moved to U-Boot, but I have verified
Barebox works in the past. When booting from SD card, either bootloader
should work. When booting from Barebox, the NAND OOB layout is
incompatible between the bootloader and the kernel.
I haven't had any OOB / ECC errors in the NAND at all, which was my
main concern. Due to that, I'm submitting this as a patch instead of
an RFC. Hardware ECC correction seems to be fully functional.
v3->v4
* Add initial .yaml documentation instead of omap.txt
Thanks to Andrew Davis <afd@ti.com> for posting their WIP patch
set, which was the basis for patch 1, with Rob's feedback.
* Removed Rob's "Acked-by" because the patch is completely different
* Removed unnecessary "omap-4430" from compatible in .dts
v2->v3
* Acked-by on patch 1
* Code review changes (see patch 2 for details)
* Fix intermittent NAND failures (patch 2)
v1->v2
* Almost everything moved into the SOM (PCM-049) .dtsi. Only the
LED chip is dev-board specific.
* Fix pinmux associations (*pmx_core was applying *pmx_wkup
entries... I'm surprised that didn't cause more issues)
* Documentation added
* Updates from review:
* Board compatible strings added
* Hyphen / underscore changes
* Remove unnecessary status="okay" entries
* Generic names used (regulator, led-1, etc.)
Colin Foster (2):
dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board
arm: dts: omap4: pcm959: add initial support for phytec pcm959
.../devicetree/bindings/arm/ti,omap.yaml | 29 ++
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/omap4-phytec-pcm-049.dtsi | 400 ++++++++++++++++++
arch/arm/boot/dts/omap4-phytec-pcm-959.dts | 48 +++
4 files changed, 478 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/ti,omap.yaml
create mode 100644 arch/arm/boot/dts/omap4-phytec-pcm-049.dtsi
create mode 100644 arch/arm/boot/dts/omap4-phytec-pcm-959.dts
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-02-22 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 20:38 Colin Foster [this message]
2023-02-22 20:38 ` [PATCH v4 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board Colin Foster
2023-02-22 21:40 ` Colin Foster
2023-02-23 16:00 ` Andrew Davis
2023-02-23 16:25 ` Colin Foster
2023-02-23 17:17 ` Andrew Davis
2023-02-26 17:22 ` Rob Herring
2023-02-27 7:15 ` Tony Lindgren
2023-02-22 20:38 ` [PATCH v4 2/2] arm: dts: omap4: pcm959: add initial support for phytec pcm959 Colin Foster
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=20230222203847.2664903-1-colin.foster@in-advantage.com \
--to=colin.foster@in-advantage.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).