linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Maso Huang (黃加竹)" <Maso.Huang@mediatek.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Trevor Wu (吳文良)" <Trevor.Wu@mediatek.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
	"renzhijie2@huawei.com" <renzhijie2@huawei.com>,
	"tiwai@suse.com" <tiwai@suse.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"perex@perex.cz" <perex@perex.cz>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>,
	"Jiaxin Yu (俞家鑫)" <Jiaxin.Yu@mediatek.com>
Subject: Re: [PATCH 7/7] ASoC: dt-bindings: mediatek,mt79xx-afe: add audio afe document
Date: Wed, 14 Jun 2023 08:34:47 +0200	[thread overview]
Message-ID: <d6289232-6276-a2d3-c059-1edcef6a1b6f@kernel.org> (raw)
In-Reply-To: <14913cbb87981eed6f8b72f9e659ed3e25958320.camel@mediatek.com>

On 14/06/2023 05:17, Maso Huang (黃加竹) wrote:
> On Tue, 2023-06-13 at 10:51 +0200, Krzysztof Kozlowski wrote:
>>  	 
>> External email : Please do not click links or open attachments until
>> you have verified the sender or the content.
>>  
>> On 12/06/2023 12:52, Maso Hunag wrote:
>>> From: Maso Huang <maso.huang@mediatek.com>
>>>
>>> Add mt79xx audio afe document.
>>
>> Please use scripts/get_maintainers.pl to get a list of necessary
>> people
>> and lists to CC.  It might happen, that command when run on an older
>> kernel, gives you outdated entries.  Therefore please be sure you
>> base
>> your patches on recent Linux kernel.
>>
> 
> Hi Krzysztif, 
> 
> Thanks for your review. And sorry for missing some necessary
> maintainers.
> What's your suggestion, resend these patches again with them, or add
> them back in v2 patch?


You need to fix the patch anyway, so use get_maintainers.pl in v2. I
don't understand why you Cc here many unrelated people but not the
actual maintainers which get_maintainers.pl asks you to Cc!

> 
>>>
>>> Signed-off-by: Maso Huang <maso.huang@mediatek.com>
>>> ---
>>>  .../bindings/sound/mediatek,mt79xx-afe.yaml   | 102
>> ++++++++++++++++++
>>>  1 file changed, 102 insertions(+)
>>>  create mode 100644
>> Documentation/devicetree/bindings/sound/mediatek,mt79xx-afe.yaml
>>>
>>> diff --git
>> a/Documentation/devicetree/bindings/sound/mediatek,mt79xx-afe.yaml
>> b/Documentation/devicetree/bindings/sound/mediatek,mt79xx-afe.yaml
>>> new file mode 100644
>>> index 000000000000..11ef1cfdf49b
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/sound/mediatek,mt79xx-
>> afe.yaml
>>> @@ -0,0 +1,102 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/sound/mediatek,mt79xx-afe.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: MediaTek AFE PCM controller for MT79xx
>>
>> 79XX sounds weird. Are you sure you are not using wildcards (which
>> are
>> not allowed)?
>>
> 
> We would like to use mt79xx for mt7986/mt7981/mt7988 series.
> Or is it better to just use mt7986 for this series?

You cannot use wildcard. Get some internal review of your patches prior
to submission to mailing list.

https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst

> 
>>> +
>>> +maintainers:
>>> +  - Maso Huang <maso.huang@mediatek.com>
>>> +
>>> +properties:
>>> +  compatible:
>>> +    oneOf:
>>> +      - const: mediatek,mt79xx-afe
>>> +      - items:
>>> +          - enum:
>>> +              - mediatek,mt7981-afe
>>> +              - mediatek,mt7986-afe
>>> +              - mediatek,mt7988-afe
>>> +          - const: mediatek,mt79xx-afe
>>
>> I already saw AFE, why it cannot be part of existing bindings?

Can you answer this?

>>
>> This list is odd. 79xx, 7981? So it is wildcard?
>>
> 
> Yes, it is wildcard for mt7986/mt7981/mt7988 series.
> Is it better to just use mt7986 for this series? 

No wildcards.


Best regards,
Krzysztof


  reply	other threads:[~2023-06-14  6:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 10:52 [PATCH 0/7] ASoC: mediatek: Add support for MT79xx SoC Maso Hunag
2023-06-12 10:52 ` [PATCH 1/7] ASoC: mediatek: mt79xx: add common header Maso Hunag
2023-06-14  7:44   ` AngeloGioacchino Del Regno
2023-06-14  7:52     ` Maso Huang (黃加竹)
2023-06-12 10:52 ` [PATCH 2/7] ASoC: mediatek: mt79xx: support audio clock control Maso Hunag
2023-06-13  7:27   ` Claudiu.Beznea
2023-06-14  7:44     ` Maso Huang (黃加竹)
2023-06-12 10:52 ` [PATCH 3/7] ASoC: mediatek: mt79xx: add platform driver Maso Hunag
2023-06-14  7:57   ` AngeloGioacchino Del Regno
2023-06-14  9:06     ` Maso Huang (黃加竹)
2023-06-14 12:21   ` kernel test robot
2023-06-12 10:52 ` [PATCH 4/7] ASoC: mediatek: mt79xx: support etdm in " Maso Hunag
2023-06-12 10:52 ` [PATCH 5/7] ASoC: mediatek: mt79xx: add machine driver with wm8960 Maso Hunag
2023-06-12 10:52 ` [PATCH 6/7] ASoC: dt-bindings: mediatek,mt79xx-wm8960: add mt79xx-wm8960 document Maso Hunag
2023-06-13  8:49   ` Krzysztof Kozlowski
2023-06-14  7:40     ` Maso Huang (黃加竹)
2023-06-14  8:22       ` Krzysztof Kozlowski
2023-06-14  8:45         ` Maso Huang (黃加竹)
2023-06-12 10:52 ` [PATCH 7/7] ASoC: dt-bindings: mediatek,mt79xx-afe: add audio afe document Maso Hunag
2023-06-13  8:51   ` Krzysztof Kozlowski
2023-06-14  3:17     ` Maso Huang (黃加竹)
2023-06-14  6:34       ` Krzysztof Kozlowski [this message]
2023-06-14  7:37         ` Maso Huang (黃加竹)
2023-06-14  8:21           ` Krzysztof Kozlowski
2023-06-14  9:19             ` Maso Huang (黃加竹)
2023-06-14 10:26               ` Krzysztof Kozlowski
2023-06-15  2:26                 ` Maso Huang (黃加竹)

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=d6289232-6276-a2d3-c059-1edcef6a1b6f@kernel.org \
    --to=krzk@kernel.org \
    --cc=Allen-KH.Cheng@mediatek.com \
    --cc=Jiaxin.Yu@mediatek.com \
    --cc=Maso.Huang@mediatek.com \
    --cc=Trevor.Wu@mediatek.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=perex@perex.cz \
    --cc=renzhijie2@huawei.com \
    --cc=tiwai@suse.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).