From: Liu Ying <victor.liu@nxp.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, tomm.merciai@gmail.com
Cc: linux-renesas-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org, biju.das.jz@bp.renesas.com,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/bridge: ite-it6263: Support VESA input format
Date: Wed, 4 Dec 2024 11:42:51 +0800 [thread overview]
Message-ID: <054a0278-428f-49cb-b0f0-182c5bb3b61b@nxp.com> (raw)
In-Reply-To: <hd2kom5acz47c3mkjuauxhauahkt7vq2qoilppwn34iidldhos@rb5ydcayhtlj>
On 12/04/2024, Dmitry Baryshkov wrote:
> On Tue, Dec 03, 2024 at 06:21:29PM +0100, tomm.merciai@gmail.com wrote:
>> From: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
>>
>> Introduce it6263_is_input_bus_fmt_valid() and refactor the
>> it6263_bridge_atomic_get_input_bus_fmts() function to support VESA
>> format by selecting the LVDS input format based on the LVDS data mapping
>> and thereby support both JEIDA and VESA input formats.
>
> For the patch itself,
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
> A more generic question: is the bridge limited to 4 lanes or does it
> support 3-lane or 5-lane configurations?
According to ite,it6263.yaml, the bridge supports all the data
mappings(jeida-{18,24,30} and vesa-{24,30}) listed in
lvds-data-mapping.yaml. lvds-data-mapping.yaml specifies the
data lanes(3/4/5) used by each of the data mappings. So, the
bridge supports 3, 4 or 5 data lanes.
>
>>
>> Signed-off-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
>> ---
>> drivers/gpu/drm/bridge/ite-it6263.c | 25 ++++++++++++++++++++++---
>> 1 file changed, 22 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/ite-it6263.c b/drivers/gpu/drm/bridge/ite-it6263.c
>> index cbabd4e20d3e..83d1db29157a 100644
>> --- a/drivers/gpu/drm/bridge/ite-it6263.c
>> +++ b/drivers/gpu/drm/bridge/ite-it6263.c
>> @@ -48,6 +48,7 @@
>> #define REG_COL_DEP GENMASK(1, 0)
>> #define BIT8 FIELD_PREP(REG_COL_DEP, 1)
>> #define OUT_MAP BIT(4)
>> +#define VESA BIT(4)
>> #define JEIDA 0
>> #define REG_DESSC_ENB BIT(6)
>> #define DMODE BIT(7)
>> @@ -428,12 +429,30 @@ static inline void it6263_lvds_reset(struct it6263 *it)
>> fsleep(10000);
>> }
>>
>> +static bool it6263_is_input_bus_fmt_valid(u32 input_fmt)
>> +{
>> + switch (input_fmt) {
>> + case MEDIA_BUS_FMT_RGB888_1X7X4_JEIDA:
>> + case MEDIA_BUS_FMT_RGB888_1X7X4_SPWG:
>> + return true;
>> + }
>> + return false;
>> +}
>> +
>
--
Regards,
Liu Ying
next prev parent reply other threads:[~2024-12-04 3:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 17:21 tomm.merciai
2024-12-03 17:37 ` Dmitry Baryshkov
2024-12-04 3:42 ` Liu Ying [this message]
2024-12-04 6:45 ` Biju Das
2024-12-05 9:02 ` Liu Ying
2024-12-05 11:42 ` Dmitry Baryshkov
2024-12-05 12:19 ` Biju Das
2024-12-04 3:34 ` Liu Ying
2024-12-04 6:27 ` Biju Das
2024-12-04 6:47 ` Liu Ying
2024-12-04 10:37 ` Tommaso Merciai
2024-12-04 11:53 ` Dmitry Baryshkov
2024-12-04 13:11 ` Tommaso Merciai
2024-12-04 13:33 ` Dmitry Baryshkov
2024-12-04 13:36 ` Tommaso Merciai
2024-12-04 8:11 ` Tommaso Merciai
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=054a0278-428f-49cb-b0f0-182c5bb3b61b@nxp.com \
--to=victor.liu@nxp.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomm.merciai@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.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®