public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tal Shorer <tal.shorer@gmail.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	USB list <linux-usb@vger.kernel.org>,
	"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
	balbi@kernel.org
Subject: Re: [PATCH v2 00/10] usb: ulpi: remove "dev" field from struct ulpi_ops
Date: Tue, 9 Aug 2016 18:43:05 +0200	[thread overview]
Message-ID: <20160809164305.GB29539@kroah.com> (raw)
In-Reply-To: <CAFDyS3PxNKkZcU8mLHsRxtuSkrT3aWu3zWOKpLd1o5EgEsk0fQ@mail.gmail.com>

On Tue, Aug 09, 2016 at 06:55:18PM +0300, Tal Shorer wrote:
> On Tue, Aug 9, 2016 at 5:04 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Aug 01, 2016 at 09:15:48PM +0300, Tal Shorer wrote:
> >> struct ulpi_ops is defined as follows:
> >>
> >> struct ulpi_ops {
> >>         struct device *dev;
> >>         int (*read)(struct ulpi_ops *ops, u8 addr);
> >>         int (*write)(struct ulpi_ops *ops, u8 addr, u8 val);
> >> };
> >>
> >> Upon calling ulpi_register_interface(), the struct device argument is
> >> put inside the struct ulpi_ops argument's dev field. Later, when
> >> calling the actual read()/write() operations, the struct ulpi_ops is
> >> passed to them and they use the stored device to access whatever
> >> private data they need.
> >>
> >> This means that if one wishes to reuse the same oprations for multiple
> >> interfaces (e.g if we have multiple instances of the same controller),
> >> any but the last interface registered will not operate properly (and
> >> the one that does work will be at the mercy of the others to not mess
> >> it up).
> >>
> >> I understand that barely any driver uses this bus right now, but I
> >> suppose it's there to be used at some point. We might as well fix the
> >> design here before we hit this bug.
> >>
> >> This series fixes this by passing the given struct device directly to
> >> the operation functions via ulpi->dev.parent in ulpi_read() and
> >> ulpi_write(). It also changes the operations struct to be constant
> >> since now nobody has a reason to modify it.
> >>
> >> Changes from v1:
> >>  * Split the actual api change into multiple patch as per Felipe Balbi's
> >>    suggestion. The series now first adds the new api, then migrates
> >>    everything to use and only then removes the old api.
> >>
> >> Tal Shorer (10):
> >>   usb: ulpi: move setting of ulpi->dev parent up in ulpi_register()
> >>   usb: ulpi: add new api functions, {read|write}_dev()
> >>   usb: ulpi: use new api functions if available
> >>   usb: dwc3: ulpi: use new api
> >>   usb: ulpi: remove calls to old api callbacks
> >>   usb: ulpi: remove old api callbacks from struct ulpi_ops
> >>   usb: ulpi: rename operations {read|write}_dev to simply {read|write}
> >>   usb: ulpi: remove "dev" field from struct ulpi_ops
> >>   usb: ulpi: make ops struct constant
> >>   usb: dwc3: ulpi: make dwc3_ulpi_ops constant
> >
> > I'd like to get Heikki's ack for this series...
> Anything to do on my end except waiting?

Wait another week or so, if no response, I'll queue it up for 4.9-rc1 :)

thanks,

greg k-h

  reply	other threads:[~2016-08-09 16:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 18:15 [PATCH v2 00/10] usb: ulpi: remove "dev" field from struct ulpi_ops Tal Shorer
2016-08-01 18:15 ` [PATCH v2 01/10] usb: ulpi: move setting of ulpi->dev parent up in ulpi_register() Tal Shorer
2016-08-01 18:15 ` [PATCH v2 02/10] usb: ulpi: add new api functions, {read|write}_dev() Tal Shorer
2016-08-01 18:15 ` [PATCH v2 03/10] usb: ulpi: use new api functions if available Tal Shorer
2016-08-16 10:55   ` Heikki Krogerus
2016-08-01 18:15 ` [PATCH v2 04/10] usb: dwc3: ulpi: use new api Tal Shorer
2016-08-01 18:15 ` [PATCH v2 05/10] usb: ulpi: remove calls to old api callbacks Tal Shorer
2016-08-01 18:15 ` [PATCH v2 06/10] usb: ulpi: remove old api callbacks from struct ulpi_ops Tal Shorer
2016-08-16 10:55   ` Heikki Krogerus
2016-08-01 18:15 ` [PATCH v2 07/10] usb: ulpi: rename operations {read|write}_dev to simply {read|write} Tal Shorer
2016-08-01 18:15 ` [PATCH v2 08/10] usb: ulpi: remove "dev" field from struct ulpi_ops Tal Shorer
2016-08-16 10:58   ` Heikki Krogerus
2016-08-01 18:15 ` [PATCH v2 09/10] usb: ulpi: make ops struct constant Tal Shorer
2016-08-01 18:15 ` [PATCH v2 10/10] usb: dwc3: ulpi: make dwc3_ulpi_ops constant Tal Shorer
2016-08-09 14:04 ` [PATCH v2 00/10] usb: ulpi: remove "dev" field from struct ulpi_ops Greg KH
2016-08-09 15:55   ` Tal Shorer
2016-08-09 16:43     ` Greg KH [this message]
2016-08-15 12:02 ` Heikki Krogerus

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=20160809164305.GB29539@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@kernel.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tal.shorer@gmail.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