From: Hollis Blanchard <hollis_blanchard-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Cc: linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: "status" property checks
Date: Thu, 07 Jan 2010 15:07:53 -0800 [thread overview]
Message-ID: <1262905673.11702.16.camel@localhost.localdomain> (raw)
Right now, a number of drivers honor the "status" property on device
nodes (via of_device_is_available() checks), but it's open-coded in each
driver. I'm thinking of "hiding" arbitrary devices from the kernel, and
setting this property seems like the best approach, but at the moment
that would require modifying all OF drivers to check for it.
Wouldn't the better approach be to have of_platform_device_probe()
itself do the check, and not call the driver's probe() routine if the
device isn't available?
--
Hollis Blanchard
Mentor Graphics, Embedded Systems Division
WARNING: multiple messages have this Message-ID (diff)
From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: devicetree-discuss@lists.ozlabs.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: "status" property checks
Date: Thu, 07 Jan 2010 15:07:53 -0800 [thread overview]
Message-ID: <1262905673.11702.16.camel@localhost.localdomain> (raw)
Right now, a number of drivers honor the "status" property on device
nodes (via of_device_is_available() checks), but it's open-coded in each
driver. I'm thinking of "hiding" arbitrary devices from the kernel, and
setting this property seems like the best approach, but at the moment
that would require modifying all OF drivers to check for it.
Wouldn't the better approach be to have of_platform_device_probe()
itself do the check, and not call the driver's probe() routine if the
device isn't available?
--=20
Hollis Blanchard
Mentor Graphics, Embedded Systems Division
next reply other threads:[~2010-01-07 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 23:07 Hollis Blanchard [this message]
2010-01-07 23:07 ` "status" property checks Hollis Blanchard
2010-01-08 2:35 ` Hunter Cobbs
2010-01-08 18:34 ` Hollis Blanchard
2010-01-08 18:34 ` Hollis Blanchard
[not found] ` <1262975655.31871.67.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-08 19:28 ` Scott Wood
2010-01-08 19:28 ` Scott Wood
[not found] ` <4B478747.8070009-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2010-01-08 19:45 ` Hollis Blanchard
2010-01-08 19:45 ` Hollis Blanchard
2010-01-08 23:46 ` David Gibson
2010-01-08 23:58 ` Hollis Blanchard
2010-01-08 23:58 ` Hollis Blanchard
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=1262905673.11702.16.camel@localhost.localdomain \
--to=hollis_blanchard-nmggyn9qbj3qt0dzr+alfa@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.