Thanks for the review,
On 31/05/16 00:01, Kenneth Westfield wrote:
On Fri, May 27, 2016 at 02:45:44PM +0100, Srinivas Kandagatla wrote:
This patch adds DT bindings required for msm8916 codec which is
integrated in msm8916 and apq8016 SOCs.
Codec IP is divided into two parts, first analog which is integrated
in pmic pm8916 and secondly digital part which is integrated into
application processor. Codec register controls are also split across
pmic an lpass. Analog part is controlled via spmi bus to pmic, registers
on the Application processor are memory mapped.
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@xxxxxxxxxx>
---
.../devicetree/bindings/sound/qcom,msm8916-wcd.txt | 101 +++++++++++++++++++++
1 file changed, 101 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/qcom,msm8916-wcd.txt
diff --git a/Documentation/devicetree/bindings/sound/qcom,msm8916-wcd.txt b/Documentation/devicetree/bindings/sound/qcom,msm8916-wcd.txt
new file mode 100644
index 0000000..4e3826d
--- /dev/null
+++ b/Documentation/devicetree/bindings/sound/qcom,msm8916-wcd.txt
@@ -0,0 +1,101 @@
+msm8916 audio CODEC aka Tombak audio CODEC
Please remove all mentions of "Tombak" from the patch submissions.
Sure, Will fix that in next version.
+
+Codec IP is divided into two parts, first analog which is integrated in pmic pm8916
+and secondly digital part which is integrated into application processor. Codec register
+controls are also split across pmic an lpass. Analog part is controlled via spmi bus to pmic.
+
+## Bindings for codec core on pmic:
+
+Required properties
Need to document the clocks and clock-names properties as well.
yep.
...
+
+Required properties
+ - compatible: should be "qcom,msm8916-lpass-codec" followed by "syscon".
IMO, the driver names are somewhat confusing. Perhaps,
qcom,msm8916-pmic-codec - for the codec blocks in the PMIC
Am Ok with this, naming.
qcom,msm8916-soc-codec - for the codec blocks in the SoC
But I think we can just use "qcom,msm8916-lpass-codec" for the codec
block in side the lpass, as SOC seems to be more generic term.
+ vdd-tx-rx-supply = <&pm8916_l5>;
+ vdd-micbias-supply = <&pm8916_l13>;
+ qcom,lpass-codec-core = <&lpass_codec_core>;
Is there a reason the PMIC codec holds a phandle reference to the SoC
codec node? Rather than having the SoC codec hold a ref to the PMIC
codec?
It depends, How you want to model the driver.
But in this case, most of the codec stuff like interrupts are handled in
pmic, and the lpass side of it had just few mapped registers, so making
a syscon for the lpass and accessing it in the pmic driver made more
sense for me, if not we are going to complicate the driver design.
Thanks,
srini
+ #sound-dai-cells = <1>;
+ };
+};
+
+soc {
+ ...
+ lpass_codec_core: lpass-codec{
+ compatible = "qcom,msm8916-lpass-codec", "syscon";
+ reg = <0x0771c000 0x400>;
+ };
+
+};
--
2.8.2
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
