public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Steven Price <steven.price@arm.com>
Cc: Rain Yang <jiyu.yang@oss.nxp.com>,
	imx@lists.linux.dev, dri-devel@lists.freedesktop.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	boris.brezillon@collabora.com, liviu.dudau@arm.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.co, simona@ffwll.ch,
	marek.vasut@mailbox.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, Rain Yang <jiyu.yang@nxp.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: gpu: mali-valhall: make mali-supply optional
Date: Thu, 9 Oct 2025 10:43:25 -0400	[thread overview]
Message-ID: <aOfKDbjIHnFi6AX1@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <7c3b219f-f504-4c4c-a13a-6a25a0eda277@arm.com>

On Thu, Oct 09, 2025 at 02:00:43PM +0100, Steven Price wrote:
> Series applied to drm-misc-next.

I have not seen DT team's acked tag for binding.

Frank

>
> Thanks,
> Steve
>
> On 28/09/2025 10:03, Rain Yang wrote:
> > From: Rain Yang <jiyu.yang@nxp.com>
> >
> > Not all platforms require the mali-supply regulator. This change removes
> > it from the required list in the binding schema, and make mali-supply
> > required for rk3588 only.
> >
> > Signed-off-by: Rain Yang <jiyu.yang@nxp.com>
> > ---
> >  .../devicetree/bindings/gpu/arm,mali-valhall-csf.yaml          | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-valhall-csf.yaml b/Documentation/devicetree/bindings/gpu/arm,mali-valhall-csf.yaml
> > index b220cbd5362f..ef9791d8ed95 100644
> > --- a/Documentation/devicetree/bindings/gpu/arm,mali-valhall-csf.yaml
> > +++ b/Documentation/devicetree/bindings/gpu/arm,mali-valhall-csf.yaml
> > @@ -92,7 +92,6 @@ required:
> >    - interrupts
> >    - interrupt-names
> >    - clocks
> > -  - mali-supply
> >
> >  additionalProperties: false
> >
> > @@ -109,6 +108,8 @@ allOf:
> >          power-domains:
> >            maxItems: 1
> >          power-domain-names: false
> > +      required:
> > +        - mali-supply
> >
> >  examples:
> >    - |
>

  reply	other threads:[~2025-10-09 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28  9:03 [PATCH v2 1/2] dt-bindings: gpu: mali-valhall: make mali-supply optional Rain Yang
2025-09-28  9:03 ` [PATCH v2 2/2] drm/panthor: skip regulator setup if no such prop Rain Yang
2025-10-02  6:38   ` Boris Brezillon
2025-10-02  8:21   ` Steven Price
2025-10-02  3:37 ` [PATCH v2 1/2] dt-bindings: gpu: mali-valhall: make mali-supply optional Rob Herring (Arm)
2025-10-02  6:38 ` Boris Brezillon
2025-10-09 13:00 ` Steven Price
2025-10-09 14:43   ` Frank Li [this message]
2025-10-09 14:52     ` Boris Brezillon

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=aOfKDbjIHnFi6AX1@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=airlied@gmail.co \
    --cc=boris.brezillon@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imx@lists.linux.dev \
    --cc=jiyu.yang@nxp.com \
    --cc=jiyu.yang@oss.nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marek.vasut@mailbox.org \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=steven.price@arm.com \
    --cc=tzimmermann@suse.de \
    /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