linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>,
	vkoul@kernel.org, agross@kernel.org, andersson@kernel.org,
	robh+dt@kernel.org, broonie@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	quic_rohkumar@quicinc.com, srinivas.kandagatla@linaro.org,
	dianders@chromium.org, swboyd@chromium.org,
	judyhsiao@chromium.org, alsa-devel@alsa-project.org,
	quic_rjendra@quicinc.com, konrad.dybcio@somainline.org,
	mka@chromium.org
Cc: Ratna Deepthi Kudaravalli <quic_rkudarav@quicinc.com>
Subject: Re: [PATCH v5 4/4] dt-bindings: soundwire: Convert text bindings to DT Schema
Date: Tue, 8 Nov 2022 14:49:58 +0100	[thread overview]
Message-ID: <2a2385a0-0055-aeff-cd7c-71270dd4e561@linaro.org> (raw)
In-Reply-To: <b8175f2a-0096-80d4-5733-26ce9f7fd437@quicinc.com>

On 08/11/2022 14:29, Srinivasa Rao Mandadapu wrote:
>>> +  qcom,ports-block-pack-mode:
>>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>>> +    description: Indicate the block packing mode.
>>> +                 0 to indicate Blocks are per Channel
>>> +                 1 to indicate Blocks are per Port.
>>> +                 Out ports followed by In ports.
>>> +                 Value of 0xFF indicates that this option is not implemented
>>> +                 or applicable for the respective data port.
>>> +                 More info in MIPI Alliance SoundWire 1.0 Specifications.
>>> +    minItems: 3
>>> +    maxItems: 8
>>> +
>>> +  qcom,ports-hstart:
>>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>>> +    description: Identifying lowerst numbered coloum in
>>> +                 SoundWire Frame, i.e. left edge of the Transport sub-frame
>>> +                 for each port. Values between 0 and 15 are valid.
>> minimum: 0
>> maximum: 15
>> and drop that one sentence.
>>
>> The same in other places.
> 
> As below mentioned it will also have 0xFF value. I think we can't 
> restrict with minimum and maximum values.
> 
> Please suggest if my understanding is wrong.

Then (and it is actually an array):
minItems: 3
maxItems: 5
items:
  oneOf:
    - minimum: 0
      maximum: 15
    - const: 0xff

> 
>>
>>> +                 Out ports followed by In ports.
>>> +                 Value of 0xFF indicates that this option is not implemented
>>> +                 or applicable for the respective data port.
>>> +                 More info in MIPI Alliance SoundWire 1.0 Specifications.
>>> +    minItems: 3
>>> +    maxItems: 5
>>> +
>>> +  qcom,ports-hstop:
>>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>>> +    description: Identifying highest numbered coloum in
>>> +                 SoundWire Frame, i.e. the right edge of the Transport
>>> +                 sub-frame for each port. Values between 0 and 15 are valid.
>>> +                 Out ports followed by In ports.
>>> +                 Value of 0xFF indicates that this option is not implemented
>>> +                 or applicable for the respective data port.
>>> +                 More info in MIPI Alliance SoundWire 1.0 Specifications.
>>> +    minItems: 3
>>> +    maxItems: 5
>>> +
>>> +  qcom,ports-block-group-count:
>>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>>> +    description: In range 1 to 4 to indicate how many sample
>>> +                 intervals are combined into a payload.
>>> +                 Out ports followed by In ports.
>>> +                 Value of 0xFF indicates that this option is not implemented
>>> +                 or applicable for the respective data port.
>>> +                 More info in MIPI Alliance SoundWire 1.0 Specifications.
>>> +    minItems: 3
>>> +    maxItems: 5
>>> +
>>> +  label:
>>> +    maxItems: 1
>>> +
>>> +patternProperties:
>>> +  "^.*@[0-9a-f],[0-9a-f]$":
>>> +    type: object
>>> +    description: Child nodes for a standalone audio codec or speaker amplifier IC.
>>> +                 It has RX and TX Soundwire slave devices.
>> s/slave/secondary/
>>
>> This is some odd indentation. Please use standard, like example-schema
>> is showing, so:
>>
>>      description:
>>        Child nodes for a standalone audio codec or speaker amplifier IC.
>>        RX and TX Soundwire slave devices.
>>
>> It looks you used such pattern in other places here - they should also
>> be corrected.
> Okay. Will change accordingly.
>>
>>> +    properties:
>>> +      compatible:
>>> +        pattern: "^sdw[0-9a-f]{1}[0-9a-f]{4}[0-9a-f]{4}[0-9a-f]{2}$"
>>> +
>>
>> Best regards,
>> Krzysztof
>>

Best regards,
Krzysztof


      reply	other threads:[~2022-11-08 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 12:39 [PATCH v5 0/4] Convert soundwire bindings to DT schema Srinivasa Rao Mandadapu
2022-11-08 12:39 ` [PATCH v5 1/4] arm64: dts: qcom: Update soundwire slave node names Srinivasa Rao Mandadapu
2022-11-08 12:46   ` Krzysztof Kozlowski
2022-11-08 12:39 ` [PATCH v5 2/4] arm64: dts: qcom: sm8250: Remove redundant soundwire property Srinivasa Rao Mandadapu
2022-11-08 12:47   ` Krzysztof Kozlowski
2022-11-08 12:39 ` [PATCH v5 3/4] arm64: dts: qcom: sc7280: " Srinivasa Rao Mandadapu
2022-11-08 12:48   ` Krzysztof Kozlowski
2022-11-08 12:39 ` [PATCH v5 4/4] dt-bindings: soundwire: Convert text bindings to DT Schema Srinivasa Rao Mandadapu
2022-11-08 12:45   ` Krzysztof Kozlowski
2022-11-08 13:29     ` Srinivasa Rao Mandadapu
2022-11-08 13:49       ` Krzysztof Kozlowski [this message]

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=2a2385a0-0055-aeff-cd7c-71270dd4e561@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=andersson@kernel.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=judyhsiao@chromium.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=quic_rjendra@quicinc.com \
    --cc=quic_rkudarav@quicinc.com \
    --cc=quic_rohkumar@quicinc.com \
    --cc=quic_srivasam@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=swboyd@chromium.org \
    --cc=vkoul@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 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).