From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Rob Herring <robh+dt@kernel.org>
Cc: Avri Altman <avri.altman@wdc.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
DT <devicetree@vger.kernel.org>,
SCSI <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v3 5/7] dt-bindings: scsi: ufs: Add document for ufs-mediatek
Date: Thu, 14 Mar 2019 09:46:09 +0100 [thread overview]
Message-ID: <7f801bb4-97ea-1fe2-045c-507fd2656469@free.fr> (raw)
In-Reply-To: <CAL_JsqJ8EkM5EsQCCsyY0M1SuDar2qQi6QjA=91+Svv79-8rAg@mail.gmail.com>
On 13/03/2019 20:48, Rob Herring wrote:
Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt mentions:
- <name>-fixed-regulator : boolean property specifying that <name>-supply is a fixed regulator.
> There are no users of that property in tree and doesn't look like
> adding it was ever reviewed. We have standard ways to handle this and
> don't need a custom property.
FWIW, it seems to come from downstream:
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tree/?h=LE.UM.1.3.r3.25
$ git grep fixed-regulator vendor -- arch/arm/boot/dts/qcom/
vendor:arch/arm/boot/dts/qcom/msm8996.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-cdp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-interposer-sdm660-cdp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-interposer-sdm660-mtp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-mtp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-qrd-skuk.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-qrd-vr1.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-qrd.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-rumi.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-sim.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-svr20.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/msm8998-v2.1-interposer-sdm660-qrd.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm630-cdp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm630-mtp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm630-qrd.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm630-rumi.dts: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm660-cdp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm660-mtp.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm660-pm660a-rumi.dts: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm660-pm660a-sim.dts: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm660-qrd.dtsi: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm660-rumi.dts: vdd-hba-fixed-regulator;
vendor:arch/arm/boot/dts/qcom/sdm660-sim.dts: vdd-hba-fixed-regulator;
next prev parent reply other threads:[~2019-03-14 8:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 7:23 scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips Stanley Chu
[not found] ` <1551252192-535-1-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-02-27 7:23 ` [PATCH v3 0/7] " Stanley Chu
[not found] ` <1551252192-535-2-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-06 1:32 ` Stanley Chu
2019-02-27 7:23 ` [PATCH v3 1/7] scsi: ufs: Introduce ufshcd_get_pwr_dev_param Stanley Chu
2019-02-27 7:23 ` [PATCH v3 2/7] scsi: ufs-qcom: Re-factor ufshcd_get_pwr_dev_param Stanley Chu
2019-02-27 7:23 ` [PATCH v3 3/7] scsi: ufs-hisi: " Stanley Chu
2019-02-27 7:23 ` [PATCH v3 4/7] dt-bindings: phy: Add document for phy-mtk-ufs Stanley Chu
[not found] ` <1551252192-535-6-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-12 13:25 ` Rob Herring
2019-03-13 2:42 ` Stanley Chu
2019-03-13 10:27 ` Stanley Chu
2019-03-13 10:21 ` [SPAM][PATCH " Yingjoe Chen
2019-03-13 14:05 ` Stanley Chu
2019-03-13 19:52 ` Rob Herring
[not found] ` <CAL_JsqKohcSXw5BcqpQ2eVHf36kVoPdVe+rxJ+6XvdqM4nQ0Wg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-03-14 3:42 ` [PATCH " Stanley Chu
2019-02-27 7:23 ` [PATCH v3 5/7] dt-bindings: scsi: ufs: Add document for ufs-mediatek Stanley Chu
[not found] ` <1551252192-535-7-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-12 13:31 ` Rob Herring
2019-03-13 2:41 ` Stanley Chu
2019-03-13 19:48 ` Rob Herring
[not found] ` <CAL_JsqJ8EkM5EsQCCsyY0M1SuDar2qQi6QjA=91+Svv79-8rAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-03-14 3:45 ` Stanley Chu
2019-03-14 8:46 ` Marc Gonzalez [this message]
2019-03-14 16:44 ` Rob Herring
2019-03-15 4:04 ` Stanley Chu
2019-03-14 8:54 ` Marc Gonzalez
2019-02-27 7:23 ` [PATCH v3 6/7] phy: mediatek: Add UFS M-PHY driver Stanley Chu
[not found] ` <1551252192-535-8-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-01 7:13 ` Chunfeng Yun
2019-03-13 9:37 ` Yingjoe Chen
2019-03-13 10:17 ` Stanley Chu
2019-02-27 7:23 ` [PATCH v3 7/7] scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips Stanley Chu
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=7f801bb4-97ea-1fe2-045c-507fd2656469@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jhugo@codeaurora.org \
--cc=linux-scsi@vger.kernel.org \
--cc=robh+dt@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).