From: Marek Vasut <marex@denx.de>
To: Ying Liu <gnuiyl@gmail.com>
Cc: 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, conor+dt@kernel.org,
alexander.stein@ew.tq-group.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, krzysztof.kozlowski@linaro.org,
robh+dt@kernel.org, linux-imx@nxp.com,
krzysztof.kozlowski+dt@linaro.org, kernel@pengutronix.de,
LW@karo-electronics.de
Subject: Re: [PATCH v5 2/6] drm: lcdif: Drop unnecessary NULL pointer check on lcdif->bridge
Date: Wed, 10 May 2023 10:40:35 +0200 [thread overview]
Message-ID: <c9dedb24-5714-0301-d8cc-7c56673b07b0@denx.de> (raw)
In-Reply-To: <CAOcKUNXjvOMXtf2FVwjhWNbdwQy82T+wz-QN7ukAOmQo5DKQ2w@mail.gmail.com>
On 5/10/23 10:30, Ying Liu wrote:
> On Tue, May 9, 2023 at 10:14 AM Marek Vasut <marex@denx.de> wrote:
>>
>> On 5/8/23 07:57, Liu Ying wrote:
>>
>> Hi,
>
> Hi,
Hi,
>>> diff --git a/drivers/gpu/drm/mxsfb/lcdif_kms.c b/drivers/gpu/drm/mxsfb/lcdif_kms.c
>>> index 262bc43b1079..e54200a9fcb9 100644
>>> --- a/drivers/gpu/drm/mxsfb/lcdif_kms.c
>>> +++ b/drivers/gpu/drm/mxsfb/lcdif_kms.c
>>> @@ -394,7 +394,7 @@ static void lcdif_crtc_mode_set_nofb(struct lcdif_drm_private *lcdif,
>>> struct drm_display_mode *m = &lcdif->crtc.state->adjusted_mode;
>>> u32 bus_flags = 0;
>>>
>>> - if (lcdif->bridge && lcdif->bridge->timings)
>>> + if (lcdif->bridge->timings)
>>> bus_flags = lcdif->bridge->timings->input_bus_flags;
>>> else if (bridge_state)
>>> bus_flags = bridge_state->input_bus_cfg.flags;
>>> @@ -463,30 +463,21 @@ static void lcdif_crtc_atomic_enable(struct drm_crtc *crtc,
>>> struct drm_display_mode *m = &lcdif->crtc.state->adjusted_mode;
>>> struct drm_bridge_state *bridge_state = NULL;
>>> struct drm_device *drm = lcdif->drm;
>>> - u32 bus_format = 0;
>>> + u32 bus_format;
>>> dma_addr_t paddr;
>>>
>>> - /* If there is a bridge attached to the LCDIF, use its bus format */
>>> - if (lcdif->bridge) {
>>> - bridge_state =
>>> - drm_atomic_get_new_bridge_state(state,
>>> - lcdif->bridge);
>>> - if (!bridge_state)
>>> - bus_format = MEDIA_BUS_FMT_FIXED;
>>> - else
>>> - bus_format = bridge_state->input_bus_cfg.format;
>>> -
>>> - if (bus_format == MEDIA_BUS_FMT_FIXED) {
>>> - dev_warn_once(drm->dev,
>>> - "Bridge does not provide bus format, assuming MEDIA_BUS_FMT_RGB888_1X24.\n"
>>> - "Please fix bridge driver by handling atomic_get_input_bus_fmts.\n");
>>> - bus_format = MEDIA_BUS_FMT_RGB888_1X24;
>>> - }
>>> - }
>>> + bridge_state = drm_atomic_get_new_bridge_state(state, lcdif->bridge);
>>> + if (!bridge_state)
>>> + bus_format = MEDIA_BUS_FMT_FIXED;
>>> + else
>>> + bus_format = bridge_state->input_bus_cfg.format;
>>
>> The code below seems to change the logic slightly.
>>
>> Could it happen that:
>> - bridge_state is valid (i.e. non-NULL)
>> - bridge_state->input_bus_cfg.format is set to 0 (i.e. not set) ?
>> (note that MEDIA_BUS_FMT_FIXED is defined as 0x0001)
>
> Yes, bridge_state->input_bus_cfg.format could be zero.
> Will keep the below default MEDIA_BUS_FMT_RGB888_1X24
> bus format setting in next version.
Thanks for confirming.
The rest of the series looks good, sorry for the delay in reviews.
next prev parent reply other threads:[~2023-05-10 8:41 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 [this message]
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
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=c9dedb24-5714-0301-d8cc-7c56673b07b0@denx.de \
--to=marex@denx.de \
--cc=LW@karo-electronics.de \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gnuiyl@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=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).