From: Lina Iyer <lina.iyer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Device Tree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: How-to: Uniquely identify a DT node in the driver?
Date: Tue, 28 Jul 2015 13:56:41 -0600 [thread overview]
Message-ID: <20150728195641.GD51847@linaro.org> (raw)
In-Reply-To: <20150728193833.GC51847-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Tue, Jul 28 2015 at 13:38 -0600, Lina Iyer wrote:
>Hello,
>
>I am looking to find a way to uniquely identify a device in the driver.
>Here is an example -
>
> big: power-controller@1 {
@1 is probably not a good example here. @1 could as well be a SoC
specific phy address that the driver may not really care about.
> compatible = "soc,foo";
> ...
> };
>
> little: power-controller@2 {
> compatible = "soc,foo";
> ...
> };
>
>
>In the driver for the power-controller foo.c, would like to do -
>
> struct xyz {
> const char *name;
> ...
> };
>
> static struct xyz a = {
> .name = "big"; // To be associated with big device
> ...
> };
>
> static struct xyz b = {
> .name = "little"; // To be associated with little device
> ...
> };
>
>What would be the best way to associate the power-controller devices 'big'
>and 'little' with 'a' and 'b' respectively? A string comparison would be
>ideal but possibly can work with other ways.
>
>I could think of adding compatibles to achieve this, but was hoping to
>find something more elegant and appropriate. Or, is compatible the
>recommended way to uniquely identify devices by the driver?
>
>Thanks,
>Lina
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-28 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 19:38 How-to: Uniquely identify a DT node in the driver? Lina Iyer
[not found] ` <20150728193833.GC51847-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-28 19:56 ` Lina Iyer [this message]
2015-07-29 9:44 ` Sudeep Holla
[not found] ` <55B8A061.6060306-5wv7dgnIgG8@public.gmane.org>
2015-07-29 16:01 ` Lina Iyer
[not found] ` <20150729160120.GH51847-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-30 18:53 ` Mark Rutland
2015-07-31 15:57 ` Lina Iyer
2015-07-29 16:39 ` Mark Rutland
2015-07-30 15:33 ` Lina Iyer
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=20150728195641.GD51847@linaro.org \
--to=lina.iyer-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@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 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).