From: Marek Vasut <marex@denx.de>
To: Robert Foss <robert.foss@linaro.org>,
Lucas Stach <l.stach@pengutronix.de>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
Jonas Karlman <jonas@kwiboo.se>,
dri-devel@lists.freedesktop.org,
Maxime Ripard <maxime@cerno.tech>,
Sam Ravnborg <sam@ravnborg.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH] drm/bridge: ti-sn65dsi83: Handle dsi_lanes == 0 as invalid
Date: Mon, 23 May 2022 11:58:28 +0200 [thread overview]
Message-ID: <adadd88b-9e6f-1ee8-9824-d284b0f91237@denx.de> (raw)
In-Reply-To: <CAG3jFyvm+gVESUX9LM0Mh48SsC+MZnTpOwrtbi+rRv8PtRWWTQ@mail.gmail.com>
On 5/23/22 11:40, Robert Foss wrote:
> On Thu, 19 May 2022 at 09:57, Lucas Stach <l.stach@pengutronix.de> wrote:
>>
>> Am Donnerstag, dem 19.05.2022 um 01:38 +0200 schrieb Marek Vasut:
>>> Handle empty data-lanes = < >; property, which translates to
>>> dsi_lanes = 0 as invalid.
[...]
>>> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
>>> index d64d4385188dd..dc65f424e7f3c 100644
>>> --- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
>>> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
>>> @@ -585,7 +585,7 @@ static int sn65dsi83_parse_dt(struct sn65dsi83 *ctx, enum sn65dsi83_model model)
>>> ctx->host_node = of_graph_get_remote_port_parent(endpoint);
>>> of_node_put(endpoint);
>>>
>>> - if (ctx->dsi_lanes < 0 || ctx->dsi_lanes > 4) {
>>> + if (ctx->dsi_lanes <= 0 || ctx->dsi_lanes > 4) {
>>> ret = -EINVAL;
>>> goto err_put_node;
>>> }
>>
>>
>
> Applied to drm-misc-next.
This was already applied to drm-misc-next-fixes , since this is a fix
for something that was already in release . The conflict will resolve
itself easily though ?
next prev parent reply other threads:[~2022-05-23 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 23:38 [PATCH] drm/bridge: ti-sn65dsi83: Handle dsi_lanes == 0 as invalid Marek Vasut
2022-05-19 7:43 ` Andrzej Hajda
2022-05-19 7:57 ` Lucas Stach
2022-05-23 9:40 ` Robert Foss
2022-05-23 9:58 ` Marek Vasut [this message]
2022-05-23 10:23 ` Robert Foss
2022-05-23 10:54 ` 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=adadd88b-9e6f-1ee8-9824-d284b0f91237@denx.de \
--to=marex@denx.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonas@kwiboo.se \
--cc=l.stach@pengutronix.de \
--cc=maxime@cerno.tech \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.