linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jung Daehwan <dh10.jung@samsung.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	"open list:USB XHCI DRIVER" <linux-usb@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Howard Yen <howardyen@google.com>, Puma Hsu <pumahsu@google.com>,
	"J . Avila" <elavila@google.com>,
	sc.suh@samsung.com, Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v4 4/5] usb: host: add some to xhci overrides for xhci-exynos
Date: Wed, 27 Apr 2022 11:37:12 +0200	[thread overview]
Message-ID: <YmkOyDT+ejWMHB7k@kroah.com> (raw)
In-Reply-To: <20220427091901.GC145620@ubuntu>

On Wed, Apr 27, 2022 at 06:19:01PM +0900, Jung Daehwan wrote:
> On Tue, Apr 26, 2022 at 12:23:30PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Apr 26, 2022 at 06:18:47PM +0900, Daehwan Jung wrote:
> > > Co-processor needs some information about connected usb device.
> > > It's proper to pass information after usb device gets address when
> > > getting "Set Address" command. It supports vendors to implement it
> > > using xhci overrides. There're several power scenarios depending
> > > on vendors. It gives vendors flexibilty to meet their power requirement.
> > > They can override suspend and resume of root hub.
> > > 
> > > Signed-off-by: Daehwan Jung <dh10.jung@samsung.com>
> > > ---
> > >  drivers/usb/host/xhci.c | 6 ++++++
> > >  drivers/usb/host/xhci.h | 4 ++++
> > >  2 files changed, 10 insertions(+)
> > > 
> > > diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> > > index 5ccf1bbe8732..8b3df1302650 100644
> > > --- a/drivers/usb/host/xhci.c
> > > +++ b/drivers/usb/host/xhci.c
> > > @@ -5555,6 +5555,12 @@ void xhci_init_driver(struct hc_driver *drv,
> > >  			drv->check_bandwidth = over->check_bandwidth;
> > >  		if (over->reset_bandwidth)
> > >  			drv->reset_bandwidth = over->reset_bandwidth;
> > > +		if (over->address_device)
> > > +			drv->address_device = over->address_device;
> > > +		if (over->bus_suspend)
> > > +			drv->bus_suspend = over->bus_suspend;
> > > +		if (over->bus_resume)
> > > +			drv->bus_resume = over->bus_resume;
> > >  	}
> > >  }
> > >  EXPORT_SYMBOL_GPL(xhci_init_driver);
> > > diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
> > > index 3a414a2f41f0..5bc621e77762 100644
> > > --- a/drivers/usb/host/xhci.h
> > > +++ b/drivers/usb/host/xhci.h
> > > @@ -1947,6 +1947,9 @@ struct xhci_driver_overrides {
> > >  			     struct usb_host_endpoint *ep);
> > >  	int (*check_bandwidth)(struct usb_hcd *, struct usb_device *);
> > >  	void (*reset_bandwidth)(struct usb_hcd *, struct usb_device *);
> > > +	int (*address_device)(struct usb_hcd *hcd, struct usb_device *udev);
> > > +	int (*bus_suspend)(struct usb_hcd *hcd);
> > > +	int (*bus_resume)(struct usb_hcd *hcd);
> > >  };
> > >  
> > >  #define	XHCI_CFC_DELAY		10
> > > @@ -2103,6 +2106,7 @@ int xhci_drop_endpoint(struct usb_hcd *hcd, struct usb_device *udev,
> > >  		       struct usb_host_endpoint *ep);
> > >  int xhci_check_bandwidth(struct usb_hcd *hcd, struct usb_device *udev);
> > >  void xhci_reset_bandwidth(struct usb_hcd *hcd, struct usb_device *udev);
> > > +int xhci_address_device(struct usb_hcd *hcd, struct usb_device *udev);
> > 
> > You do not use this function in this change, why include it in here?
> > 
> > Please reorganize your patch series to only include what you need for
> > each step, as-is it's kind of out-of-order and might not build at each
> > step along the way (or it might, it's hard to determine...)
> > 
> 
> This patch is to add function pointers. xhci-exynos or other user could use it.

But this commit has nothing to do with xhci_address_device(), why add it
to the .h file here?

> If I reorganize them as you said, all patches depend on xhci-exynos.

Of course, we need real users of the functions you export, otherwise
they do not need to be exported.

You can export them in one commit, and then use them in the next, but
that's not what you are doing here at all.  You have a mix of .c and .h
changes across different commits that are not coordinated at all.

> That's because hooks and override are only used in xhci-exynos for now.
> I don't want user driver effects common files like xhci platform.
> I've tried removing dependancies.. That's why I split patches like that.

Splitting patches is the correct way, just do it so that it makes sense.
As you can see by the kbuild reports, what you have here is not correct.

thanks,

greg k-h

  reply	other threads:[~2022-04-27 11:06 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220426092019epcas2p2ef5dfde273edaaadc2ff74414f1b2c7a@epcas2p2.samsung.com>
2022-04-26  9:18 ` [PATCH v4 0/5] add xhci-exynos driver Daehwan Jung
2022-04-26  9:18   ` [PATCH v4 1/5] usb: host: export symbols for xhci-exynos to use xhci hooks Daehwan Jung
2022-04-26  9:54     ` Greg Kroah-Hartman
2022-04-26 10:27       ` Jung Daehwan
2022-04-26 10:31         ` Greg Kroah-Hartman
2022-04-26 18:40           ` Greg Kroah-Hartman
2022-04-28  3:30             ` Jung Daehwan
2022-04-26 16:02     ` kernel test robot
2022-04-26  9:18   ` [PATCH v4 2/5] usb: host: add xhci hooks for xhci-exynos Daehwan Jung
2022-04-26 10:19     ` Greg Kroah-Hartman
2022-04-27  9:06       ` Jung Daehwan
2022-04-27  9:19         ` Greg Kroah-Hartman
2022-04-28  3:23           ` Jung Daehwan
2022-04-28  5:30             ` Greg Kroah-Hartman
2022-04-26  9:18   ` [PATCH v4 3/5] usb: host: xhci-plat: support override of hc driver Daehwan Jung
2022-04-26 10:20     ` Greg Kroah-Hartman
2022-04-27  9:07       ` Jung Daehwan
2022-04-26  9:18   ` [PATCH v4 4/5] usb: host: add some to xhci overrides for xhci-exynos Daehwan Jung
2022-04-26 10:23     ` Greg Kroah-Hartman
2022-04-27  9:19       ` Jung Daehwan
2022-04-27  9:37         ` Greg Kroah-Hartman [this message]
2022-04-26  9:18   ` [PATCH v4 5/5] usb: host: add xhci-exynos driver Daehwan Jung
2022-04-26 10:20     ` Greg Kroah-Hartman
2022-04-28  3:26       ` Jung Daehwan
2022-04-26 10:21     ` Greg Kroah-Hartman
2022-04-27  9:24       ` Jung Daehwan
2022-04-27  9:37         ` Greg Kroah-Hartman
2022-04-26 12:59     ` Krzysztof Kozlowski
2022-04-28  1:29       ` Jung Daehwan
2022-04-28  5:19         ` Krzysztof Kozlowski
2022-04-28  6:36           ` Jung Daehwan
2022-04-28  6:45             ` Greg Kroah-Hartman
2022-04-28  7:45               ` Jung Daehwan
2022-04-28  7:31             ` Krzysztof Kozlowski
2022-04-28  7:53               ` Jung Daehwan
2022-04-28  8:26                 ` Krzysztof Kozlowski
2022-04-26 17:55     ` kernel test robot
2022-04-27 16:25     ` Mathias Nyman
2022-04-28  3:03       ` Jung Daehwan
2022-04-28 12:28         ` Mathias Nyman
2022-05-03  8:41           ` Jung Daehwan
2022-04-28  5:15       ` Jung Daehwan
2022-04-26 10:19   ` [PATCH v4 0/5] " Greg Kroah-Hartman
2022-04-26 12:46   ` Krzysztof Kozlowski
2022-04-27  9:49     ` Jung Daehwan
2022-04-27 18:24       ` Krzysztof Kozlowski
2022-04-28  3:19         ` Jung Daehwan

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=YmkOyDT+ejWMHB7k@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dh10.jung@samsung.com \
    --cc=elavila@google.com \
    --cc=howardyen@google.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=pumahsu@google.com \
    --cc=sc.suh@samsung.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).