mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Andy Yan <andyshrk@163.com>
Cc: linux-kernel@vger.kernel.org, krzk+dt@kernel.org,
	neil.armstrong@linaro.org, conor+dt@kernel.org,
	sebastian.reichel@collabora.com, quic_jesszhan@quicinc.com,
	devicetree@vger.kernel.org, tzimmermann@suse.de,
	dri-devel@lists.freedesktop.org,
	Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH 1/2] dt-bindings: display: panel: Make reset-gpio as optional for Raydium RM67200
Date: Thu, 26 Jun 2025 18:53:35 -0500	[thread overview]
Message-ID: <175098201489.1430871.16529661509700275956.robh@kernel.org> (raw)
In-Reply-To: <20250616070536.670519-1-andyshrk@163.com>


On Mon, 16 Jun 2025 15:05:16 +0800, Andy Yan wrote:
> From: Andy Yan <andy.yan@rock-chips.com>
> 
> Although the datasheet of the panel module describes that it has a
> reset pin, in the actual hardware design, we often use an RC circuit
> to control the reset, and rarely use GPIO to control the reset. This
> is the way it is done on our numerous development boards (such as RK3568,
> RK3576 EVB).
> So make the reset-gpio optional.
> 
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
> ---
> 
>  .../devicetree/bindings/display/panel/raydium,rm67200.yaml       | 1 -
>  1 file changed, 1 deletion(-)
> 

Acked-by: Rob Herring (Arm) <robh@kernel.org>


  parent reply	other threads:[~2025-06-26 23:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  7:05 Andy Yan
2025-06-16  7:05 ` [PATCH 2/2] drivers/panel: raydium-rm67200: Make reset-gpio optional Andy Yan
2025-06-19 13:34   ` Sebastian Reichel
2025-06-19 13:12 ` [PATCH 1/2] dt-bindings: display: panel: Make reset-gpio as optional for Raydium RM67200 Sebastian Reichel
2025-06-26 23:53 ` Rob Herring (Arm) [this message]
2025-06-30 15:41 ` Neil Armstrong

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=175098201489.1430871.16529661509700275956.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andy.yan@rock-chips.com \
    --cc=andyshrk@163.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_jesszhan@quicinc.com \
    --cc=sebastian.reichel@collabora.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

all inboxes | Powered by JetHome®