From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC v4] ARM: shmobile: armadillo800eva-reference: add SDHI and MMCIF interfaces
Date: Sun, 29 Sep 2013 06:49:26 +0000 [thread overview]
Message-ID: <2318676.bdc47MCX2p@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1309231651230.11505@axis700.grange>
Hi Linus,
On Friday 27 September 2013 16:08:31 Linus Walleij wrote:
> On Fri, Sep 27, 2013 at 2:55 AM, Laurent Pinchart wrote:
> > Is there a way to patch the device tree in the board code init function to
> > turn "disabled" into "okay" based on the state of a GPIO ?
>
> Can't you just locate the node using of_find_node_by_path()
> or whatever and then use this:
> int of_update_property(struct device_node *np, struct property *newprop)?
Where can I do that ? I need the PFC/GPIO devices to have been probed, so
board init isn't an option, but I also need the device to be enabled not to
have been probed yet.
One option would be to use a bus notifier to find out when the PFC/GPIO
devices are available, and extend of_update_property() with a notification
mechanism (either generic, or specific to the enabled propery) to detect when
a device gets enabled and probe it.
Before implementing that, I'd like to know if this approach has a chance to be
accepted.
> It's not like I'm a master of DT but... I'd very much like to know as well,
> because it'd be very useful :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-09-29 6:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 15:38 [PATCH/RFC v4] ARM: shmobile: armadillo800eva-reference: add SDHI and MMCIF interfaces Guennadi Liakhovetski
2013-09-25 5:36 ` Simon Horman
[not found] ` <20130925053636.GD1916-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-09-25 7:03 ` Simon Horman
2013-09-25 9:05 ` Laurent Pinchart
2013-09-26 7:46 ` Linus Walleij
2013-09-26 8:24 ` Guennadi Liakhovetski
2013-09-26 9:41 ` Magnus Damm
2013-09-26 9:57 ` Guennadi Liakhovetski
2013-09-26 10:17 ` Magnus Damm
2013-09-27 0:55 ` Laurent Pinchart
2013-09-27 14:08 ` Linus Walleij
2013-09-29 6:49 ` Laurent Pinchart [this message]
2013-09-29 23:20 ` Linus Walleij
2013-09-30 11:10 ` Laurent Pinchart
2013-10-08 11:19 ` Linus Walleij
2013-10-08 14:32 ` Laurent Pinchart
2013-09-30 13:15 ` Grant Likely
2013-09-30 14:38 ` Laurent Pinchart
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=2318676.bdc47MCX2p@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.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).