From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Rahul T R <r-ravikumar@ti.com>, thierry.reding@gmail.com
Cc: sam@ravnborg.org, airlied@linux.ie, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
nikhil.nd@ti.com, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH] drm/panel: simple: Initialize bpc in RK101II01D-CT panel descriptor
Date: Fri, 11 Feb 2022 09:58:49 +0200 [thread overview]
Message-ID: <2c534402-3302-047f-a362-18dfc2db2a39@ideasonboard.com> (raw)
In-Reply-To: <20220210140300.11900-1-r-ravikumar@ti.com>
On 10/02/2022 16:03, Rahul T R wrote:
> Initialize bpc while creating panel_desc structure for RK101II01D-CT
>
> Below warning is triggered since bpc is not being initialized
>
> WARNING: CPU: 2 PID: 47 at drivers/gpu/drm/panel/panel-simple.c:614
> panel_simple_probe+0x1b0/0x3c8
>
> Signed-off-by: Rahul T R <r-ravikumar@ti.com>
> ---
> drivers/gpu/drm/panel/panel-simple.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c
> index c324a3ed34b9..c09eb5ad65fc 100644
> --- a/drivers/gpu/drm/panel/panel-simple.c
> +++ b/drivers/gpu/drm/panel/panel-simple.c
> @@ -3058,6 +3058,7 @@ static const struct drm_display_mode rocktech_rk101ii01d_ct_mode = {
>
> static const struct panel_desc rocktech_rk101ii01d_ct = {
> .modes = &rocktech_rk101ii01d_ct_mode,
> + .bpc = 8,
> .num_modes = 1,
> .size = {
> .width = 217,
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Tomi
next prev parent reply other threads:[~2022-02-11 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 14:03 [PATCH] drm/panel: simple: Initialize bpc in RK101II01D-CT panel descriptor Rahul T R
2022-02-11 7:58 ` Tomi Valkeinen [this message]
2022-02-28 9:36 ` Tomi Valkeinen
-- strict thread matches above, loose matches on Subject: below --
2021-10-28 11:52 Rahul T R
2021-11-08 16:33 ` Rahul T R
2021-11-11 12:07 ` Rahul T R
2022-01-27 16:25 ` Rahul T R
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=2c534402-3302-047f-a362-18dfc2db2a39@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.nd@ti.com \
--cc=r-ravikumar@ti.com \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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