From: cy_huang <u0084500@gmail.com>
To: robh+dt@kernel.org, heikki.krogerus@linux.intel.com
Cc: gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
cy_huang@richtek.com, will_lin@richtek.com,
th_chuang@richtek.com
Subject: [PATCH v3 0/2] Add Richtek RT1719 USBPD controller support
Date: Mon, 7 Feb 2022 23:16:08 +0800 [thread overview]
Message-ID: <1644246970-18305-1-git-send-email-u0084500@gmail.com> (raw)
From: ChiYuan Huang <cy_huang@richtek.com>
Since v3:
1. Fix checkpatch.pl consistent space error in line 332.
2. Refine some error codes to more appropriate one.
3. In psy_set_property, except prop VOLTAGE_NOW, directly return -EINVAL.
4. Use devm_kasprintf to replace devm_kzalloc and snprintf in psy_register function.
Since v2:
1. Fix below kernel test robot build warning.
>> drivers/usb/typec/rt1719.c:492:65: warning: suggest parentheses around arithmetic in operand of '|' [-Wparentheses]
492 | RT1719_EVALMODE_MASK | src_sel + 1);
| ~~~~~~~~^~~
ChiYuan Huang (2):
dt-bindings: usb: rt1719: Add binding for Richtek RT1719
usb: typec: rt1719: Add support for Richtek RT1719
.../devicetree/bindings/usb/richtek,rt1719.yaml | 85 ++
drivers/usb/typec/Kconfig | 12 +
drivers/usb/typec/Makefile | 1 +
drivers/usb/typec/rt1719.c | 970 +++++++++++++++++++++
4 files changed, 1068 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/richtek,rt1719.yaml
create mode 100644 drivers/usb/typec/rt1719.c
--
2.7.4
next reply other threads:[~2022-02-07 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 15:16 cy_huang [this message]
2022-02-07 15:16 ` [PATCH v3 1/2] dt-bindings: usb: rt1719: Add binding for Richtek RT1719 cy_huang
2022-02-07 21:59 ` Rob Herring
2022-02-07 15:16 ` [PATCH v3 2/2] usb: typec: rt1719: Add support " cy_huang
2022-02-09 12:52 ` Heikki Krogerus
2022-02-09 13:26 ` ChiYuan Huang
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=1644246970-18305-1-git-send-email-u0084500@gmail.com \
--to=u0084500@gmail.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=th_chuang@richtek.com \
--cc=will_lin@richtek.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).