devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Liu Ying <victor.liu@nxp.com>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: stefan@agner.ch, airlied@gmail.com, daniel@ffwll.ch,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	krzysztof.kozlowski@linaro.org, LW@karo-electronics.de,
	alexander.stein@ew.tq-group.com
Subject: Re: [PATCH v5 4/6] drm: lcdif: Check consistent bus format and flags across first bridges
Date: Tue, 9 May 2023 02:13:06 +0200	[thread overview]
Message-ID: <ed2a654c-68ae-43cd-a69e-79b6e467f016@denx.de> (raw)
In-Reply-To: <20230508055740.635256-5-victor.liu@nxp.com>

On 5/8/23 07:57, Liu Ying wrote:
> The single LCDIF embedded in i.MX93 SoC may drive multiple displays
> simultaneously.  Check bus format and flags across first bridges in
> ->atomic_check() to ensure they are consistent.  This is a preparation
> for adding i.MX93 LCDIF support.
> 
> Acked-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> Signed-off-by: Liu Ying <victor.liu@nxp.com>

Reviewed-by: Marek Vasut <marex@denx.de>

  reply	other threads:[~2023-05-09  2:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  5:57 [PATCH v5 0/6] drm: lcdif: Add i.MX93 LCDIF support Liu Ying
2023-05-08  5:57 ` [PATCH v5 1/6] dt-bindings: " Liu Ying
2023-05-08  6:26   ` Rob Herring
2023-05-08  5:57 ` [PATCH v5 2/6] drm: lcdif: Drop unnecessary NULL pointer check on lcdif->bridge Liu Ying
2023-05-09  0:02   ` Marek Vasut
2023-05-10  8:30     ` Ying Liu
2023-05-10  8:40       ` Marek Vasut
2023-05-08  5:57 ` [PATCH v5 3/6] drm: lcdif: Determine bus format and flags in ->atomic_check() Liu Ying
2023-05-09  0:11   ` Marek Vasut
2023-05-08  5:57 ` [PATCH v5 4/6] drm: lcdif: Check consistent bus format and flags across first bridges Liu Ying
2023-05-09  0:13   ` Marek Vasut [this message]
2023-05-08  5:57 ` [PATCH v5 5/6] drm: lcdif: Add multiple encoders and first bridges support Liu Ying
2023-05-09  0:23   ` Marek Vasut
2023-05-10  8:44     ` Ying Liu
2023-05-08  5:57 ` [PATCH v5 6/6] drm: lcdif: Add i.MX93 LCDIF compatible string Liu Ying
2023-05-09  0:24   ` Marek Vasut

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=ed2a654c-68ae-43cd-a69e-79b6e467f016@denx.de \
    --to=marex@denx.de \
    --cc=LW@karo-electronics.de \
    --cc=airlied@gmail.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=victor.liu@nxp.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;
as well as URLs for NNTP newsgroup(s).