From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] of/platform: Initialise dev->fwnode appropriately
Date: Thu, 15 Sep 2016 08:36:57 -0500 [thread overview]
Message-ID: <20160915133657.GB14424@rob-hp-laptop> (raw)
In-Reply-To: <38259ab3716da072fab37f06d034329244491c13.1473865096.git.robin.murphy@arm.com>
On Wed, Sep 14, 2016 at 04:01:24PM +0100, Robin Murphy wrote:
> Whilst we're some of the way towards a universal firmware property
> interface, drivers which deal with both OF and ACPI probing end up
> having to do things like this:
>
> dev->of_node ? &dev->of_node->fwnode : dev->fwnode
>
> This seems unnecessary, when the OF code could instead simply fill in
> the device's fwnode when binding the of_node, and let the drivers use
> dev->fwnode either way. Let's give it a go and see what falls out.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> drivers/of/platform.c | 2 ++
> 1 file changed, 2 insertions(+)
I've applied this, but what about non-platform devices such as i2c?
Rob
next prev parent reply other threads:[~2016-09-15 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 15:01 [PATCH] of/platform: Initialise dev->fwnode appropriately Robin Murphy
2016-09-15 13:36 ` Rob Herring [this message]
2016-09-16 11:12 ` Lorenzo Pieralisi
2016-09-16 12:07 ` Robin Murphy
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=20160915133657.GB14424@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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