From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
nikolaus.voss@loewensteinmedical.de,
andriy.shevchenko@linux.intel.com, garsilva@embeddedor.com,
keescook@chromium.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Subject: [PATCH v2 0/1] Add USB role switch to tps6598x
Date: Thu, 7 May 2020 22:59:37 +0100 [thread overview]
Message-ID: <20200507215938.1983363-1-bryan.odonoghue@linaro.org> (raw)
V2:
- Updates the git commit to include a link to the TI document which
describes firmware configuration - Andy
- Pads out the description a bit to include information on baking the
data-role into the firmware with the referenced utility.
V1:
This patch - adds USB role switching to the TI TPS6598x. It has been tested
out with a ChipIdea controller inside a Qualcomm MSM8939.
Right now you need to have configured the TPS firmware with the TI
configuration tool so that the chip knows if it should initiate or accept
data and power role swaps.
https://www.ti.com/lit/an/slva843a/slva843a.pdf
Heikki mentioned that on the ACPI systems the firmware had been
pre-configured to do data/power role swaps. On the hardware I have this is
the case also, which is why I did't invest more time in adding DT bindings
to control data/power roles that I don't need or necessarily support with
the reference hardware.
As-is this code will do role-swappping nicely for me, and I think should be
safe on existing ACPI systems.
Bryan O'Donoghue (1):
usb: typec: tps6598x: Add USB role switching logic
drivers/usb/typec/tps6598x.c | 56 +++++++++++++++++++++++++++++++-----
1 file changed, 49 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2020-05-07 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 21:59 Bryan O'Donoghue [this message]
2020-05-07 21:59 ` [PATCH v2] usb: typec: tps6598x: Add USB role switching logic Bryan O'Donoghue
2020-05-11 10:46 ` 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=20200507215938.1983363-1-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=garsilva@embeddedor.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nikolaus.voss@loewensteinmedical.de \
/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).