From: Brian Masney <masneyb@onstation.org>
To: andy.gross@linaro.org, sre@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, david.brown@linaro.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-soc@vger.kernel.org, jonathan@marek.ca
Subject: [PATCH RFC 0/5] treewide: add USB OTG support for hammerhead
Date: Mon, 1 Oct 2018 01:30:00 -0400 [thread overview]
Message-ID: <20181001053005.18906-1-masneyb@onstation.org> (raw)
This patch set adds USB OTG support for the LG Nexus 5 (hammerhead)
phone. My only question is related to patch #4 where the GPIO support
is added to bq24190_charger. Based on the information in the device tree
binding Documentation/devicetree/bindings/power/supply/bq24190.txt, I
should be using a gpio-hog. I'm not sure what my input pin would be for
this particular board since I can't find a publicly-available datasheet
for this board.
The USB OTG support works properly with this patch set. I am able to use
USB networking, and I'm also able to plug in a USB hub with a thumb
drive on the phone, and mount the drive.
All of the other msm8974-based boards in upstream use the
qcom,pm8941-charger (via the smbb node) that is defined in
qcom-pm8941.dtsi. USB networking works for me with that driver, however
I'm not able to get any devices connected to my USB hub to show up on
the phone, even when I port the GPIO code into that driver. I can see
the USB hub node with lsusb, but no devices on the hub.
Thanks in advance for any assistance that you can provide.
Brian Masney (1):
dt-bindings: power: supply: bq24190_charger: add bq24192 and
usb-otg-vbus
Jonathan Marek (4):
power: supply: bq24190_charger: add support for bq24192 variant
power: supply: bq24190_charger: add of_match for usb-otg-vbus
regulator
power: supply: bq24190_charger: add support for extcon and GPIO for
USB OTG support
ARM: dts: qcom: msm8974-hammerhead: add USB OTG support
.../bindings/power/supply/bq24190.txt | 7 +++
.../qcom-msm8974-lge-nexus5-hammerhead.dts | 54 +++++++++++++++++++
arch/arm/boot/dts/qcom-msm8974.dtsi | 11 ++++
drivers/power/supply/bq24190_charger.c | 51 +++++++++++++++++-
4 files changed, 121 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-01 5:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 5:30 Brian Masney [this message]
2018-10-01 5:30 ` [PATCH RFC 1/5] dt-bindings: power: supply: bq24190_charger: add bq24192 and usb-otg-vbus Brian Masney
2018-10-15 18:52 ` Rob Herring
2018-10-23 0:04 ` Brian Masney
2018-10-01 5:30 ` [PATCH RFC 2/5] power: supply: bq24190_charger: add support for bq24192 variant Brian Masney
2018-10-21 22:17 ` Sebastian Reichel
2018-10-01 5:30 ` [PATCH RFC 3/5] power: supply: bq24190_charger: add of_match for usb-otg-vbus regulator Brian Masney
2018-10-01 5:30 ` [PATCH RFC 4/5] power: supply: bq24190_charger: add support for extcon and GPIO for USB OTG support Brian Masney
2018-10-01 5:30 ` [PATCH RFC 5/5] ARM: dts: qcom: msm8974-hammerhead: add " Brian Masney
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=20181001053005.18906-1-masneyb@onstation.org \
--to=masneyb@onstation.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).