mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Hans Christian Lonstad <hcl@datarespons.com>
Subject: [PATCH 0/3] soc: imx: featctrl: finalize support for i.MX8MP
Date: Fri, 19 Jan 2024 23:45:19 +0100	[thread overview]
Message-ID: <20240119224522.1399213-1-a.fatoum@pengutronix.de> (raw)

We only had preliminary feature controller support for i.MX8MP and
support for detecting missing VPU, DSP, NPU, LVDS and CPUs was missing.

Add support for them, so barebox may fix up the kernel device tree to
disable these nodes. This is especially important for the VPU and NPU as
the kernel's blk-ctrl power domain driver may try to power them down as
they are unused, which would make the SoC hang.

Ahmad Fatoum (3):
  soc: imx: imx8m-featctrl: make header self-contained
  nvmem: ocotp: prepare adding tester3 support
  soc: imx: featctrl: finalize support for i.MX8MP

 arch/arm/dts/imx8mp.dtsi             | 54 +++++++++++++++++++++++++++-
 drivers/nvmem/ocotp.c                | 27 +++++++++-----
 drivers/soc/imx/imx8m-featctrl.c     | 45 +++++++++++++++--------
 include/dt-bindings/features/imx8m.h |  5 ++-
 include/soc/imx8m/featctrl.h         | 25 +++++++++----
 5 files changed, 123 insertions(+), 33 deletions(-)

-- 
2.39.2




             reply	other threads:[~2024-01-19 22:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 22:45 Ahmad Fatoum [this message]
2024-01-19 22:45 ` [PATCH 1/3] soc: imx: imx8m-featctrl: make header self-contained Ahmad Fatoum
2024-01-19 22:45 ` [PATCH 2/3] nvmem: ocotp: prepare adding tester3 support Ahmad Fatoum
2024-01-22  9:35   ` Sascha Hauer
2024-01-19 22:45 ` [PATCH 3/3] soc: imx: featctrl: finalize support for i.MX8MP Ahmad Fatoum
2024-01-22  9:31 ` [PATCH 0/3] " Sascha Hauer

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=20240119224522.1399213-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=hcl@datarespons.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