linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Allow use of DVS GPIOs on the RK808 PMIC variant only
Date: Mon, 14 Oct 2024 12:43:38 +0200	[thread overview]
Message-ID: <cover.1728902488.git.dsimic@manjaro.org> (raw)

This is a small series that primarily makes the rk808-regulator driver
more compliant to the DT bindings, by allowing use of DVS GPIOs on the
RK808 variant only.  There's no point in allowing that on the other PMIC
variants, because they don't support the DVS GPIOs, and it goes against
the DT bindings to allow a possibly misplaced "dvs-gpios" property to
actually be handled in the rk808-regulator driver.

This series also cleans up the code a bit, improves some comments, and
replaces dev_err() with dev_err_probe(), where appropriate.

Dragan Simic (3):
  regulator: rk808: Perform trivial code cleanups
  regulator: rk808: Use dev_err_probe() in the probe path
  regulator: rk808: Restrict DVS GPIOs to the RK808 variant only

 drivers/regulator/rk808-regulator.c | 41 +++++++++++++----------------
 1 file changed, 19 insertions(+), 22 deletions(-)



             reply	other threads:[~2024-10-14 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 10:43 Dragan Simic [this message]
2024-10-14 10:43 ` [PATCH 1/3] regulator: rk808: Perform trivial code cleanups Dragan Simic
2024-10-14 10:43 ` [PATCH 2/3] regulator: rk808: Use dev_err_probe() in the probe path Dragan Simic
2024-10-14 10:43 ` [PATCH 3/3] regulator: rk808: Restrict DVS GPIOs to the RK808 variant only Dragan Simic
2024-10-22 18:45 ` [PATCH 0/3] Allow use of DVS GPIOs on the RK808 PMIC " 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=cover.1728902488.git.dsimic@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.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 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).