From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Andrzej Hajda <a.hajda@samsung.com>,
Jonas Karlman <jonas@kwiboo.se>,
"Laurent.pinchart@ideasonboard.com"
<Laurent.pinchart@ideasonboard.com>,
"narmstrong@baylibre.com" <narmstrong@baylibre.com>,
"khilman@baylibre.com" <khilman@baylibre.com>,
"zhengyang@rock-chips.com" <zhengyang@rock-chips.com>,
"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
"hjc@rock-chips.com" <hjc@rock-chips.com>,
"heiko@sntech.de" <heiko@sntech.de>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] drm/sun4i: Enable DRM InfoFrame support on H6
Date: Mon, 24 Jun 2019 18:03:45 +0200 [thread overview]
Message-ID: <44611965.cJa5QBey4U@jernej-laptop> (raw)
In-Reply-To: <CAGb2v67FF3k9wZu7K+Z5yKFFeh8A_4iuEXfh+tO65UvVRfY-sA@mail.gmail.com>
Dne ponedeljek, 24. junij 2019 ob 17:56:30 CEST je Chen-Yu Tsai napisal(a):
> On Mon, Jun 24, 2019 at 11:49 PM Andrzej Hajda <a.hajda@samsung.com> wrote:
> > On 24.06.2019 17:05, Jernej Škrabec wrote:
> > > Dne ponedeljek, 24. junij 2019 ob 17:03:31 CEST je Andrzej Hajda
napisal(a):
> > >> On 26.05.2019 23:20, Jonas Karlman wrote:
> > >>> This patch enables Dynamic Range and Mastering InfoFrame on H6.
> > >>>
> > >>> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> > >>> Cc: Jernej Skrabec <jernej.skrabec@siol.net>
> > >>> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
> > >>> ---
> > >>>
> > >>> drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c | 2 ++
> > >>> drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h | 1 +
> > >>> 2 files changed, 3 insertions(+)
> > >>>
> > >>> diff --git a/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c
> > >>> b/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c index
> > >>> 39d8509d96a0..b80164dd8ad8
> > >>> 100644
> > >>> --- a/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c
> > >>> +++ b/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c
> > >>> @@ -189,6 +189,7 @@ static int sun8i_dw_hdmi_bind(struct device *dev,
> > >>> struct device *master,>
> > >>>
> > >>> sun8i_hdmi_phy_init(hdmi->phy);
> > >>>
> > >>> plat_data->mode_valid = hdmi->quirks->mode_valid;
> > >>>
> > >>> + plat_data->drm_infoframe = hdmi->quirks->drm_infoframe;
> > >>>
> > >>> sun8i_hdmi_phy_set_ops(hdmi->phy, plat_data);
> > >>>
> > >>> platform_set_drvdata(pdev, hdmi);
> > >>>
> > >>> @@ -255,6 +256,7 @@ static const struct sun8i_dw_hdmi_quirks
> > >>> sun8i_a83t_quirks = {>
> > >>>
> > >>> static const struct sun8i_dw_hdmi_quirks sun50i_h6_quirks = {
> > >>>
> > >>> .mode_valid = sun8i_dw_hdmi_mode_valid_h6,
> > >>>
> > >>> + .drm_infoframe = true,
> > >>>
> > >>> };
> > >>>
> > >>> static const struct of_device_id sun8i_dw_hdmi_dt_ids[] = {
> > >>>
> > >>> diff --git a/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h
> > >>> b/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h index
> > >>> 720c5aa8adc1..2a0ec08ee236
> > >>> 100644
> > >>> --- a/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h
> > >>> +++ b/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h
> > >>> @@ -178,6 +178,7 @@ struct sun8i_dw_hdmi_quirks {
> > >>>
> > >>> enum drm_mode_status (*mode_valid)(struct drm_connector
> > >
> > > *connector,
> > >
> > >>> const struct
> > >
> > > drm_display_mode *mode);
> > >
> > >>> unsigned int set_rate : 1;
> > >>>
> > >>> + unsigned int drm_infoframe : 1;
> > >>
> > >> Again, drm_infoframe suggests it contains inforframe, but in fact it
> > >> just informs infoframe can be used, so again my suggestion
> > >> use_drm_infoframe.
> > >>
> > >> Moreover bool type seems more appropriate here.
> > >
> > > checkpatch will give warning if bool is used.
> >
> > Then I would say "fix/ignore checkpatch" :)
> >
> > But maybe there is a reason.
>
> Here's an old one from Linus: https://lkml.org/lkml/2013/9/1/154
>
> I'd say that bool in a struct is a waste of space compared to a 1 bit
> bitfield, especially when there already are other bitfields in the same
> struct.
> > Anyway I've tested and I do not see the warning, could you elaborate it.
>
> Maybe checkpatch.pl --strict?
It seems they removed that check:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?
id=7967656ffbfa493f5546c0f1
After reading that block of text, I'm not sure what would be prefered way for
this case.
Best regards,
Jernej
next prev parent reply other threads:[~2019-06-24 16:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 21:18 [PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata Jonas Karlman
2019-05-26 21:19 ` [PATCH 1/4] drm/bridge: dw-hdmi: Add Dynamic Range and Mastering InfoFrame support Jonas Karlman
2019-06-05 12:57 ` Neil Armstrong
2019-06-24 13:40 ` Andrzej Hajda
2019-05-26 21:20 ` [PATCH 2/4] drm/rockchip: Enable DRM InfoFrame support on RK3328 and RK3399 Jonas Karlman
2019-06-14 9:29 ` Heiko Stuebner
2019-06-24 14:43 ` Andrzej Hajda
2019-05-26 21:20 ` [PATCH 3/4] drm/meson: Enable DRM InfoFrame support on GXL, GXM and G12A Jonas Karlman
2019-06-05 12:55 ` Neil Armstrong
2019-06-24 14:59 ` Andrzej Hajda
2019-06-26 9:16 ` Neil Armstrong
2019-05-26 21:20 ` [PATCH 4/4] drm/sun4i: Enable DRM InfoFrame support on H6 Jonas Karlman
2019-06-24 15:03 ` Andrzej Hajda
2019-06-24 15:05 ` Jernej Škrabec
2019-06-24 15:49 ` Andrzej Hajda
2019-06-24 15:56 ` Chen-Yu Tsai
2019-06-24 16:03 ` Jernej Škrabec [this message]
2019-06-24 16:07 ` Chen-Yu Tsai
2019-06-24 16:59 ` Andrzej Hajda
2019-05-28 17:03 ` [PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata Jernej Škrabec
2019-06-20 14:40 ` Neil Armstrong
2019-06-21 9:01 ` Daniel Vetter
2019-06-23 23:30 ` Laurent Pinchart
2019-06-24 8:19 ` Neil Armstrong
2019-06-24 8:42 ` Daniel Vetter
2019-06-24 11:16 ` Laurent Pinchart
2019-06-24 15:27 ` Andrzej Hajda
2019-09-18 8:05 ` Neil Armstrong
2019-09-18 16:39 ` Jonas Karlman
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=44611965.cJa5QBey4U@jernej-laptop \
--to=jernej.skrabec@siol.net \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jonas@kwiboo.se \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=narmstrong@baylibre.com \
--cc=wens@csie.org \
--cc=zhengyang@rock-chips.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