From: Mark Brown <broonie@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Rob Herring <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, boot-architecture@lists.linaro.org,
Stephen Boyd <sboyd@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexander Graf <agraf@suse.de>,
Grant Likely <grant.likely@arm.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] driver core: make deferring probe forever optional
Date: Sat, 5 May 2018 10:25:13 +0900 [thread overview]
Message-ID: <20180505012513.GJ13402@sirena.org.uk> (raw)
In-Reply-To: <74d495d8-04e2-fb7d-7d07-0905fbc8a6cf@arm.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Wed, May 02, 2018 at 07:49:57PM +0100, Robin Murphy wrote:
> I guess there's also the possibility that a single driver may want multiple
> behaviours, if e.g. if SoC variants A and B have some identical peripherals
> but slightly different pinctrl/IOMMU/etc. hardware such that A has workable
> default behaviour and can be treated as optional, whereas B absolutely must
> be controlled by the kernel for the consumers to function properly, and they
> *should* defer forever otherwise. I think that would pretty much demand some
> sort of explicitly-curated white/blacklist setup at the subsystem or driver
> level.
Different board variants, and possibly even different bootloaders might
also be an issue here - a vendor bootloader might do pinmuxing that an
upstream bootloader doesn't for example. In some cases the pinmuxing
even depends on the boot method with things only getting configured if
the bootloader wanted to use them.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-05 1:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 21:31 [RFC PATCH] driver core: make deferring probe forever optional Rob Herring
2018-05-01 22:08 ` Greg Kroah-Hartman
2018-05-02 11:40 ` Robin Murphy
2018-05-02 14:48 ` Rob Herring
2018-05-02 18:49 ` Robin Murphy
2018-05-05 1:25 ` Mark Brown [this message]
2018-05-07 13:37 ` Rob Herring
2018-05-02 13:16 ` Alexander Graf
2018-05-07 18:31 ` Bjorn Andersson
2018-05-07 19:55 ` Rob Herring
2018-05-07 22:34 ` Bjorn Andersson
2018-05-09 9:18 ` Mark Brown
2018-05-09 9:57 ` Alexander Graf
2018-05-09 22:34 ` Rob Herring
2018-05-09 22:30 ` Rob Herring
2018-05-09 9:44 ` Alexander Graf
2018-05-13 22:01 ` Linus Walleij
2018-05-14 7:37 ` Alexander Graf
2018-05-14 12:44 ` Michal Simek
2018-05-16 14:38 ` Linus Walleij
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=20180505012513.GJ13402@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agraf@suse.de \
--cc=boot-architecture@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).