From: Dinh Nguyen <dinguyen@altera.com>
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"dinh.linux@gmail.com" <dinh.linux@gmail.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@ti.com>
Subject: RE: [RFC PATCHv1] usb: dwc2: Combine the dwc2 and s3c_hsotg into a single USB DRD driver.
Date: Wed, 5 Feb 2014 00:14:22 -0600 [thread overview]
Message-ID: <1391580862.32553.10.camel@linux-builds1> (raw)
In-Reply-To: <A2CA0424C0A6F04399FB9E1CD98E03046D149949@US01WEMBX2.internal.synopsys.com>
On Wed, 2014-02-05 at 00:42 +0000, Paul Zimmerman wrote:
> > From: dinguyen@altera.com [mailto:dinguyen@altera.com]
> > Sent: Tuesday, February 04, 2014 1:46 PM
> >
> > From: Dinh Nguyen <dinguyen@altera.com>
> >
> > This means that the driver can be in host or peripheral mode when the appropriate
> > connector is used. When an A-cable is plugged in, the driver behaves in host
> > mode, and when a B-cable is used, the driver will be in peripheral mode.
> >
> > This commit:
> > - Replaces in the defines used in s3c_hsotg.h with the defines used in the dwc2
> > hw.h defines.
> > - Use the dw2_hsotg as the unified data structure for the host/gadget.
> > - Uses the dwc2 IRQ handler for host/gadget.
> > - A single spinlock.
>
> Hi Dinh,
>
> Putting all of these changes into a single patch makes them unreviewable
> as far I am concerned. You need to break this into a series of smaller
> patches. I would suggest something like this:
>
> 1 of n: Make the minimum changes to the dwc2 header files needed to
> support s3c-hsotg as a standalone driver.
> 2 of n: Make the spelling changes to s3c-hsotg.c needed to use the dwc2
> headers, and move it to the dwc2/ directory. Make the Kconfig
> and Makefile changes needed for the move. Delete s3c-hsotg.h.
> 3 of n: Move the struct defines etc. from s3c-hsotg.c to the dwc2
> header files.
> .. of n: Make the changes required to combine the functionality of
> both drivers into one. Preferably this would also be a series
> of patches instead of one big one.
>
> At each step of the series, both drivers should still compile and work.
I agree. My original thought was to also split this patch, but I just
didn't know how to split it. This is why I designated as an RFC. I was
really looking for feedback as this is the correct way to combine this
driver. I was also looking for testing purpose to make sure I did not
break anything for the s3c platform.
>
> Also, please follow the patch style used on the linux lists.
> 'git format-patch --cover-letter' should do most of this for you
> automatically.
I did use --cover-letter on this patch series.
>
> And you should probably trim the Cc list to something more reasonable.
I looked through all the commits for the dwc2 driver for the cc list. I
also CC a bunch of the Samsung people as I figured that the biggest
impact of the work would affect the s3c folks.
Dinh
next prev parent reply other threads:[~2014-02-05 6:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 21:45 [RFC PATCHv1] usb: dwc2: Combine dwc2/s3c-hsotg into a single DRD dinguyen-EIB2kfCEclfQT0dZR+AlfA
[not found] ` <1391550341-32509-1-git-send-email-dinguyen-EIB2kfCEclfQT0dZR+AlfA@public.gmane.org>
2014-02-04 21:45 ` [RFC PATCHv1] usb: dwc2: Combine the dwc2 and s3c_hsotg into a single USB DRD driver dinguyen-EIB2kfCEclfQT0dZR+AlfA
[not found] ` <1391550341-32509-2-git-send-email-dinguyen-EIB2kfCEclfQT0dZR+AlfA@public.gmane.org>
2014-02-05 0:42 ` Paul Zimmerman
2014-02-05 6:14 ` Dinh Nguyen [this message]
2014-02-05 19:20 ` Paul Zimmerman
2014-02-06 3:23 ` Jingoo Han
2014-02-12 5:34 ` Stephen Warren
2014-02-12 5:56 ` Jingoo Han
2014-02-12 6:17 ` Dinh Nguyen
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=1391580862.32553.10.camel@linux-builds1 \
--to=dinguyen@altera.com \
--cc=Paul.Zimmerman@synopsys.com \
--cc=balbi@ti.com \
--cc=dinh.linux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.