From: Felipe Balbi <balbi@ti.com>
To: "suresh.gupta@freescale.com" <suresh.gupta@freescale.com>
Cc: "balbi@ti.com" <balbi@ti.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: fsl: Add FSL USB Gadget entry in platform device id
Date: Fri, 14 Mar 2014 20:40:15 -0500 [thread overview]
Message-ID: <20140315014015.GD31520@saruman.home> (raw)
In-Reply-To: <71f42b215c58414d8bfa7efb968dadbf@BN1PR03MB251.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
On Fri, Mar 14, 2014 at 08:52:19PM +0000, suresh.gupta@freescale.com wrote:
> Hi,
> Thanks for reviewing my patches.
> Please find my comments inline
>
> -----Original Message-----
> From: Felipe Balbi [mailto:balbi@ti.com]
> Sent: Thursday, March 13, 2014 8:56 PM
> To: Gupta Suresh-B42813
> Cc: balbi@ti.com; gregkh@linuxfoundation.org; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org; Gupta Suresh-B42813
> Subject: Re: [PATCH] usb: gadget: fsl: Add FSL USB Gadget entry in platform device id
>
> On Thu, Mar 13, 2014 at 07:35:31PM +0530, Suresh Gupta wrote:
> > From: Suresh Gupta <B42813@freescale.com>
> >
> > Add FSL USB Gadget entry in platform device id table
>
> why this tab ?
> [SuresH] I will remove it in next version.
>
> > Signed-off-by: Suresh Gupta <B42813@freescale.com>
> > ---
> > drivers/usb/gadget/fsl_udc_core.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/usb/gadget/fsl_udc_core.c b/drivers/usb/gadget/fsl_udc_core.c
> > index b7dea4e..35b20e6 100644
> > --- a/drivers/usb/gadget/fsl_udc_core.c
> > +++ b/drivers/usb/gadget/fsl_udc_core.c
> > @@ -2654,6 +2654,8 @@ static const struct platform_device_id fsl_udc_devtype[] = {
> > }, {
> > .name = "imx-udc-mx51",
> > }, {
> > + .name = "fsl-usb2-udc",
>
> why aren't you just using chipidea ?
> [SuresH] This is our legacy driver for all previous and existing ppc
> socs. Many of our customers are already using this, and we need to
> support them on this driver. We do have plans to shift to chipidea,
> but after some time.
cool, you already have plans, so we will see a new glue layer for v3.16
right ? Which means I don't need to take this patch either.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-03-15 1:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 14:05 Suresh Gupta
2014-03-13 15:26 ` Felipe Balbi
2014-03-14 20:52 ` suresh.gupta
2014-03-15 1:40 ` Felipe Balbi [this message]
2014-03-19 14:25 ` suresh.gupta
2014-03-19 16:51 ` gregkh
2014-03-19 18:03 ` suresh.gupta
2014-03-20 5:43 ` suresh.gupta
2014-03-20 15:01 ` suresh.gupta
2014-03-20 16:02 ` gregkh
2014-03-20 16:06 ` Felipe Balbi
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=20140315014015.GD31520@saruman.home \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=suresh.gupta@freescale.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
all inboxes | Powered by JetHome®