linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH v4 1/2] media: dt-bindings: mediatek: Rename child node names for decoder
Date: Wed, 5 Oct 2022 07:21:18 +0000	[thread overview]
Message-ID: <ffc56eb60a3ef74c815c8d3c170a0df51958e20d.camel@mediatek.com> (raw)
In-Reply-To: <20220930220011.GA1107972-robh@kernel.org>

Hi Rob,

On Fri, 2022-09-30 at 17:00 -0500, Rob Herring wrote:
> On Fri, Sep 30, 2022 at 07:22:36PM +0800, Allen-KH Cheng wrote:
> > In order to make the names of the child nodes more generic, we
> > rename
> > "vcodec" to "video-codec" for decoder in patternProperties and
> > example.
> 
> They are either generic or they aren't. Until something generic is 
> defined, I don't think it's worth the churn to change.
> 
> 
> > Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> > Reviewed-by: AngeloGioacchino Del Regno <
> > angelogioacchino.delregno@collabora.com>
> > ---
> >  .../bindings/media/mediatek,vcodec-subdev-decoder.yaml    | 8
> > ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git
> > a/Documentation/devicetree/bindings/media/mediatek,vcodec-subdev-
> > decoder.yaml
> > b/Documentation/devicetree/bindings/media/mediatek,vcodec-subdev-
> > decoder.yaml
> > index c4f20acdc1f8..67fde48f991c 100644
> > --- a/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > subdev-decoder.yaml
> > +++ b/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > subdev-decoder.yaml
> > @@ -91,7 +91,7 @@ properties:
> >  
> >  # Required child node:
> >  patternProperties:
> > -  '^vcodec-lat@[0-9a-f]+$':
> > +  '^video-codec-lat@[0-9a-f]+$':
> 
> Just 'video-codec' doesn't work?
> 

Thanks for your reply.

hmm, I think 'vidoe-codec' does wrok.

There are two seperate hardwares for the MTK video codec.
codec-lat and codec-core.

Is it ok to keep two child node names for various hardwares?


Thanks,
Allen

> >      type: object
> >  
> >      properties:
> > @@ -145,7 +145,7 @@ patternProperties:
> >  
> >      additionalProperties: false
> >  
> > -  '^vcodec-core@[0-9a-f]+$':
> > +  '^video-codec-core@[0-9a-f]+$':
> >      type: object
> >  
> >      properties:
> > @@ -241,7 +241,7 @@ examples:
> >              #size-cells = <2>;
> >              ranges = <0 0 0 0x16000000 0 0x40000>;
> >              reg = <0 0x16000000 0 0x1000>;		/* VDEC_SYS */
> > -            vcodec-lat@10000 {
> > +            video-codec-lat@10000 {
> >                  compatible = "mediatek,mtk-vcodec-lat";
> >                  reg = <0 0x10000 0 0x800>;
> >                  interrupts = <GIC_SPI 426 IRQ_TYPE_LEVEL_HIGH 0>;
> > @@ -264,7 +264,7 @@ examples:
> >                  power-domains = <&spm MT8192_POWER_DOMAIN_VDEC>;
> >              };
> >  
> > -            vcodec-core@25000 {
> > +            video-codec-core@25000 {
> >                  compatible = "mediatek,mtk-vcodec-core";
> >                  reg = <0 0x25000 0 0x1000>;
> >                  interrupts = <GIC_SPI 425 IRQ_TYPE_LEVEL_HIGH 0>;
> > -- 
> > 2.18.0
> > 
> > 
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-10-05  8:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 11:22 [PATCH v4 0/2] Add vcodec lat and core nodes for mt8192 Allen-KH Cheng
2022-09-30 11:22 ` [PATCH v4 1/2] media: dt-bindings: mediatek: Rename child node names for decoder Allen-KH Cheng
2022-09-30 22:00   ` Rob Herring
2022-10-05  7:21     ` Allen-KH Cheng (程冠勳) [this message]
2022-10-05  7:30       ` Krzysztof Kozlowski
2022-10-05 11:58         ` Allen-KH Cheng (程冠勳)
2022-11-24 11:05           ` Hans Verkuil
2022-11-24 11:09             ` Krzysztof Kozlowski
2022-11-25  9:28               ` Allen-KH Cheng (程冠勳)
2022-10-03 13:26   ` Krzysztof Kozlowski
2022-09-30 11:22 ` [PATCH v4 2/2] arm64: dts: mt8192: Add vcodec lat and core nodes Allen-KH Cheng
2022-10-06 18:44   ` Nícolas F. R. A. Prado
2022-11-18 14:10   ` Nícolas F. R. A. Prado
2022-11-21 12:30     ` Allen-KH Cheng (程冠勳)
2022-11-21 14:23       ` Nícolas F. R. A. Prado
2022-11-18  7:12 ` [PATCH v4 0/2] Add vcodec lat and core nodes for mt8192 Allen-KH Cheng (程冠勳)

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=ffc56eb60a3ef74c815c8d3c170a0df51958e20d.camel@mediatek.com \
    --to=allen-kh.cheng@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=robh@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).