From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Zhaoxiong Lv <lvzhaoxiong@huaqin.corp-partner.google.com>
Cc: neil.armstrong@linaro.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
airlied@gmail.com, mripard@kernel.org, dianders@google.com,
hsinyi@google.com, awarnecke002@hotmail.com,
quic_jesszhan@quicinc.com, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] drm/panel: boe-th101mb31ig002 : Fix the way to get porch parameters
Date: Mon, 15 Jul 2024 14:32:26 +0300 [thread overview]
Message-ID: <CAA8EJpp8LvzKdHR2y-f-qtfx-fLSOwxG_CXTCrtV6JWnzX_YmQ@mail.gmail.com> (raw)
In-Reply-To: <20240715031845.6687-2-lvzhaoxiong@huaqin.corp-partner.google.com>
On Mon, 15 Jul 2024 at 06:19, Zhaoxiong Lv
<lvzhaoxiong@huaqin.corp-partner.google.com> wrote:
>
> The current driver can only obtain the porch parameters
> of boe-th101mb31ig002. Modify it to obtain the porch
> parameters of the panel currently being used.
>
> Fixes: 24179ff9a2e4524 ("drm/panel: boe-th101mb31ig002 : Make it compatible with other panel.")
>
> Signed-off-by: Zhaoxiong Lv <lvzhaoxiong@huaqin.corp-partner.google.com>
No empty line between Fixed and Sign-off-by
> ---
> drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c b/drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c
> index b55cf80c5522..d4e4abd103bb 100644
> --- a/drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c
> +++ b/drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c
> @@ -312,15 +312,14 @@ static int boe_th101mb31ig002_get_modes(struct drm_panel *panel,
> struct boe_th101mb31ig002 *ctx = container_of(panel,
> struct boe_th101mb31ig002,
> panel);
> + const struct drm_display_mode *desc_mode = ctx->desc->modes;
> struct drm_display_mode *mode;
>
> - mode = drm_mode_duplicate(connector->dev,
> - &boe_th101mb31ig002_default_mode);
> + mode = drm_mode_duplicate(connector->dev, desc_mode);
> if (!mode) {
> dev_err(panel->dev, "Failed to add mode %ux%u@%u\n",
> - boe_th101mb31ig002_default_mode.hdisplay,
> - boe_th101mb31ig002_default_mode.vdisplay,
> - drm_mode_vrefresh(&boe_th101mb31ig002_default_mode));
> + desc_mode->hdisplay, desc_mode->vdisplay,
> + drm_mode_vrefresh(desc_mode));
> return -ENOMEM;
Please add a followup switching to drm_connector_helper_get_modes_fixed()
> }
>
> --
> 2.17.1
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2024-07-15 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 3:18 [PATCH v1 0/1] Fix the way to get porch parameters Zhaoxiong Lv
2024-07-15 3:18 ` [PATCH v1 1/1] drm/panel: boe-th101mb31ig002 : " Zhaoxiong Lv
2024-07-15 11:32 ` Dmitry Baryshkov [this message]
2024-07-15 13:57 ` [PATCH v1 0/1] " Doug Anderson
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=CAA8EJpp8LvzKdHR2y-f-qtfx-fLSOwxG_CXTCrtV6JWnzX_YmQ@mail.gmail.com \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=awarnecke002@hotmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsinyi@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvzhaoxiong@huaqin.corp-partner.google.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@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).