From: Jiaxin Yu <jiaxin.yu@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: <broonie@kernel.org>, <tzungbi@google.com>,
<angelogioacchino.delregno@collabora.com>, <aaronyu@google.com>,
<matthias.bgg@gmail.com>, <trevor.wu@mediatek.com>,
<linmq006@gmail.com>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [v5 1/4] ASoC: dt-bindings: mt8192-mt6359: add new compatible and new properties
Date: Tue, 22 Mar 2022 11:45:24 +0800 [thread overview]
Message-ID: <0e909de12a52ae88633634d868bd5001eef1b830.camel@mediatek.com> (raw)
In-Reply-To: <YjkLVwvxvOKr30qL@robh.at.kernel.org>
On Mon, 2022-03-21 at 18:33 -0500, Rob Herring wrote:
> On Sat, Mar 19, 2022 at 07:41:08PM +0800, Jiaxin Yu wrote:
> > 1. Adds new compatible string "mt8192_mt6359_rt1015p_rt5682s" for
> > machines
> > with rt1015p and rt5682s.
> > 2. Adds new property "mediatek,headset-codec" for getting headset
> > codecs.
> > 3. Adds new property "mediatek,speaker-codec" for getting speaker
> > codecs.
> >
> > Signed-off-by: Jiaxin Yu <jiaxin.yu@mediatek.com>
> > ---
> > .../sound/mt8192-mt6359-rt1015-rt5682.yaml | 29
> > +++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/sound/mt8192-mt6359-
> > rt1015-rt5682.yaml
> > b/Documentation/devicetree/bindings/sound/mt8192-mt6359-rt1015-
> > rt5682.yaml
> > index a781e7aaaa38..aa0476eedd38 100644
> > --- a/Documentation/devicetree/bindings/sound/mt8192-mt6359-rt1015-
> > rt5682.yaml
> > +++ b/Documentation/devicetree/bindings/sound/mt8192-mt6359-rt1015-
> > rt5682.yaml
> > @@ -18,6 +18,7 @@ properties:
> > enum:
> > - mediatek,mt8192_mt6359_rt1015_rt5682
> > - mediatek,mt8192_mt6359_rt1015p_rt5682
> > + - mediatek,mt8192_mt6359_rt1015p_rt5682s
> >
> > mediatek,platform:
> > $ref: "/schemas/types.yaml#/definitions/phandle"
> > @@ -27,6 +28,25 @@ properties:
> > $ref: "/schemas/types.yaml#/definitions/phandle"
> > description: The phandle of HDMI codec.
> >
> > +patternProperties:
> > + "^mediatek,headset-codec$":
>
> Fixed string, not a pattern. Move to 'properties'. Drop the vendor
> prefix too.
>
Hi Rob,
I originally referred to simple-card.yaml and move "xxx.yyy" to the
patternProperties.
Such as:
# use patternProperties to avoid naming "xxx,yyy" issue
patternProperties:
"^simple-audio-card,widgets$":
$ref: "#/definitions/widgets"
But your comment is more reasonable. I will move them to 'properties'
and drop the vendor prefix. Thanks for your review.
> > + description: Holds subnode which indicates headset dai.
> > + type: object
> > + properties:
> > + sound-dai:
> > + $ref: /schemas/types.yaml#/definitions/phandle-array
>
> Standard property, don't need a type or description. Just how many
> and
> what each one is if more than 1.
Should I describe them as below?
properties:
...
speaker-codec:
type: object
properties:
sound-dai:
maxItems: 1
...
>
> > + description: List of phandles to the headset codec nodes.
>
> More than 1?
>
Sorry, the description here is incorrect, there is only one phandle.
> > + additionalProperties: false
> > +
> > + "^mediatek,speaker-codec$":
> > + description: Holds subnode which indicates speaker dai.
> > + type: object
> > + properties:
> > + sound-dai:
> > + $ref: /schemas/types.yaml#/definitions/phandle-array
> > + description: List of phandles to the speaker codec nodes.
>
> Same here.
>
> > + additionalProperties: false
> > +
> > additionalProperties: false
> >
> > required:
> > @@ -44,6 +64,15 @@ examples:
> > "aud_clk_mosi_on";
> > pinctrl-0 = <&aud_clk_mosi_off>;
> > pinctrl-1 = <&aud_clk_mosi_on>;
> > +
> > + mediatek,headset-codec {
> > + sound-dai = <&rt5682>;
> > + };
> > +
> > + mediatek,speaker-codec {
> > + sound-dai = <&rt1015_l>,
> > + <&rt1015_r>;
> > + };
> > };
> >
> > ...
> > --
> > 2.18.0
> >
> >
next prev parent reply other threads:[~2022-03-22 3:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 11:41 [v5 0/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s Jiaxin Yu
2022-03-19 11:41 ` [v5 1/4] ASoC: dt-bindings: mt8192-mt6359: add new compatible and new properties Jiaxin Yu
2022-03-21 23:33 ` Rob Herring
2022-03-22 3:45 ` Jiaxin Yu [this message]
2022-03-22 15:02 ` Rob Herring
2022-03-19 11:41 ` [v5 2/4] ASoC: mediatek: mt8192: refactor for I2S3 DAI link of speaker Jiaxin Yu
2022-03-21 3:59 ` Tzung-Bi Shih
2022-03-21 15:24 ` Tzung-Bi Shih
2022-03-19 11:41 ` [v5 3/4] ASoC: mediatek: mt8192: refactor for I2S8/I2S9 DAI links of headset Jiaxin Yu
2022-03-21 3:59 ` Tzung-Bi Shih
2022-03-21 9:14 ` Jiaxin Yu
2022-03-21 9:21 ` Tzung-Bi Shih
2022-03-21 14:38 ` Jiaxin Yu
2022-03-21 15:23 ` Tzung-Bi Shih
2022-03-21 15:24 ` Tzung-Bi Shih
2022-03-19 11:41 ` [v5 4/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s Jiaxin Yu
2022-03-21 3:59 ` Tzung-Bi Shih
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=0e909de12a52ae88633634d868bd5001eef1b830.camel@mediatek.com \
--to=jiaxin.yu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=aaronyu@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linmq006@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=trevor.wu@mediatek.com \
--cc=tzungbi@google.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
all inboxes | Powered by JetHome®