From: <cy_huang@richtek.com>
To: Jonathan Cameron <jic23@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Rob Herring" <robh+dt@kernel.org>,
"ChiYuan Huang" <cy_huang@richtek.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] RTQ6056: Add compatible for the same chip family
Date: Thu, 28 Dec 2023 19:29:33 +0800 [thread overview]
Message-ID: <cover.1703762557.git.cy_huang@richtek.com> (raw)
From: ChiYuan Huang <cy_huang@richtek.com>
RTQ6053 and RTQ6059 are the same RTQ6056 family.
The differences are listed below
- RTQ6053
Only change chip package type
- RTQ6059
1. Enlarge the shunt voltage sensing range
2. Shrink the pinout for VBUS sense pin
3. Due to 1, the scale value is also changed
Since v2:
- Refine the description of 'compatible' property
ChiYuan Huang (2):
dt-bindings: iio: adc: rtq6056: add support for the whole RTQ6056
family
iio: adc: rtq6056: Add support for the whole RTQ6056 family
.../bindings/iio/adc/richtek,rtq6056.yaml | 9 +-
drivers/iio/adc/rtq6056.c | 264 +++++++++++++++++-
2 files changed, 258 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-28 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 11:29 cy_huang [this message]
2023-12-28 11:29 ` [PATCH v2 1/2] dt-bindings: iio: adc: rtq6056: add support for the whole RTQ6056 family cy_huang
2023-12-28 11:50 ` Krzysztof Kozlowski
2023-12-28 11:29 ` [PATCH v2 2/2] iio: adc: rtq6056: Add " cy_huang
2023-12-30 12:03 ` Jonathan Cameron
2024-01-02 8:30 ` ChiYuan Huang
2024-01-02 19:36 ` Jonathan Cameron
2024-01-03 1:04 ` ChiYuan Huang
2024-01-03 9:49 ` Jonathan Cameron
2024-01-02 8:39 ` 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=cover.1703762557.git.cy_huang@richtek.com \
--to=cy_huang@richtek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.