From: Felipe Balbi <balbi@kernel.org>
To: Tal Shorer <tal.shorer@gmail.com>,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
heikki.krogerus@linux.intel.com
Cc: linux-kernel@vger.kernel.org, Tal Shorer <tal.shorer@gmail.com>
Subject: Re: [PATCH v3 0/8] usb: ulpi: remove "dev" field from struct ulpi_ops
Date: Mon, 29 Aug 2016 10:58:25 +0300 [thread overview]
Message-ID: <87a8fwdn1a.fsf@linux.intel.com> (raw)
In-Reply-To: <1471363493-7836-1-git-send-email-tal.shorer@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2423 bytes --]
Hi folks,
Tal Shorer <tal.shorer@gmail.com> writes:
> 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.
>
> Changes from v2:
> * Merge patches 2 and 3 (now patch 2)
> * Merge patches 5 and 6 (now patch 4)
> * Remove comment documenting the removed dev field in struct ulpi_ops
>
> Tal Shorer (8):
> usb: ulpi: move setting of ulpi->dev parent up in ulpi_register()
> usb: ulpi: add new api functions, {read|write}_dev()
> usb: dwc3: ulpi: use new api
> usb: ulpi: remove calls to old api callbacks
> 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 have no idea how to apply these :-) Many of the patches touch dwc3,
but some touch common ulpi. Greg, is it okay if I take the entire series
and send it to you during my for-next pull request?
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-08-29 7:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 16:04 [PATCH v3 0/8] usb: ulpi: remove "dev" field from struct ulpi_ops Tal Shorer
2016-08-16 16:04 ` [PATCH v3 1/8] usb: ulpi: move setting of ulpi->dev parent up in ulpi_register() Tal Shorer
2016-08-17 11:11 ` Heikki Krogerus
2016-08-16 16:04 ` [PATCH v3 2/8] usb: ulpi: add new api functions, {read|write}_dev() Tal Shorer
2016-08-17 11:11 ` Heikki Krogerus
2016-08-16 16:04 ` [PATCH v3 3/8] usb: dwc3: ulpi: use new api Tal Shorer
2016-08-17 11:14 ` Heikki Krogerus
2016-08-16 16:04 ` [PATCH v3 4/8] usb: ulpi: remove calls to old api callbacks Tal Shorer
2016-08-17 11:14 ` Heikki Krogerus
2016-08-16 16:04 ` [PATCH v3 5/8] usb: ulpi: rename operations {read|write}_dev to simply {read|write} Tal Shorer
2016-08-17 11:15 ` Heikki Krogerus
2016-08-16 16:04 ` [PATCH v3 6/8] usb: ulpi: remove "dev" field from struct ulpi_ops Tal Shorer
2016-08-17 11:15 ` Heikki Krogerus
2016-08-16 16:04 ` [PATCH v3 7/8] usb: ulpi: make ops struct constant Tal Shorer
2016-08-17 11:16 ` Heikki Krogerus
2016-08-16 16:04 ` [PATCH v3 8/8] usb: dwc3: ulpi: make dwc3_ulpi_ops constant Tal Shorer
2016-08-17 11:17 ` Heikki Krogerus
2016-08-29 7:58 ` Felipe Balbi [this message]
2016-08-29 11:15 ` [PATCH v3 0/8] usb: ulpi: remove "dev" field from struct ulpi_ops Greg KH
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=87a8fwdn1a.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.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