From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"Brown, Len" <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: driver model, duplicate names question
Date: Tue, 16 Jul 2013 09:44:59 -0700 [thread overview]
Message-ID: <20130716164459.GB17827@kroah.com> (raw)
In-Reply-To: <51E57631.2030805@linux.intel.com>
On Tue, Jul 16, 2013 at 09:34:57AM -0700, Srinivas Pandruvada wrote:
> Hi Greg,
>
> I would like to create tree like structure using device model (struct
> device, device_register/device_unregister) using parent/child
> relationship while creation. I want to be able to create duplicate
> names, when their parents are different, similar to a directory structure.
> I see that I can't create devices with duplicate names (device names),
> even when their parents are different.
We actually check that? Nice, I didn't realize that :)
> How can I allow duplicate names when their parents are different devices?
> I want to avoid flat model as I have parent child relationship and there
> will be too many devices using flat model.
Devices on the same bus shouldn't have the same name, but if they are in
a "tree", it should be ok. What check is erroring out?
> Why, I need?
> I am going to publish RFC for a new power cap class driver. We have a
> multiple controllers under power cap class (they are devices). Under
> which there are multiple power zones, with parent/child relationships.
> Currently I have to use kobject_init_and_add, which I want to avoid and
> just use device_register. Other places, wherever such relationships are
> required, kobjects are used like cpufreq.
Yes, you shouldn't use "raw" kobject calls at all, so we should fix
this.
thanks,
greg k-h
next prev parent reply other threads:[~2013-07-16 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 16:34 driver model, duplicate names question Srinivas Pandruvada
2013-07-16 16:44 ` Greg KH [this message]
2013-07-16 18:29 ` Srinivas Pandruvada
2013-07-16 18:31 ` Greg KH
2013-07-16 18:54 ` Srinivas Pandruvada
2013-07-16 19:04 ` Greg KH
2013-07-16 19:33 ` Srinivas Pandruvada
2013-07-16 19:32 ` Greg KH
2013-07-16 20:11 ` Srinivas Pandruvada
[not found] ` <51E6D95B.1070203@linux.intel.com>
2013-07-17 17:48 ` Greg KH
2013-07-17 18:09 ` Srinivas Pandruvada
2013-07-17 18:31 ` Greg KH
2013-07-17 18:55 ` Srinivas Pandruvada
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=20130716164459.GB17827@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=srinivas.pandruvada@linux.intel.com \
/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