From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, vkoul@kernel.org
Cc: sanyog.r.kale@intel.com, yung-chuan.liao@linux.intel.com,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 1/5] soundwire: qcom: add support to missing transport params
Date: Wed, 3 Mar 2021 10:16:46 -0600 [thread overview]
Message-ID: <de3b8223-f51d-6cb1-6346-7bd7dcefb482@linux.intel.com> (raw)
In-Reply-To: <d0dc4c6f-cbd5-06e8-6ed8-234a55f9de9c@linaro.org>
> soundwire-controller@3210000 {
> reg = <0 0x3210000 0 0x2000>;
> compatible = "qcom,soundwire-v1.5.1";
> interrupts = <GIC_SPI 298 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&rxmacro>;
> clock-names = "iface";
> qcom,clock-stop-mode0;
> qcom,din-ports = <0>;
> qcom,dout-ports = <5>;
>
> qcom,ports-sinterval-low = /bits/ 8 <0x03 0x1F 0x1F 0x07 0x00>;
> qcom,ports-offset1 = /bits/ 8 <0x00 0x00 0x0B 0x01 0x00>;
> qcom,ports-offset2 = /bits/ 8 <0x00 0x00 0x0B 0x00 0x00>;
> qcom,ports-hstart = /bits/ 8 <0xFF 0x03 0xFF 0xFF 0xFF>;
> qcom,ports-hstop = /bits/ 8 <0xFF 0x06 0xFF 0xFF 0xFF>;
> qcom,ports-word-length = /bits/ 8 <0x01 0x07 0x04 0xFF 0xFF>;
> qcom,ports-block-pack-mode = /bits/ 8 <0xFF 0x00 0x01 0xFF 0xFF>;
> qcom,ports-lane-control = /bits/ 8 <0x01 0x00 0x00 0x00 0x00>;
> qcom,ports-block-group-count = /bits/ 8 <0xFF 0xFF 0xFF 0xFF 0x00>;
>
> #sound-dai-cells = <1>;
> #address-cells = <2>;
> #size-cells = <0>;
> };
>> properties that may or may not be valid. If this is intentional and
>> desired, this should still be captured somehow, e.g. in the bindings
>> documentation or in the code with a comment, no?
>
> Yes, I agree with you on this, I should document this in bindings!
thanks for the explanations, it'd be useful indeed to document what this
magic 0xFF value means.
next prev parent reply other threads:[~2021-03-04 0:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 15:58 [PATCH v2 0/5] soundwire: qcom: various improvements Srinivas Kandagatla
2021-02-26 15:58 ` [PATCH v2 1/5] soundwire: qcom: add support to missing transport params Srinivas Kandagatla
2021-02-26 16:45 ` Pierre-Louis Bossart
2021-03-02 10:13 ` Srinivas Kandagatla
2021-03-02 14:29 ` Pierre-Louis Bossart
2021-03-03 9:36 ` Srinivas Kandagatla
2021-03-03 16:16 ` Pierre-Louis Bossart [this message]
2021-02-26 15:58 ` [PATCH v2 2/5] soundwire: qcom: set continue execution flag for ignored commands Srinivas Kandagatla
2021-02-26 15:58 ` [PATCH v2 3/5] soundwire: qcom: start the clock during initialization Srinivas Kandagatla
2021-02-26 15:58 ` [PATCH v2 4/5] soundwire: qcom: update register read/write routine Srinivas Kandagatla
2021-02-26 15:58 ` [PATCH v2 5/5] soundwire: qcom: add support to new interrupts 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=de3b8223-f51d-6cb1-6346-7bd7dcefb482@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.com \
/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
Powered by JetHome