linux-kernel - [PATCH 0/2] Allow twl4030_charger to find phy reliably.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150224035809.32252.4180.stgit@notabene.brown>
Date:	Tue, 24 Feb 2015 15:01:29 +1100
From:	NeilBrown <neilb@...e.de>
To:	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Sebastian Reichel <sre@...nel.org>, Felipe Balbi <balbi@...com>
Cc:	GTA04 owners <gta04-owner@...delico.com>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-pm@...r.kernel.org
Subject: [PATCH 0/2] Allow twl4030_charger to find phy reliably.

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/