From: Mark Brown <broonie@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Wolfram Sang <wsa@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linus.walleij@linaro.org, Loic Poulain <loic.poulain@linaro.org>,
Robert Foss <robert.foss@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/9] dt-bindings: i2c: qcom-cci: add description of a vbus-supply property
Date: Thu, 10 Feb 2022 18:26:50 +0000 [thread overview]
Message-ID: <YgVY6t4OknBR6ySW@sirena.org.uk> (raw)
In-Reply-To: <CAA8EJprrhame0zG4=4cFF7PBS0c9synjStLBingk58y7EJfV6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Thu, Feb 10, 2022 at 09:21:42PM +0300, Dmitry Baryshkov wrote:
> Please excuse me. I missed the e-mail suggesting to move support for
> that into the core level.
No problem.
> I'd second a request to handle the adapter->bus_regulator in the core code.
> Would you be ok with the 'external-sda-scl-supply' property? Would you
> demand that it's completely handled by the core layer (including DT
> parsing) or should we let a driver parse the DT property?
I'm not super worried about how it's implemented so long as the binding
is good for the long term - if doing it in a driver helps get things
done that's fixable later on without breaking ABI.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-10 18:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 16:46 [PATCH 0/9] i2c: qcom-cci: fixes and updates Vladimir Zapolskiy
2022-02-03 16:46 ` [PATCH 1/9] dt-bindings: i2c: qcom-cci: add QCOM SM8450 compatible Vladimir Zapolskiy
2022-02-04 11:04 ` Robert Foss
2022-02-11 14:12 ` Rob Herring
2022-02-18 9:02 ` Wolfram Sang
2022-02-03 16:46 ` [PATCH 2/9] dt-bindings: i2c: qcom-cci: add description of a vbus-supply property Vladimir Zapolskiy
2022-02-04 11:06 ` Robert Foss
2022-02-04 18:05 ` Bjorn Andersson
2022-02-04 18:42 ` Mark Brown
2022-02-04 19:02 ` Bjorn Andersson
2022-02-04 19:32 ` Mark Brown
2022-02-07 14:08 ` Vladimir Zapolskiy
2022-02-07 14:39 ` Mark Brown
2022-02-07 18:31 ` Vladimir Zapolskiy
2022-02-08 12:55 ` Mark Brown
2022-02-10 15:33 ` Dmitry Baryshkov
2022-02-10 15:44 ` Mark Brown
2022-02-10 17:32 ` Dmitry Baryshkov
2022-02-10 17:36 ` Mark Brown
2022-02-10 18:21 ` Dmitry Baryshkov
2022-02-10 18:26 ` Mark Brown [this message]
2022-02-10 19:02 ` Dmitry Baryshkov
2022-02-11 17:49 ` [PATCH 0/9] i2c: qcom-cci: fixes and updates Wolfram Sang
2022-02-11 19:46 ` Vladimir Zapolskiy
2022-02-11 20:43 ` Wolfram Sang
2022-02-17 19:57 ` Wolfram Sang
2022-02-17 21:47 ` Vladimir Zapolskiy
2022-02-18 9:05 ` Wolfram Sang
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=YgVY6t4OknBR6ySW@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=wsa@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).