From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>,
Rao Mandadapu <quic_srivasam@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Cc: Patrick Lai <quic_plai@quicinc.com>
Subject: Re: [PATCH v2 2/7] dt-bindings: soundwire: qcom: add 16-bit sample interval
Date: Thu, 13 Apr 2023 12:12:19 +0100 [thread overview]
Message-ID: <9156affd-7f08-282b-ee65-ae82f4d94cbc@linaro.org> (raw)
In-Reply-To: <7c7afc80-713f-1949-4feb-f5f2d192569c@linaro.org>
On 12/04/2023 17:16, Krzysztof Kozlowski wrote:
> On 12/04/2023 17:28, Srinivas Kandagatla wrote:
>>
>>
>> On 03/04/2023 14:24, Krzysztof Kozlowski wrote:
>>> The port sample interval was always 16-bit, split into low and high
>>> bytes. This split was unnecessary, although harmless for older devices
>>> because all of them used only lower byte (so values < 0xff). With
>>> support for Soundwire controller on Qualcomm SM8550 and its devices,
>>> both bytes will be used, thus add a new 'qcom,ports-sinterval' property
>>> to allow 16-bit sample intervals.
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>> ---
>>> .../bindings/soundwire/qcom,soundwire.yaml | 22 +++++++++++++++++--
>>> 1 file changed, 20 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml b/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
>>> index c283c594fb5c..883b8be9be1b 100644
>>> --- a/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
>>> +++ b/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
>>> @@ -86,7 +86,7 @@ properties:
>>> qcom,ports-sinterval-low:
>>> $ref: /schemas/types.yaml#/definitions/uint8-array
>>> description:
>>> - Sample interval low of each data port.
>>> + Sample interval (only lowest byte) of each data port.
>>> Out ports followed by In ports. Used for Sample Interval calculation.
>>> Value of 0xff indicates that this option is not implemented
>>> or applicable for the respective data port.
>>> @@ -94,6 +94,19 @@ properties:
>>> minItems: 3
>>> maxItems: 16
>>>
>>> + qcom,ports-sinterval:
>>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>>
>> Should this not be ref: /schemas/types.yaml#/definitions/uint16-array ?
>
> Same answer as for Rob:
>
> Because I am afraid it will grow in next version to 24 or 32 bits. I can
> change easily maximum, but if I put here uint16-array, all DTS will have
> /bytes 16/ annotation.
>
As per MiPi Specs the sample Interval is an integer in the range 2 to
65535. I don't see a value in making this u32, other than adding some
confusion by deviating from specs.
--srini
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-04-13 11:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 13:24 [PATCH v2 0/7] soundwire: qcom: add support for SM8550 (Soundwire v2.0.0) Krzysztof Kozlowski
2023-04-03 13:24 ` [PATCH v2 1/7] dt-bindings: soundwire: qcom: add Qualcomm Soundwire v2.0.0 Krzysztof Kozlowski
2023-04-04 14:20 ` Rob Herring
2023-04-03 13:24 ` [PATCH v2 2/7] dt-bindings: soundwire: qcom: add 16-bit sample interval Krzysztof Kozlowski
2023-04-04 14:21 ` Rob Herring
2023-04-04 18:18 ` Krzysztof Kozlowski
2023-04-06 15:59 ` Rob Herring
2023-04-12 15:28 ` Srinivas Kandagatla
2023-04-12 16:16 ` Krzysztof Kozlowski
2023-04-13 11:12 ` Srinivas Kandagatla [this message]
2023-04-17 14:17 ` Krzysztof Kozlowski
2023-04-03 13:24 ` [PATCH v2 3/7] soundwire: qcom: allow 16-bit sample interval for ports Krzysztof Kozlowski
2023-04-04 18:03 ` Konrad Dybcio
2023-04-03 13:25 ` [PATCH v2 4/7] soundwire: qcom: use consistently 'ctrl' as state variable name Krzysztof Kozlowski
2023-04-04 18:07 ` Konrad Dybcio
2023-04-13 11:13 ` Srinivas Kandagatla
2023-04-03 13:25 ` [PATCH v2 5/7] soundwire: qcom: prepare for handling different register layouts Krzysztof Kozlowski
2023-04-06 13:24 ` Konrad Dybcio
2023-04-13 11:14 ` Srinivas Kandagatla
2023-04-03 13:25 ` [PATCH v2 6/7] soundwire: qcom: add support for v2.0.0 controller Krzysztof Kozlowski
2023-04-06 13:28 ` Konrad Dybcio
2023-04-13 11:27 ` Srinivas Kandagatla
2023-04-17 14:16 ` Krzysztof Kozlowski
2023-04-03 13:25 ` [PATCH v2 7/7] soundwire: qcom: use tabs for indentation in defines Krzysztof Kozlowski
2023-04-06 13:28 ` Konrad Dybcio
2023-04-13 13:11 ` 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=9156affd-7f08-282b-ee65-ae82f4d94cbc@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=quic_plai@quicinc.com \
--cc=quic_srivasam@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sanyog.r.kale@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).