From: Georgi Djakov <gdjakov@mm-sol.com>
To: Bjorn Andersson <bjorn@kryo.se>
Cc: linux-mmc@vger.kernel.org, cjb@laptop.org,
grant.likely@linaro.org, rob.herring@calxeda.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Asutosh Das <asutoshd@codeaurora.org>,
Venkat Gopalakrishnan <venkatg@codeaurora.org>,
Sahitya Tummala <stummala@codeaurora.org>,
Subhash Jadavani <subhashj@codeaurora.org>
Subject: Re: [PATCH] mmc: sdhci-msm: Add support for MSM chipsets
Date: Wed, 31 Jul 2013 18:14:06 +0300 [thread overview]
Message-ID: <51F929BE.1050505@mm-sol.com> (raw)
In-Reply-To: <CAJAp7OgOT82G=W8RpDvaogskUmAN26CWq4gKUs45RwOeU8pXvQ@mail.gmail.com>
On 07/31/2013 03:19 AM, Bjorn Andersson wrote:
> On Tue, Jul 30, 2013 at 8:22 AM, Georgi Djakov <gdjakov@mm-sol.com> wrote:
>> This platform driver adds the support of Secure Digital Host
>> Controller Interface compliant controller in MSM chipsets.
>>
>> [snip]
>> +
>> + sdhc_1: qcom,sdhc@f9824900 {
>> + compatible = "qcom,sdhci-msm";
>> + reg = <0xf9824900 0x11c>, <0xf9824000 0x800>;
>> + reg-names = "hc_mem", "core_mem";
>> + interrupts = <0 123 0>, <0 138 0>;
>> + interrupt-names = "hc_irq", "pwr_irq";
>> +
>> + vdd-supply = <&pm8941_l21>;
>> + vdd-io-supply = <&pm8941_l13>;
>> + qcom,vdd-voltage-level = <2950000 2950000>;
>> + qcom,vdd-current-level = <9000 800000>;
>> +
>> + qcom,vdd-io-always-on;
>> + qcom,vdd-io-lpm-sup;
>> + qcom,vdd-io-voltage-level = <1800000 2950000>;
>> + qcom,vdd-io-current-level = <6 22000>;
>> +
>> + bus-width = <4>;
>> + non-removable;
>> + qcom,bus-speed-mode = "HS200_1p8v", "DDR_1p8v";
>> +
>> + gpios = <&msmgpio 40 0>, /* CLK */
>> + <&msmgpio 39 0>, /* CMD */
>> + <&msmgpio 38 0>, /* DATA0 */
>> + <&msmgpio 37 0>, /* DATA1 */
>> + <&msmgpio 36 0>, /* DATA2 */
>> + <&msmgpio 35 0>; /* DATA3 */
>> + qcom,gpio-names = "CLK", "CMD", "DAT0", "DAT1", "DAT2", "DAT3";
>
> I believe these gpio references (and in the rest of the patch) should
> be replaced by pinctrl. As far as I can see it provides what you want
> and gives you configurability and potential sleep states of those pins
> nicely integrated.
>
Thanks! I'll make it use the pinctrl driver that is coming too.
BR,
Georgi
WARNING: multiple messages have this Message-ID (diff)
From: gdjakov@mm-sol.com (Georgi Djakov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: sdhci-msm: Add support for MSM chipsets
Date: Wed, 31 Jul 2013 18:14:06 +0300 [thread overview]
Message-ID: <51F929BE.1050505@mm-sol.com> (raw)
In-Reply-To: <CAJAp7OgOT82G=W8RpDvaogskUmAN26CWq4gKUs45RwOeU8pXvQ@mail.gmail.com>
On 07/31/2013 03:19 AM, Bjorn Andersson wrote:
> On Tue, Jul 30, 2013 at 8:22 AM, Georgi Djakov <gdjakov@mm-sol.com> wrote:
>> This platform driver adds the support of Secure Digital Host
>> Controller Interface compliant controller in MSM chipsets.
>>
>> [snip]
>> +
>> + sdhc_1: qcom,sdhc at f9824900 {
>> + compatible = "qcom,sdhci-msm";
>> + reg = <0xf9824900 0x11c>, <0xf9824000 0x800>;
>> + reg-names = "hc_mem", "core_mem";
>> + interrupts = <0 123 0>, <0 138 0>;
>> + interrupt-names = "hc_irq", "pwr_irq";
>> +
>> + vdd-supply = <&pm8941_l21>;
>> + vdd-io-supply = <&pm8941_l13>;
>> + qcom,vdd-voltage-level = <2950000 2950000>;
>> + qcom,vdd-current-level = <9000 800000>;
>> +
>> + qcom,vdd-io-always-on;
>> + qcom,vdd-io-lpm-sup;
>> + qcom,vdd-io-voltage-level = <1800000 2950000>;
>> + qcom,vdd-io-current-level = <6 22000>;
>> +
>> + bus-width = <4>;
>> + non-removable;
>> + qcom,bus-speed-mode = "HS200_1p8v", "DDR_1p8v";
>> +
>> + gpios = <&msmgpio 40 0>, /* CLK */
>> + <&msmgpio 39 0>, /* CMD */
>> + <&msmgpio 38 0>, /* DATA0 */
>> + <&msmgpio 37 0>, /* DATA1 */
>> + <&msmgpio 36 0>, /* DATA2 */
>> + <&msmgpio 35 0>; /* DATA3 */
>> + qcom,gpio-names = "CLK", "CMD", "DAT0", "DAT1", "DAT2", "DAT3";
>
> I believe these gpio references (and in the rest of the patch) should
> be replaced by pinctrl. As far as I can see it provides what you want
> and gives you configurability and potential sleep states of those pins
> nicely integrated.
>
Thanks! I'll make it use the pinctrl driver that is coming too.
BR,
Georgi
next prev parent reply other threads:[~2013-07-31 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 16:22 [PATCH] mmc: sdhci-msm: Add support for MSM chipsets Georgi Djakov
2013-07-30 16:22 ` Georgi Djakov
2013-07-30 16:40 ` Chris Ball
2013-07-30 16:40 ` Chris Ball
2013-07-30 17:17 ` David Brown
2013-07-30 17:17 ` David Brown
2013-07-31 0:19 ` Bjorn Andersson
2013-07-31 0:19 ` Bjorn Andersson
2013-07-31 15:14 ` Georgi Djakov [this message]
2013-07-31 15:14 ` Georgi Djakov
2013-08-13 14:06 ` [PATCH RFC v2] " Georgi Djakov
2013-08-13 14:06 ` Georgi Djakov
2013-08-15 7:22 ` Ivan T. Ivanov
2013-08-15 7:22 ` Ivan T. Ivanov
2013-08-16 8:11 ` Georgi Djakov
2013-08-16 8:11 ` Georgi Djakov
2013-08-19 7:27 ` Jaehoon Chung
2013-08-19 7:27 ` Jaehoon Chung
2013-08-19 8:35 ` Georgi Djakov
2013-08-19 8:35 ` Georgi Djakov
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=51F929BE.1050505@mm-sol.com \
--to=gdjakov@mm-sol.com \
--cc=asutoshd@codeaurora.org \
--cc=bjorn@kryo.se \
--cc=cjb@laptop.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=stummala@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=venkatg@codeaurora.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.