devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: David Collins <quic_collinsd@quicinc.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-arm-msm@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	David Dai <daidavid1@codeaurora.org>,
	Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: spmi: Add qcom,bus-id
Date: Mon, 7 Feb 2022 15:45:05 -0600	[thread overview]
Message-ID: <YgGS4b+8c4xmy0H5@robh.at.kernel.org> (raw)
In-Reply-To: <20220201134108.2677578-2-vkoul@kernel.org>

On Tue, 01 Feb 2022 19:11:07 +0530, Vinod Koul wrote:
> PMIC arbiter version 7 and beyond we need to define if we are using
> primary or secondary bus, so add a new property of qcom,bus-id
> 
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> ---
>  .../devicetree/bindings/spmi/qcom,spmi-pmic-arb.yaml  | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-02-07 21:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 13:41 [PATCH v3 0/2] spmi: pmic-arb: Add support for PMIC v7 Vinod Koul
2022-02-01 13:41 ` [PATCH v3 1/2] dt-bindings: spmi: Add qcom,bus-id Vinod Koul
2022-02-07 21:45   ` Rob Herring [this message]
2022-02-01 13:41 ` [PATCH v3 2/2] spmi: pmic-arb: Add support for PMIC v7 Vinod Koul
2022-06-20 19:30   ` Dmitry Baryshkov
2022-08-29 22:45   ` Dmitry Baryshkov
2022-02-22 16:53 ` [PATCH v3 0/2] " Vinod Koul
2022-05-01 19:41   ` Dmitry Baryshkov
2022-06-18 15:29     ` Dmitry Baryshkov
2022-06-28 12:46       ` Linus Walleij
2022-08-29 22:25       ` Stephen Boyd
2022-08-30  4:36         ` Vinod Koul
2022-08-30 21:11           ` Stephen Boyd
2022-09-14 11:23             ` Vinod Koul

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=YgGS4b+8c4xmy0H5@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=daidavid1@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_collinsd@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=vkoul@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 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).