Linux IOMMU Development
 help / color / mirror / Atom feed
From: Chengci.Xu <chengci.xu@mediatek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Yong Wu <yong.wu@mediatek.com>, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: <iommu@lists.linux.dev>, <linux-mediatek@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH 1/3] dt-bindings: mediatek: mt8188: Add binding for MM & INFRA IOMMU
Date: Thu, 18 Aug 2022 16:03:26 +0800	[thread overview]
Message-ID: <bc7214a78952066bf93f8bedaa5b8191ff3e10e3.camel@mediatek.com> (raw)
In-Reply-To: <61c0d3bf-cf1f-77f0-bb47-dec7cde5b488@linaro.org>

On Thu, 2022-08-18 at 10:42 +0300, Krzysztof Kozlowski wrote:
> On 18/08/2022 10:26, Chengci.Xu wrote:
> > > >      then:
> > > >        required:
> > > > diff --git a/include/dt-bindings/memory/mt8188-memory-port.h
> > > >  b/include/dt-bindings/memory/mt8188-memory-port.h
> > > > new file mode 100644
> > > > index 000000000000..612fd366c3a7
> > > > --- /dev/null
> > > > +++ b/include/dt-bindings/memory/mt8188-memory-port.h
> > > 
> > > Use vendor prefix in filename, so mediatek,mt8188-memory-port.h
> > 
> > Is this a new mandatory rules to add a vendor prefix in dt-bindings
> > file name? we have never add a vendor prefix before.
> > 
> > If possible, we'd like not to use vendor prefix for the consistency
> > of
> > fliename's format(mtxxxx-memory-port.h).
> > Such as "mt8195-memory-port.h" and "mt8186-memory-port.h".
> 
> That's a generic rule, although loosely applied. The consistency is
> rather to have a vendor prefix everywhere. Why Mediatek should have
> an
> exception?
> 

Thank you for sharing that generic rule and we will rename the file to 
"mediatek,mt8188-memory-port.h" in th coming next version.

> Best regards,
> Krzysztof
> 

Best regards,
Chengci Xu


  reply	other threads:[~2022-08-18  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 10:58 [PATCH 0/3] MT8188 IOMMU SUPPORT Chengci.Xu
2022-08-04 10:58 ` [PATCH 1/3] dt-bindings: mediatek: mt8188: Add binding for MM & INFRA IOMMU Chengci.Xu
2022-08-04 11:13   ` Krzysztof Kozlowski
2022-08-18  7:26     ` Chengci.Xu
2022-08-18  7:42       ` Krzysztof Kozlowski
2022-08-18  8:03         ` Chengci.Xu [this message]
2022-08-18  7:48       ` Krzysztof Kozlowski
2022-08-18  8:12         ` Chengci.Xu
2022-08-04 10:58 ` [PATCH 2/3] iommu/mediatek: Add enable IOMMU SMC command for INFRA master Chengci.Xu
2022-08-04 10:58 ` [PATCH 3/3] iommu/mediatek: Add MT8188 IOMMU Support Chengci.Xu

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=bc7214a78952066bf93f8bedaa5b8191ff3e10e3.camel@mediatek.com \
    --to=chengci.xu@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --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+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=yong.wu@mediatek.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