From: "Hans Christian Lønstad" <hcl@datarespons.no>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
"Hans Christian Lønstad" <hcl@datarespons.no>
Subject: Re: [RFT PATCH master 0/3] soc: imx8m-featctrl: fixes and first 8MP support
Date: Mon, 17 Oct 2022 19:46:44 +0000 [thread overview]
Message-ID: <435DD691-93D6-417E-82A6-405EEC677DC2@datarespons.no> (raw)
In-Reply-To: <20221017134929.622022-1-a.fatoum@pengutronix.de>
Works on deep-probe enabled imx8mp-evk as well as custom IMX8MP Quadlite.
Tested-by: Hans Christian Lonstad <hcl@datarespons.com>
> 17. okt. 2022 kl. 15:49 skrev Ahmad Fatoum <a.fatoum@pengutronix.de>:
>
> Newer upstream kernels may fail to boot with less featureful 8MP SoCs,
> because barebox doesn't fix the DT up appropriately. Fix that.
>
> @Hans, could you give this a test? I tested on 8MM only.
>
> Ahmad Fatoum (3):
> dt-bindings: features: imx8m: fix typo in constant
> soc: imx: imx8m-featctrl: check if all bits are set
> ARM: i.MX8MP: add feature controller support for Plus
>
> arch/arm/dts/imx8mp.dtsi | 43 ++++++++++++++++++++++++++++
> drivers/nvmem/ocotp.c | 9 ++++++
> drivers/soc/imx/imx8m-featctrl.c | 29 +++++++++++++------
> include/dt-bindings/features/imx8m.h | 6 ++--
> include/soc/imx8m/featctrl.h | 3 ++
> 5 files changed, 79 insertions(+), 11 deletions(-)
>
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-10-17 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 13:49 Ahmad Fatoum
2022-10-17 13:49 ` [RFT PATCH master 1/3] dt-bindings: features: imx8m: fix typo in constant Ahmad Fatoum
2022-10-17 13:49 ` [RFT PATCH master 2/3] soc: imx: imx8m-featctrl: check if all bits are set Ahmad Fatoum
2022-10-17 13:49 ` [RFT PATCH master 3/3] ARM: i.MX8MP: add feature controller support for Plus Ahmad Fatoum
2022-10-17 19:46 ` Hans Christian Lønstad [this message]
2022-10-18 8:57 ` [RFT PATCH master 0/3] soc: imx8m-featctrl: fixes and first 8MP support 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=435DD691-93D6-417E-82A6-405EEC677DC2@datarespons.no \
--to=hcl@datarespons.no \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox