From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
ChiYuan Huang <cy_huang@richtek.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v3 0/2] regulator: richtek,rt4801: parse GPIOs per regulator
Date: Mon, 25 Apr 2022 09:24:53 +0200 [thread overview]
Message-ID: <20220425072455.27356-1-krzysztof.kozlowski@linaro.org> (raw)
Hi,
Not tested.
Follow up of discussion:
https://lore.kernel.org/all/2d124d53-1f36-5315-3877-af8f8ad5f824@linaro.org/#t
Changes since v2
================
Patch 2: Do not use core's ena_gpiod feature because of lost voltage issue
(ChiYuan Huang).
Changes since v1
================
Patch 1: add review tag.
Patch 2: Check for ena_gpio_state before accessing I2C (issue pointed out by
ChiYuan Huang).
Best regards,
Krzysztof
Krzysztof Kozlowski (2):
regulator: dt-bindings: richtek,rt4801: use existing ena_gpiod feature
regulator: richtek,rt4801: parse GPIOs per regulator
.../regulator/richtek,rt4801-regulator.yaml | 14 +++++-
drivers/regulator/rt4801-regulator.c | 49 ++++++++++++++-----
2 files changed, 51 insertions(+), 12 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-25 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 7:24 Krzysztof Kozlowski [this message]
2022-04-25 7:24 ` [PATCH v3 1/2] regulator: dt-bindings: richtek,rt4801: use existing ena_gpiod feature Krzysztof Kozlowski
2022-04-25 7:24 ` [PATCH v3 2/2] regulator: richtek,rt4801: parse GPIOs per regulator Krzysztof Kozlowski
2022-04-25 7:58 ` ChiYuan Huang
2022-04-25 8:01 ` Krzysztof Kozlowski
2022-04-25 8:08 ` ChiYuan Huang
2022-04-25 8:50 ` ChiYuan Huang
2022-04-25 15:01 ` [PATCH v3 0/2] " Mark Brown
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=20220425072455.27356-1-krzysztof.kozlowski@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 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.