mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <>
To: Sascha Hauer <>
Subject: Re: [PATCH 00/10] Add new feature controller framework
Date: Tue, 30 Aug 2022 09:38:57 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hello Sascha,

On 30.08.22 09:32, Sascha Hauer wrote:
> Hi Ahmad,
> On Thu, Aug 18, 2022 at 07:19:45AM +0200, Ahmad Fatoum wrote:
>> The i.MX8MM exists in a Lite variant with no VPUs as well as Solo and
>> Dual variants with one or two cores respectively instead of the default
>> four. For i.MX6, we had a manual fixup taking care of deleting the
>> excess CPUs, but for e.g. the i.MX8MP, we have fuses for the M7, VPUs, CAN,
>> CAN-FD, ISPs, NPU, ... etc. Describing all that in the DT is overly verbose
>> as we need to take care not to rely on specific device node names that
>> should be disabled. There has been an upstream attempt to get a binding
>> for U-Boot to act on:
>> This was refused by the DT maintainer, because any solution to this
>> problem should also be flexible enough to cover the case of partitioning
>> devices between the secure and normal world.
>> There's a patch series upstream to describe a domain-controller binding
>> that allows a hypervisor to partition devices into domains. With the
>> naming generalized, this fits nicely the use case of gating devices
>> behind specific features:
>> This series does that. See the first two commit messages for details.
>> We use a barebox, prefix as the naming isn't set in stone, but the intention
>> is to drop the prefix and potentially rename once an upstream binding is
>> approved.
> I am fine with this series. Is this still the way you want to have it
> merged or do you have an update?

No updates, please apply series, except for last two RFC commits.
I'll revise the naming once there is an upstream binding,
but we can do with the barebox, prefixed binding until then.


> Sascha

Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       |  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2022-08-30  7:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  5:19 Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 01/10] driver: add " Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 02/10] driver: consult feature controller prior to device probe Ahmad Fatoum
2022-08-18  8:19   ` Philipp Zabel
2022-08-18  8:34     ` Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 03/10] driver: featctrl: fixup kernel device tree Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 04/10] dt-bindings: add i.MX8M feature controller bindings Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 05/10] soc: imx: add i.MX8M feature controller driver Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 06/10] nvmem: import Linux nvmem_cell_read_variable_le_u32 Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 07/10] nvmem: ocotp: add i.MX8M[MN] feature controller support Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 08/10] ARM: dts: i.MX8MN: describe feature controller Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 09/10] RFC: soc: imx: imx8m-featctrl: add i.MX8M[MN] stand-alone driver Ahmad Fatoum
2022-08-18  5:19 ` [PATCH 10/10] RFC: ARM: dts: i.MX8MM: describe standlone feature controller Ahmad Fatoum
2022-08-30  7:32 ` [PATCH 00/10] Add new feature controller framework Sascha Hauer
2022-08-30  7:38   ` Ahmad Fatoum [this message]
2022-08-31  6:06     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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