From: NeilBrown <neilb@suse.de>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Woodhouse <dwmw2@infradead.org>,
Sebastian Reichel <sre@kernel.org>, Felipe Balbi <balbi@ti.com>
Cc: GTA04 owners <gta04-owner@goldelico.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: [PATCH 0/2] Allow twl4030_charger to find phy reliably.
Date: Tue, 24 Feb 2015 15:01:29 +1100 [thread overview]
Message-ID: <20150224035809.32252.4180.stgit@notabene.brown> (raw)
The twl4030_charger is physically paired with the twl4030 USB phy,
so the drivers need to be able to reliably find each other.
twl4030_charger currently uses usb_get_phy(), which works if there is
only one phy to choose from, but is not reliable in more complex
configurations.
These patches add a new interface to allow a phy to be found given a
device node, and then use that interface in twl4030_charger so that
it finds its sibling in the devicetree, and gets the phy associated
with that.
Thanks,
NeilBrown
---
NeilBrown (2):
usb: phy: Add interface to get phy give of device_node.
twl4030_charger: find associated phy by more reliable means.
drivers/power/twl4030_charger.c | 21 ++++----
drivers/usb/phy/phy.c | 97 ++++++++++++++++++++++++++++-----------
include/linux/usb/phy.h | 2 +
3 files changed, 81 insertions(+), 39 deletions(-)
--
Signature
next reply other threads:[~2015-02-24 4:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 4:01 NeilBrown [this message]
2015-02-24 4:01 ` [PATCH 1/2] usb: phy: Add interface to get phy give of device_node NeilBrown
2015-02-24 4:01 ` [PATCH 2/2] twl4030_charger: find associated phy by more reliable means NeilBrown
2015-02-25 21:13 ` Sebastian Reichel
2015-03-04 9:14 ` NeilBrown
2015-03-02 21:05 ` [PATCH 0/2] Allow twl4030_charger to find phy reliably Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2015-03-22 22:52 NeilBrown
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=20150224035809.32252.4180.stgit@notabene.brown \
--to=neilb@suse.de \
--cc=balbi@ti.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=gta04-owner@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sre@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 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).