[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG3jFytYcLP_1JJzoTU8YcwXp8==EpPdad5z02ROu8HtuaqfzQ@mail.gmail.com>
Date: Thu, 24 Mar 2022 13:07:56 +0100
From: Robert Foss <robert.foss@...aro.org>
To: Xin Ji <xji@...logixsemi.com>
Cc: Chen-Yu Tsai <wenst@...omium.org>,
Hsin-Yi Wang <hsinyi@...omium.org>,
dri-devel@...ts.freedesktop.org, Jonas Karlman <jonas@...boo.se>,
David Airlie <airlied@...ux.ie>, qwen@...logixsemi.com,
Neil Armstrong <narmstrong@...libre.com>,
linux-kernel@...r.kernel.org,
Jernej Skrabec <jernej.skrabec@...il.com>,
treapking@...omium.org, pihsun@...omium.org,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Andrzej Hajda <andrzej.hajda@...el.com>, tzungbi@...gle.com,
bliang@...logixsemi.com
Subject: Re: [PATCH v2] drm/bridge: anx7625: Set downstream sink into normal status
> > > > The driver uses DRM_DEV_* for logs. Can we use this?
> > > Hi Hsin-Yi, as comment in drm/drm_print.h:
> > > "NOTE: this is deprecated in favor of drm_dbg". DRM bridge driver not
> > > use DRM_DEV_* any more. I'll send a patch to replace all of DRM_DEV_*
> > > later.
> >
> > drm_dbg is better than dev_dbg though. With the former, you still get the
> > option to control it with the drm.debug module parameter, unlike the latter
> > which normally gets compiled out.
> >
> > Please use drm_dbg*.
> >
> > ChenYu
>
> Hi ChenYu, the parameter of drm_dbg is "drm", if use drm_dbg, it will
> change more code, I'll consider to upstream new patch to replace all of
> them later.
>
Alright, since the driver already uses these logging functions, let's
apply this patch and fix the logging function this driver uses in a
separate series.
Xin: Can you submit a patch/series that converts this driver to use
drm_dbg* functions instead?
Powered by blists - more mailing lists