From: Pin-yen Lin <treapking@chromium.org>
To: heikki.krogerus@linux.intel.com, robh+dt@kernel.org
Cc: gregkh@linuxfoundation.org, linux@roeck-us.net,
linux-usb@vger.kernel.org, linux-imx@nxp.com, jun.li@nxp.com,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chen-Yu Tsai <wenst@chromium.org>,
Wei-Shun Chang <weishunc@chromium.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Pi-Hsun Shih <pihsun@chromium.org>,
Prashant Malani <pmalani@chromium.org>,
xu.yang_2@nxp.com, shawnguo@kernel.org, andy@kernel.org,
dmitry.torokhov@gmail.com
Subject: Suggestions for allowing drivers to detect USB Type-C MUX (switch)
Date: Fri, 15 Apr 2022 19:10:36 +0800 [thread overview]
Message-ID: <CAEXTbpeD+UaExc7qSU8idUgW7jaEP4FZXbFY==saYcNDO_AsUg@mail.gmail.com> (raw)
Hi all,
We would like to submit a patch series to allow drivers to detect USB
Type-C orientation/mux changes, but we received different opinions
from the maintainers and we are not sure how to proceed. I am sending
out this email to start the discussion and collect your feedback.
In previous works[1] by Jun, Rob suggested using general mux
controller drivers to support this. But, in later patches, Heikki
suggested moving the logic into Type-C MUX controllers
(drivers/usb/typec/mux.c).
Could anyone please suggest a direction for this patch series?
Please let me know if I misunderstood the background.
Best regards,
Pin-yen
[1]: https://patchwork.kernel.org/project/linux-usb/list/?series=484785&state=%2A&archive=both
[2]: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/1604403610-16577-1-git-send-email-jun.li@nxp.com/
[3]: https://patchwork.kernel.org/project/linux-usb/patch/1621408490-23811-4-git-send-email-jun.li@nxp.com/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-04-15 11:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAEXTbpeD+UaExc7qSU8idUgW7jaEP4FZXbFY==saYcNDO_AsUg@mail.gmail.com' \
--to=treapking@chromium.org \
--cc=andy@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hsinyi@chromium.org \
--cc=jun.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pihsun@chromium.org \
--cc=pmalani@chromium.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=weishunc@chromium.org \
--cc=wenst@chromium.org \
--cc=xu.yang_2@nxp.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;
as well as URLs for NNTP newsgroup(s).