devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Jitao shi <jitao.shi@mediatek.com>,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	Rob Herring <robh+dt@kernel.org>,
	dri-devel@lists.freedesktop.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	linux-arm-kernel@lists.infradead.org, hsinyi@chromium.org,
	linux-mediatek@lists.infradead.org, fparent@baylibre.com,
	CK Hu <ck.hu@mediatek.com>
Subject: Re: [PATCH v2 1/1] dt-bindings: display: mediatek: dpi: add power-domains property
Date: Mon, 25 Jul 2022 16:28:32 -0600	[thread overview]
Message-ID: <20220725222832.GA2859262-robh@kernel.org> (raw)
In-Reply-To: <20220720130604.14113-2-allen-kh.cheng@mediatek.com>

On Wed, 20 Jul 2022 21:06:04 +0800, Allen-KH Cheng wrote:
> DPI is part of the display / multimedia block in MediaTek SoCs
> and is managed using power controller in some platforms. We add
> the power-domains property to the binding documentation.
> 
> Fixes:9273cf7d3942("dt-bindings: display: mediatek: convert the dpi bindings to yaml")
> 
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
>  .../devicetree/bindings/display/mediatek/mediatek,dpi.yaml   | 5 +++++
>  1 file changed, 5 insertions(+)
> 

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

      reply	other threads:[~2022-07-25 22:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 13:06 [PATCH v2 0/1] dt-bindings: display: mediatek: dpi: add power-domains Allen-KH Cheng
2022-07-20 13:06 ` [PATCH v2 1/1] dt-bindings: display: mediatek: dpi: add power-domains property Allen-KH Cheng
2022-07-25 22:28   ` Rob Herring [this message]

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=20220725222832.GA2859262-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=ck.hu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fparent@baylibre.com \
    --cc=hsinyi@chromium.org \
    --cc=jitao.shi@mediatek.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --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 \
    /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).