From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski@linaro.org, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org,
Matthias Brugger <matthias.bgg@gmail.com>,
will@kernel.org
Subject: Re: [PATCH v2 1/7] dt-bindings: iommu: mediatek: Add phandles for mediatek infra/pericfg
Date: Wed, 1 Jun 2022 15:01:43 -0500 [thread overview]
Message-ID: <20220601200143.GA334351-robh@kernel.org> (raw)
In-Reply-To: <2550039f-1cfc-eb5d-bbc9-bf82666e9abd@collabora.com>
On Wed, May 18, 2022 at 01:42:20PM +0200, AngeloGioacchino Del Regno wrote:
> Il 18/05/22 13:29, Matthias Brugger ha scritto:
> >
> >
> > On 18/05/2022 12:04, AngeloGioacchino Del Regno wrote:
> > > Add properties "mediatek,infracfg" and "mediatek,pericfg" to let the
> > > mtk_iommu driver retrieve phandles to the infracfg and pericfg syscon(s)
> > > instead of performing a per-soc compatible lookup.
> > >
> > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > > ---
> > > .../devicetree/bindings/iommu/mediatek,iommu.yaml | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > index 2ae3bbad7f1a..c4af41947593 100644
> > > --- a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > +++ b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > @@ -101,6 +101,10 @@ properties:
> > > items:
> > > - const: bclk
> > > + mediatek,infracfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek infracfg syscon
> > > +
> > > mediatek,larbs:
> > > $ref: /schemas/types.yaml#/definitions/phandle-array
> > > minItems: 1
> > > @@ -112,6 +116,10 @@ properties:
> > > Refer to bindings/memory-controllers/mediatek,smi-larb.yaml. It must sort
> > > according to the local arbiter index, like larb0, larb1, larb2...
> > > + mediatek,pericfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek pericfg syscon
> > > +
> >
> > I didn't explain myself. What I was suguesting was to squash the patch
> > that add requiered mediatek,infracfg with the patch that adds
> > mediatk,infracfg to the binding description. And then squash the both
> > patches adding pericfg as well.
>
> Sorry Matthias, I'm not sure ... I think I'm misunderstanding you again...
> ...but if I'm not, I don't think that squashing actual code and bindings together
> is something acceptable?
>
> I've made that kind of mistake in the past and I was told multiple times that
> dt-bindings changes shall be sent separately from the actual driver changes.
Combine patches 1 and 6 is the suggestion, not driver changes.
Rob
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
yong.wu@mediatek.com, joro@8bytes.org, will@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski@linaro.org
Subject: Re: [PATCH v2 1/7] dt-bindings: iommu: mediatek: Add phandles for mediatek infra/pericfg
Date: Wed, 1 Jun 2022 15:01:43 -0500 [thread overview]
Message-ID: <20220601200143.GA334351-robh@kernel.org> (raw)
In-Reply-To: <2550039f-1cfc-eb5d-bbc9-bf82666e9abd@collabora.com>
On Wed, May 18, 2022 at 01:42:20PM +0200, AngeloGioacchino Del Regno wrote:
> Il 18/05/22 13:29, Matthias Brugger ha scritto:
> >
> >
> > On 18/05/2022 12:04, AngeloGioacchino Del Regno wrote:
> > > Add properties "mediatek,infracfg" and "mediatek,pericfg" to let the
> > > mtk_iommu driver retrieve phandles to the infracfg and pericfg syscon(s)
> > > instead of performing a per-soc compatible lookup.
> > >
> > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > > ---
> > > .../devicetree/bindings/iommu/mediatek,iommu.yaml | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > index 2ae3bbad7f1a..c4af41947593 100644
> > > --- a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > +++ b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > @@ -101,6 +101,10 @@ properties:
> > > items:
> > > - const: bclk
> > > + mediatek,infracfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek infracfg syscon
> > > +
> > > mediatek,larbs:
> > > $ref: /schemas/types.yaml#/definitions/phandle-array
> > > minItems: 1
> > > @@ -112,6 +116,10 @@ properties:
> > > Refer to bindings/memory-controllers/mediatek,smi-larb.yaml. It must sort
> > > according to the local arbiter index, like larb0, larb1, larb2...
> > > + mediatek,pericfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek pericfg syscon
> > > +
> >
> > I didn't explain myself. What I was suguesting was to squash the patch
> > that add requiered mediatek,infracfg with the patch that adds
> > mediatk,infracfg to the binding description. And then squash the both
> > patches adding pericfg as well.
>
> Sorry Matthias, I'm not sure ... I think I'm misunderstanding you again...
> ...but if I'm not, I don't think that squashing actual code and bindings together
> is something acceptable?
>
> I've made that kind of mistake in the past and I was told multiple times that
> dt-bindings changes shall be sent separately from the actual driver changes.
Combine patches 1 and 6 is the suggestion, not driver changes.
Rob
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
yong.wu@mediatek.com, joro@8bytes.org, will@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski@linaro.org
Subject: Re: [PATCH v2 1/7] dt-bindings: iommu: mediatek: Add phandles for mediatek infra/pericfg
Date: Wed, 1 Jun 2022 15:01:43 -0500 [thread overview]
Message-ID: <20220601200143.GA334351-robh@kernel.org> (raw)
In-Reply-To: <2550039f-1cfc-eb5d-bbc9-bf82666e9abd@collabora.com>
On Wed, May 18, 2022 at 01:42:20PM +0200, AngeloGioacchino Del Regno wrote:
> Il 18/05/22 13:29, Matthias Brugger ha scritto:
> >
> >
> > On 18/05/2022 12:04, AngeloGioacchino Del Regno wrote:
> > > Add properties "mediatek,infracfg" and "mediatek,pericfg" to let the
> > > mtk_iommu driver retrieve phandles to the infracfg and pericfg syscon(s)
> > > instead of performing a per-soc compatible lookup.
> > >
> > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > > ---
> > > .../devicetree/bindings/iommu/mediatek,iommu.yaml | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > index 2ae3bbad7f1a..c4af41947593 100644
> > > --- a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > +++ b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > @@ -101,6 +101,10 @@ properties:
> > > items:
> > > - const: bclk
> > > + mediatek,infracfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek infracfg syscon
> > > +
> > > mediatek,larbs:
> > > $ref: /schemas/types.yaml#/definitions/phandle-array
> > > minItems: 1
> > > @@ -112,6 +116,10 @@ properties:
> > > Refer to bindings/memory-controllers/mediatek,smi-larb.yaml. It must sort
> > > according to the local arbiter index, like larb0, larb1, larb2...
> > > + mediatek,pericfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek pericfg syscon
> > > +
> >
> > I didn't explain myself. What I was suguesting was to squash the patch
> > that add requiered mediatek,infracfg with the patch that adds
> > mediatk,infracfg to the binding description. And then squash the both
> > patches adding pericfg as well.
>
> Sorry Matthias, I'm not sure ... I think I'm misunderstanding you again...
> ...but if I'm not, I don't think that squashing actual code and bindings together
> is something acceptable?
>
> I've made that kind of mistake in the past and I was told multiple times that
> dt-bindings changes shall be sent separately from the actual driver changes.
Combine patches 1 and 6 is the suggestion, not driver changes.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
yong.wu@mediatek.com, joro@8bytes.org, will@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski@linaro.org
Subject: Re: [PATCH v2 1/7] dt-bindings: iommu: mediatek: Add phandles for mediatek infra/pericfg
Date: Wed, 1 Jun 2022 15:01:43 -0500 [thread overview]
Message-ID: <20220601200143.GA334351-robh@kernel.org> (raw)
In-Reply-To: <2550039f-1cfc-eb5d-bbc9-bf82666e9abd@collabora.com>
On Wed, May 18, 2022 at 01:42:20PM +0200, AngeloGioacchino Del Regno wrote:
> Il 18/05/22 13:29, Matthias Brugger ha scritto:
> >
> >
> > On 18/05/2022 12:04, AngeloGioacchino Del Regno wrote:
> > > Add properties "mediatek,infracfg" and "mediatek,pericfg" to let the
> > > mtk_iommu driver retrieve phandles to the infracfg and pericfg syscon(s)
> > > instead of performing a per-soc compatible lookup.
> > >
> > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > > ---
> > > .../devicetree/bindings/iommu/mediatek,iommu.yaml | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > index 2ae3bbad7f1a..c4af41947593 100644
> > > --- a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > +++ b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml
> > > @@ -101,6 +101,10 @@ properties:
> > > items:
> > > - const: bclk
> > > + mediatek,infracfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek infracfg syscon
> > > +
> > > mediatek,larbs:
> > > $ref: /schemas/types.yaml#/definitions/phandle-array
> > > minItems: 1
> > > @@ -112,6 +116,10 @@ properties:
> > > Refer to bindings/memory-controllers/mediatek,smi-larb.yaml. It must sort
> > > according to the local arbiter index, like larb0, larb1, larb2...
> > > + mediatek,pericfg:
> > > + $ref: /schemas/types.yaml#/definitions/phandle
> > > + description: The phandle to the mediatek pericfg syscon
> > > +
> >
> > I didn't explain myself. What I was suguesting was to squash the patch
> > that add requiered mediatek,infracfg with the patch that adds
> > mediatk,infracfg to the binding description. And then squash the both
> > patches adding pericfg as well.
>
> Sorry Matthias, I'm not sure ... I think I'm misunderstanding you again...
> ...but if I'm not, I don't think that squashing actual code and bindings together
> is something acceptable?
>
> I've made that kind of mistake in the past and I was told multiple times that
> dt-bindings changes shall be sent separately from the actual driver changes.
Combine patches 1 and 6 is the suggestion, not driver changes.
Rob
next prev parent reply other threads:[~2022-06-01 20:01 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 10:04 [PATCH v2 0/7] mtk_iommu: Specify phandles to infracfg and pericfg AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` [PATCH v2 1/7] dt-bindings: iommu: mediatek: Add phandles for mediatek infra/pericfg AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 11:29 ` Matthias Brugger
2022-05-18 11:29 ` Matthias Brugger
2022-05-18 11:29 ` Matthias Brugger
2022-05-18 11:29 ` Matthias Brugger
2022-05-18 11:42 ` AngeloGioacchino Del Regno
2022-05-18 11:42 ` AngeloGioacchino Del Regno
2022-05-18 11:42 ` AngeloGioacchino Del Regno
2022-05-18 11:42 ` AngeloGioacchino Del Regno
2022-06-01 20:01 ` Rob Herring [this message]
2022-06-01 20:01 ` Rob Herring
2022-06-01 20:01 ` Rob Herring
2022-06-01 20:01 ` Rob Herring
2022-05-26 8:21 ` Yong Wu via iommu
2022-05-26 8:21 ` Yong Wu
2022-05-26 8:21 ` Yong Wu
2022-05-26 8:21 ` Yong Wu
2022-05-18 10:04 ` [PATCH v2 2/7] iommu: mtk_iommu: Lookup phandle to retrieve syscon to infracfg AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-26 8:22 ` Yong Wu via iommu
2022-05-26 8:22 ` Yong Wu
2022-05-26 8:22 ` Yong Wu
2022-05-26 8:22 ` Yong Wu
2022-05-18 10:04 ` [PATCH v2 3/7] iommu: mtk_iommu: Lookup phandle to retrieve syscon to pericfg AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-18 10:04 ` AngeloGioacchino Del Regno
2022-05-26 8:22 ` Yong Wu via iommu
2022-05-26 8:22 ` Yong Wu
2022-05-26 8:22 ` Yong Wu
2022-05-26 8:22 ` Yong Wu
2022-05-18 10:05 ` [PATCH v2 4/7] arm64: dts: mediatek: mt8173: Add mediatek, infracfg phandle for IOMMU AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 4/7] arm64: dts: mediatek: mt8173: Add mediatek,infracfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 4/7] arm64: dts: mediatek: mt8173: Add mediatek, infracfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 5/7] arm64: dts: mediatek: mt2712e: " AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 5/7] arm64: dts: mediatek: mt2712e: Add mediatek,infracfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 5/7] arm64: dts: mediatek: mt2712e: Add mediatek, infracfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 6/7] dt-bindings: iommu: mediatek: Require mediatek, infracfg for mt2712/8173 AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 6/7] dt-bindings: iommu: mediatek: Require mediatek,infracfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 6/7] dt-bindings: iommu: mediatek: Require mediatek, infracfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 7/7] dt-bindings: iommu: mediatek: Require mediatek, pericfg for mt8195-infra AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 7/7] dt-bindings: iommu: mediatek: Require mediatek,pericfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` [PATCH v2 7/7] dt-bindings: iommu: mediatek: Require mediatek, pericfg " AngeloGioacchino Del Regno
2022-05-18 10:05 ` AngeloGioacchino Del Regno
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=20220601200143.GA334351-robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.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=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.