From: cy_huang <u0084500@gmail.com>
To: broonie@kernel.org
Cc: lgirdwood@gmail.com, lucas_tsai@richtek.com,
linux-kernel@vger.kernel.org,
ChiYuan Huang <cy_huang@richtek.com>
Subject: [PATCH 0/2] Fix rt4831 regulator active_discharge and bypass
Date: Fri, 25 Mar 2022 09:26:15 +0800 [thread overview]
Message-ID: <1648171577-9663-1-git-send-email-u0084500@gmail.com> (raw)
From: ChiYuan Huang <cy_huang@richtek.com>
This patch series is to fix rt4831 regulator set/get active_discharge and bypass
ChiYuan Huang (2):
regulator: rt4831: Add bypass mask to fix set_bypass API work
regulator: rt4831: Add active_discharge_on to fix discharge API
drivers/regulator/rt4831-regulator.c | 3 +++
1 file changed, 3 insertions(+)
--
2.7.4
next reply other threads:[~2022-03-25 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 1:26 cy_huang [this message]
2022-03-25 1:26 ` [PATCH 1/2] regulator: rt4831: Add bypass mask to fix set_bypass API work cy_huang
2022-03-25 1:26 ` [PATCH 2/2] regulator: rt4831: Add active_discharge_on to fix discharge API cy_huang
2022-03-25 20:31 ` [PATCH 0/2] Fix rt4831 regulator active_discharge and bypass 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=1648171577-9663-1-git-send-email-u0084500@gmail.com \
--to=u0084500@gmail.com \
--cc=broonie@kernel.org \
--cc=cy_huang@richtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas_tsai@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