From: govinds@codeaurora.org
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH v2] dt: bindings: add bindings for wcn3990 wifi block
Date: Tue, 10 Apr 2018 22:31:47 +0530 [thread overview]
Message-ID: <db67dc847fb6c0e05609455d023eb43d@codeaurora.org> (raw)
In-Reply-To: <20180219184046.pr6b7r5x5um22vim@rob-hp-laptop>
Thanks Rob for the review comments. I have addressed the review comments
in [PATCH v2 13/13] dt: bindings: add bindings for wcn3990 wifi block.
>> diff --git
>> a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> index 3d2a031..e34d8f8 100644
>> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> @@ -4,6 +4,7 @@ Required properties:
>> - compatible: Should be one of the following:
>> * "qcom,ath10k"
>> * "qcom,ipq4019-wifi"
>> + * "qcom,wcn3990-wifi"
>>
>> PCI based devices uses compatible string "qcom,ath10k" and takes
>> calibration
>> data along with board specific data via
>> "qcom,ath10k-calibration-data".
>> @@ -18,8 +19,11 @@ In general, entry
>> "qcom,ath10k-pre-calibration-data" and
>> "qcom,ath10k-calibration-data" conflict with each other and only one
>> can be provided per device.
>>
>> +SNOC based devices (i.e. wcn3990) uses compatible string
>> "qcom,wcn3990-wifi".
>> +
>> Optional properties:
>> - reg: Address and length of the register set for the device.
>> +- reg-names: Names of the memory regions defined in reg entry.
>
> You must define what the names are and how many (so reg needs updating
> too if there is more than 1).
>
> Though with only 1 -names, it is kind of pointless.
Updated the names.
>
>> - resets: Must contain an entry for each entry in reset-names.
>> See ../reset/reseti.txt for details.
>> - reset-names: Must include the list of following reset names,
>> @@ -49,6 +53,12 @@ Optional properties:
>> hw versions.
>> - qcom,ath10k-pre-calibration-data : pre calibration data as an
>> array,
>> the length can vary between hw versions.
>> +- qcom,<supply-name>-supply: handle to the regulator device tree node
>> + optional "supply-name" is "vdd-0.8-cx-mx".
>
> You can drop the qcom prefix. Just name this "vdd-0.8-cx-mx-supply".
Updated the same.
>> +- qcom,<supply>-config: Specifies voltage levels for supply. Should
>> be
>> + specified in pairs (min, max), units uV. There can
>> + be optional load in uA and Regulator settle delay in
>> + uS.
>
> We have standard regulator properties for this I think.
Removed the supply config.
>>
>> Example (to supply the calibration data alone):
>>
>> @@ -119,3 +129,28 @@ wifi0: wifi@a000000 {
>> qcom,msi_base = <0x40>;
>> qcom,ath10k-pre-calibration-data = [ 01 02 03 ... ];
>> };
>> +
>> +Example (to supply wcn3990 SoC wifi block details):
>> +
>> +qcom,msm_ath10k@18000000 {
>
> wifi@...
Updated the same.
>
>> + compatible = "qcom,wcn3990-wifi";
>> + reg = <0x18800000 0x800000>;
>> + reg-names = "membase";
>> + clocks = <&clock_gcc clk_aggre2_noc_clk>;
>> + clock-names = "smmu_aggre2_noc_clk"
>> + interrupts =
>> + <0 130 0 /* CE0 */ >,
>> + <0 131 0 /* CE1 */ >,
>> + <0 132 0 /* CE2 */ >,
>> + <0 133 0 /* CE3 */ >,
>> + <0 134 0 /* CE4 */ >,
>> + <0 135 0 /* CE5 */ >,
>> + <0 136 0 /* CE6 */ >,
>> + <0 137 0 /* CE7 */ >,
>> + <0 138 0 /* CE8 */ >,
>> + <0 139 0 /* CE9 */ >,
>> + <0 140 0 /* CE10 */ >,
>> + <0 141 0 /* CE11 */ >;
>> + qcom,vdd-0.8-cx-mx-supply = <&pm8998_l5>;
>> + qcom,vdd-0.8-cx-mx-config = <800000 800000 2400 1000>;
>> +};
>> --
>> 1.9.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: govinds@codeaurora.org
To: Rob Herring <robh@kernel.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt: bindings: add bindings for wcn3990 wifi block
Date: Tue, 10 Apr 2018 22:31:47 +0530 [thread overview]
Message-ID: <db67dc847fb6c0e05609455d023eb43d@codeaurora.org> (raw)
In-Reply-To: <20180219184046.pr6b7r5x5um22vim@rob-hp-laptop>
Thanks Rob for the review comments. I have addressed the review comments
in [PATCH v2 13/13] dt: bindings: add bindings for wcn3990 wifi block.
>> diff --git
>> a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> index 3d2a031..e34d8f8 100644
>> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> @@ -4,6 +4,7 @@ Required properties:
>> - compatible: Should be one of the following:
>> * "qcom,ath10k"
>> * "qcom,ipq4019-wifi"
>> + * "qcom,wcn3990-wifi"
>>
>> PCI based devices uses compatible string "qcom,ath10k" and takes
>> calibration
>> data along with board specific data via
>> "qcom,ath10k-calibration-data".
>> @@ -18,8 +19,11 @@ In general, entry
>> "qcom,ath10k-pre-calibration-data" and
>> "qcom,ath10k-calibration-data" conflict with each other and only one
>> can be provided per device.
>>
>> +SNOC based devices (i.e. wcn3990) uses compatible string
>> "qcom,wcn3990-wifi".
>> +
>> Optional properties:
>> - reg: Address and length of the register set for the device.
>> +- reg-names: Names of the memory regions defined in reg entry.
>
> You must define what the names are and how many (so reg needs updating
> too if there is more than 1).
>
> Though with only 1 -names, it is kind of pointless.
Updated the names.
>
>> - resets: Must contain an entry for each entry in reset-names.
>> See ../reset/reseti.txt for details.
>> - reset-names: Must include the list of following reset names,
>> @@ -49,6 +53,12 @@ Optional properties:
>> hw versions.
>> - qcom,ath10k-pre-calibration-data : pre calibration data as an
>> array,
>> the length can vary between hw versions.
>> +- qcom,<supply-name>-supply: handle to the regulator device tree node
>> + optional "supply-name" is "vdd-0.8-cx-mx".
>
> You can drop the qcom prefix. Just name this "vdd-0.8-cx-mx-supply".
Updated the same.
>> +- qcom,<supply>-config: Specifies voltage levels for supply. Should
>> be
>> + specified in pairs (min, max), units uV. There can
>> + be optional load in uA and Regulator settle delay in
>> + uS.
>
> We have standard regulator properties for this I think.
Removed the supply config.
>>
>> Example (to supply the calibration data alone):
>>
>> @@ -119,3 +129,28 @@ wifi0: wifi@a000000 {
>> qcom,msi_base = <0x40>;
>> qcom,ath10k-pre-calibration-data = [ 01 02 03 ... ];
>> };
>> +
>> +Example (to supply wcn3990 SoC wifi block details):
>> +
>> +qcom,msm_ath10k@18000000 {
>
> wifi@...
Updated the same.
>
>> + compatible = "qcom,wcn3990-wifi";
>> + reg = <0x18800000 0x800000>;
>> + reg-names = "membase";
>> + clocks = <&clock_gcc clk_aggre2_noc_clk>;
>> + clock-names = "smmu_aggre2_noc_clk"
>> + interrupts =
>> + <0 130 0 /* CE0 */ >,
>> + <0 131 0 /* CE1 */ >,
>> + <0 132 0 /* CE2 */ >,
>> + <0 133 0 /* CE3 */ >,
>> + <0 134 0 /* CE4 */ >,
>> + <0 135 0 /* CE5 */ >,
>> + <0 136 0 /* CE6 */ >,
>> + <0 137 0 /* CE7 */ >,
>> + <0 138 0 /* CE8 */ >,
>> + <0 139 0 /* CE9 */ >,
>> + <0 140 0 /* CE10 */ >,
>> + <0 141 0 /* CE11 */ >;
>> + qcom,vdd-0.8-cx-mx-supply = <&pm8998_l5>;
>> + qcom,vdd-0.8-cx-mx-config = <800000 800000 2400 1000>;
>> +};
>> --
>> 1.9.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-04-10 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 4:43 [PATCH v2] dt: bindings: add bindings for wcn3990 wifi block Govind Singh
2018-02-16 4:43 ` Govind Singh
2018-02-16 4:43 ` Govind Singh
2018-02-19 18:40 ` Rob Herring
2018-02-19 18:40 ` Rob Herring
2018-02-19 18:40 ` Rob Herring
2018-04-10 17:01 ` govinds [this message]
2018-04-10 17:01 ` govinds
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=db67dc847fb6c0e05609455d023eb43d@codeaurora.org \
--to=govinds@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh@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 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.