From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/8] arm64: dts: qcom: apq8016-sbc: add usb support
Date: Mon, 22 Feb 2016 10:20:13 +0000 [thread overview]
Message-ID: <56CAE0DD.304@linaro.org> (raw)
In-Reply-To: <20160222055124.GG21240@tuxbot>
Thanks for the review,
On 22/02/16 05:51, Bjorn Andersson wrote:
> On Wed 10 Feb 03:36 PST 2016, Srinivas Kandagatla wrote:
>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>> ---
>> arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi | 15 ++++++++++
>> arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 35 ++++++++++++++++++++++
>> 2 files changed, 50 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi b/arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi
>> index cbeee0b..4a79dd9 100644
>> --- a/arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi
>> @@ -10,4 +10,19 @@
>> output-low;
>> };
>> };
>> +
>> + usb_id_default: usb_id_default {
>
> Labels are built with _, node names with -.
>
>> + pinmux {
>> + function = "gpio";
>> + pins = "gpio121";
>> + };
>
> You don't need a separate node to specify function...
>
>> +
>> + pinconf {
>> + pins = "gpio121";
>> + function = "gpio";
>
> ...but if you really want it, then you shouldn't specify the function
> here.
Oops, Will remove this and resend the patch.
>
>> + drive-strength = <8>;
>> + input-enable;
>> + bias-pull-up;
>> + };
>> + };
>> };
>> diff --git a/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi b/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi
> [..]
>> +
>> + usb_id: usb-id {
>> + interrupt-parent = <&msmgpio>;
>
> interrupt-parent is part of specifying an interrupt. You're not doing
> that here, so no need to specify a parent.
Yep, will clean this up in next version.
>
>> + compatible = "linux,extcon-usb-gpio";
>> + id-gpio = <&msmgpio 121 GPIO_ACTIVE_HIGH>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&usb_id_default>;
>> };
>> };
>
> Apart from these two nits
>
> Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Thanks,
srini
>
> Regards,
> Bjorn
>
next prev parent reply other threads:[~2016-02-22 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 11:36 [PATCH v2 0/8] arm64: dts: apq8016 dt patches (Set2) Srinivas Kandagatla
2016-02-10 11:36 ` [PATCH v2 1/8] arm64: dts: qcom: add manual pullup setting to otg Srinivas Kandagatla
2016-02-10 11:36 ` [PATCH v2 2/8] arm64: dts: qcom: apq8016-sbc: add usb support Srinivas Kandagatla
2016-02-22 5:51 ` Bjorn Andersson
2016-02-22 10:20 ` Srinivas Kandagatla [this message]
2016-02-10 11:36 ` [PATCH v2 3/8] arm64: dts: qcom: add audio pinctrls Srinivas Kandagatla
2016-02-10 11:36 ` [PATCH v2 4/8] arm64: dts: qcom: add lpass node Srinivas Kandagatla
2016-02-10 11:37 ` [PATCH v2 5/8] arm64: dts: qcom: apq8016-sbc: enable lpass on DB410c Srinivas Kandagatla
2016-02-10 11:37 ` [PATCH v2 6/8] arm64: dts: qcom: fix usb digital voltage levels Srinivas Kandagatla
2016-02-10 11:37 ` [PATCH v2 7/8] arm64: dts: qcom: apq8016-sbc: enable bam dma node Srinivas Kandagatla
2016-02-10 11:37 ` [PATCH v2 8/8] arm64: dts: qcom: Fix MPP's function used for LED control Srinivas Kandagatla
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=56CAE0DD.304@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).