All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	linux-arm-msm@vger.kernel.org,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] regulator: fix pm8009 bindings on sm8250
Date: Mon, 4 Jan 2021 11:26:21 +0530	[thread overview]
Message-ID: <20210104055621.GD120946@vkoul-mobl> (raw)
In-Reply-To: <20201231122348.637917-1-dmitry.baryshkov@linaro.org>

On 31-12-20, 15:23, Dmitry Baryshkov wrote:
> 
> PM8009 has special revision (P=1), which is to be used for sm8250
> platform. The major difference is the S2 regulator which supplies 0.95 V
> instead of 2.848V. Declare regulators data to be used for this chip
> revision. The datasheet calls the chip just pm8009-1, so use the same
> name.

Thanks, this looks sane to me:

Reviewed-by: Vinod Koul <vkoul@kernel.org>

-- 
~Vinod

  parent reply	other threads:[~2021-01-04  5:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 12:23 [PATCH 0/4] regulator: fix pm8009 bindings on sm8250 Dmitry Baryshkov
2020-12-31 12:23 ` [PATCH 1/4] dt-bindings: regulator: qcom,rpmh-regulator: add pm8009 revision Dmitry Baryshkov
2020-12-31 12:23 ` [PATCH 2/4] regulator: qcom-rpmh-regulator: correct hfsmps515 definition Dmitry Baryshkov
2020-12-31 12:23 ` [PATCH 3/4] regulator: qcom-rpmh-regulator: add pm8009-1 chip revision Dmitry Baryshkov
2020-12-31 12:23 ` [PATCH 4/4] arm64: dts: qcom: qrb5165-rb5: fix pm8009 regulators Dmitry Baryshkov
2021-01-04  5:56 ` Vinod Koul [this message]
2021-01-04 17:40 ` [PATCH 0/4] regulator: fix pm8009 bindings on sm8250 Mark Brown
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm

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=20210104055621.GD120946@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.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.