From: Felipe Balbi <balbi@ti.com>
To: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>
Cc: "Balbi, Felipe" <balbi@ti.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH v5 02/11] usb: musb: kill global and static for multi instance
Date: Thu, 26 Jul 2012 16:06:14 +0300 [thread overview]
Message-ID: <20120726130613.GA2378@arwen.pp.htv.fi> (raw)
In-Reply-To: <47CEF8C4B26E8C44B22B028A650E0EA93EAF41EB@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Thu, Jul 26, 2012 at 12:46:43PM +0000, Gupta, Ajay Kumar wrote:
> Hi,
> > > > > On Wed, Jul 25, 2012 at 05:42:06PM +0530, Ajay Kumar Gupta wrote:
> > > > > > @@ -240,20 +238,24 @@ int __devinit musb_init_debugfs(struct musb
> > > *musb)
> > > > > > struct dentry *root;
> > > > > > struct dentry *file;
> > > > > > int ret;
> > > > > > + char name[10];
> > > > > >
> > > > > > - root = debugfs_create_dir("musb", NULL);
> > > > > > + sprintf(name, "musb%d", musb->id);
> > > > > > + root = debugfs_create_dir(name, NULL);
> > > > >
> > > > > I told you to use dev_name(musb) for a reason. See what happens when
> > > > > you use dev_name(musb);
> > > > >
> > > > > Do you not think about the other users of this driver ? Do you not
> > > > > know what's the ID on platform_devices which "don't have an ID" ??
> > > >
> > > > We are now using musb_ida for all glue layers so '-1' issue will not
> > come.
> > >
> > > true.
> > >
> > > > Still if we can manage without 'id' then better to do that way.
> > >
> > > just make sure to notice that directory name will "musb.0".
>
> It creates musb-hdrc.0 and musb-hdrc.1 as glue layers use "musb-hdrc"
> name in platform_device_alloc() call.
yes, indeed. That shouldn't be a problem though... what do you think ?
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-26 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:12 [PATCH v5 02/11] usb: musb: kill global and static for multi instance Ajay Kumar Gupta
[not found] ` <1343218326-30610-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2012-07-26 7:40 ` Felipe Balbi
[not found] ` <20120726074057.GH29029-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-07-26 8:25 ` Gupta, Ajay Kumar
[not found] ` <47CEF8C4B26E8C44B22B028A650E0EA93EAEF790-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-07-26 8:25 ` Felipe Balbi
[not found] ` <20120726082459.GP29029-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-07-26 8:29 ` Gupta, Ajay Kumar
[not found] ` <47CEF8C4B26E8C44B22B028A650E0EA93EAEF877-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-07-26 12:46 ` Gupta, Ajay Kumar
2012-07-26 13:06 ` Felipe Balbi [this message]
[not found] ` <20120726130613.GA2378-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-07-26 13:16 ` Gupta, Ajay Kumar
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=20120726130613.GA2378@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=ajay.gupta@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).