From: Philipp Zabel <p.zabel@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Cc: lst@pengutronix.de, ukl@pengutronix.de
Subject: Re: [PATCH 02/10] driver: consult feature controller prior to device probe
Date: Thu, 18 Aug 2022 10:19:54 +0200 [thread overview]
Message-ID: <ceb58cd4e79f540e5036b15e545aa758df3aaeba.camel@pengutronix.de> (raw)
In-Reply-To: <20220818051955.2088238-3-a.fatoum@pengutronix.de>
Hi Ahmad,
On Do, 2022-08-18 at 07:19 +0200, Ahmad Fatoum wrote:
> The newly added feature controller framework has two goals: Avoid
> probing device in barebox that aren't indeed available
This specific wording makes me wonder why this isn't implemented inside
of_device_is_available().
This would also take care of other devices querying device node
availability, for example via of_graph_port_is_available(), if that
ever happens.
regards
Philipp
next prev parent reply other threads:[~2022-08-18 8:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 5:19 [PATCH 00/10] Add new feature controller framework 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 [this message]
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
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:
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=ceb58cd4e79f540e5036b15e545aa758df3aaeba.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=lst@pengutronix.de \
--cc=ukl@pengutronix.de \
/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