From: Sergei Shtylyov <sshtylyov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
To: balbi-l0cyMroinI0@public.gmane.org
Cc: Sergei Shtylyov
<sshtylyov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>,
"Kalliguddi, Hema" <hemahk-l0cyMroinI0@public.gmane.org>,
Kevin Hilman
<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
"Cousson, Benoit" <b-cousson-l0cyMroinI0@public.gmane.org>,
Paul Walmsley <paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org>,
Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v4] usb: musb: Adding names for IRQs in resource structure
Date: Fri, 10 Dec 2010 16:35:14 +0300 [thread overview]
Message-ID: <4D022C92.7090308@ru.mvista.com> (raw)
In-Reply-To: <20101210132053.GN6027-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
Hello.
On 10-12-2010 16:20, Felipe Balbi wrote:
>>>>>> The resource data is getting automatically populated from a set of data
>>>>>> generated from TI's hardware database for the OMAP platform, While we
>>>>>> could hack in some exceptions to that tool to generate resources
>>>>>> in a specific order, it seems less fragile to use the resource name
>>>>>> instead.That way, no matter what order the resources are generated, the
>>>>>> driver still work.
>>>>>> Modified the OMAP,Blackfin and Davinci architecture files to add the name
>>>>>> of the IRQs
>>>>>> in the resource structures and musb driver to use the get_irq_byname()
>>>>>> api to
>>>>>> get the device and dma irq numbers instead of using the index.
>>>>>> Signed-off-by: Hema HK<hemahk-l0cyMroinI0@public.gmane.org>
>>>>>> Cc: Felipe Balbi<balbi-l0cyMroinI0@public.gmane.org>
>>>>>> Cc: Tony Lindgren<tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
>>>>>> Cc: Kevin Hilman<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
>>>>>> Cc: Cousson, Benoit<b-cousson-l0cyMroinI0@public.gmane.org>
>>>>>> Cc: Paul Walmsley<paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org>
>>>>>> Cc: Mike Frysinger<vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
>>>>>> ---
>>>>> For the davinci changes:
>>>>> Acked-by: Kevin Hilman<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
>>>>> Kevin
>>>> [...]
>>>>>> Index: linux-omap-pm/arch/arm/mach-davinci/usb.c
>>>>>> ===================================================================
>>>>>> --- linux-omap-pm.orig/arch/arm/mach-davinci/usb.c
>>>>>> +++ linux-omap-pm/arch/arm/mach-davinci/usb.c
>>>>>> @@ -64,10 +64,12 @@ static struct resource usb_resources[] =
>>>>>> {
>>>>>> .start = IRQ_USBINT,
>>>>>> .flags = IORESOURCE_IRQ,
>>>>>> + .name = "mc"
>>>>>> },
>>>>>> {
>>>>>> /* placeholder for the dedicated CPPI IRQ */
>>>>>> .flags = IORESOURCE_IRQ,
>>>>>> + .name = "dma"
>>>>>> },
>>>>>> };
>>>> Argh! This failed to also modify da8xx_usb20_resources[]... :-(
>>> I think when I posted these patch, da8xx support was not there in mainline.
>> No, it was added long ago, before the glue layer itself.
>>> I will send patch to add this.
>> I will care about this myself now.
> Thanks, send me the patch and I'll put to the same branch.
I was thinking about pushing this thru the DaVinci tree. Well, I'll post
to both lists and let you figure out who will apply it... :-)
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" 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:[~2010-12-10 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 16:26 [PATCH v4] usb: musb: Adding names for IRQs in resource structure Hema HK
2010-09-29 6:59 ` Felipe Balbi
2010-09-29 8:54 ` Kalliguddi, Hema
2010-09-29 10:11 ` Felipe Balbi
2010-09-29 11:38 ` Kalliguddi, Hema
2010-09-29 13:48 ` Mike Frysinger
[not found] ` <1285777599-24245-1-git-send-email-hemahk-l0cyMroinI0@public.gmane.org>
2010-09-29 14:40 ` Kevin Hilman
2010-12-09 19:34 ` Sergei Shtylyov
[not found] ` <4D012F2C.9060303-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2010-12-10 4:46 ` Kalliguddi, Hema
[not found] ` <AANLkTimF3Eotqa+jZvzCJStguGrDEeS9V-XUGOTa9qBt-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-10 12:56 ` Sergei Shtylyov
[not found] ` <4D02237B.2070708-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2010-12-10 13:20 ` Kalliguddi, Hema
2010-12-10 13:20 ` Felipe Balbi
[not found] ` <20101210132053.GN6027-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2010-12-10 13:35 ` Sergei Shtylyov [this message]
[not found] ` <4D022C92.7090308-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2010-12-10 13:58 ` Felipe Balbi
2010-12-10 16:43 ` Sergei Shtylyov
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=4D022C92.7090308@ru.mvista.com \
--to=sshtylyov-igf4poytycdqt0dzr+alfa@public.gmane.org \
--cc=b-cousson-l0cyMroinI0@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=hemahk-l0cyMroinI0@public.gmane.org \
--cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@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).