From: Rob Herring <rob.herring@calxeda.com>
To: Wojciech Baranowski <baranowski@google.com>
Cc: devicetree-discuss@lists.ozlabs.org,
Grant Likely <grant.likely@secretlab.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of/platform: Allow missing address for dev name lookup
Date: Fri, 18 Nov 2011 16:12:43 -0600 [thread overview]
Message-ID: <4EC6D85B.6020005@calxeda.com> (raw)
In-Reply-To: <CAC0oEedK1E4K9mSS_pOKz_xvHtXy576kCe9oG+D3aHz14tW=WA@mail.gmail.com>
On 11/18/2011 10:45 AM, Wojciech Baranowski wrote:
> On Fri, Nov 18, 2011 at 11:10 AM, Rob Herring <rob.herring@calxeda.com> wrote:
>> On 11/18/2011 09:09 AM, Wojciech Baranowski wrote:
>>> While looking up linux name for platform device, check the address only if it
>>> has been supplied in lookup table.
>>>
>> And the reason you want to do this is?
>
> Name lookup table is used to provide names for platform devices on the
> board I'm working on. I'm adding /sound node without address for audio
> subsystem and don't want to break that convention.
auxdata is really meant to be a temporary solution to plug platform_data.
All platform devices do not necessarily go into the DT. The DT should
describe the h/w. For sound I would expect this to be all the h/w blocks
like i2s, dma, codec and then information on how they are connected. Can
you show what your sound binding looks like.
Rob
>
>>> Signed-off-by: Wojciech Baranowski <baranowski@chromium.org>
>>> ---
>>> drivers/of/platform.c | 8 +++++---
>>> 1 files changed, 5 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/of/platform.c b/drivers/of/platform.c
>>> index cbd5d70..94763c0 100644
>>> --- a/drivers/of/platform.c
>>> +++ b/drivers/of/platform.c
>>> @@ -314,12 +314,14 @@ static const struct of_dev_auxdata *of_dev_lookup(const struct of_dev_auxdata *l
>>> if (!lookup)
>>> return NULL;
>>>
>>> - for(; lookup->name != NULL; lookup++) {
>>> + for (; lookup->name != NULL; lookup++) {
>>> if (!of_device_is_compatible(np, lookup->compatible))
>>> continue;
>>> - if (of_address_to_resource(np, 0, &res))
>>> + if (lookup->phys_addr &&
>>> + of_address_to_resource(np, 0, &res))
>>> continue;
>>> - if (res.start != lookup->phys_addr)
>>> + if (lookup->phys_addr &&
>>> + res.start != lookup->phys_addr)
>>> continue;
>>> pr_debug("%s: devname=%s\n", np->full_name, lookup->name);
>>> return lookup;
>>
>>
prev parent reply other threads:[~2011-11-18 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 15:09 [PATCH] of/platform: Allow missing address for dev name lookup Wojciech Baranowski
2011-11-18 16:10 ` Rob Herring
2011-11-18 16:45 ` Wojciech Baranowski
2011-11-18 22:12 ` Rob Herring [this message]
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=4EC6D85B.6020005@calxeda.com \
--to=rob.herring@calxeda.com \
--cc=baranowski@google.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@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).