From: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
a.hajda@samsung.com
Cc: jonas@kwiboo.se, airlied@linux.ie, robert.foss@linaro.org,
dri-devel@lists.freedesktop.org, narmstrong@baylibre.com,
linux-kernel@vger.kernel.org, jernej.skrabec@gmail.com,
Laurent.pinchart@ideasonboard.com, kernel@collabora.com
Subject: Re: [PATCH] drm/bridge: parade-ps8640: Assign drm_device to dp aux channel
Date: Wed, 10 Nov 2021 15:02:15 +0200 [thread overview]
Message-ID: <feb2ebef-5859-db38-8243-a4396770d736@collabora.com> (raw)
In-Reply-To: <20211104102035.243305-1-angelogioacchino.delregno@collabora.com>
On 04.11.21 12:20, AngeloGioacchino Del Regno wrote:
> As it was done with other bridge drivers and to solve a warning coming
> from drm_dp_aux_register(), add a backpointer to drm_device in the
> drm_dp_aux that we're registering.
>
it is common to dump the exact warning in the commit log so people can locate it later.
Maybe also add 'Fixes' tag?
apart of that
Reviewed-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> drivers/gpu/drm/bridge/parade-ps8640.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/bridge/parade-ps8640.c b/drivers/gpu/drm/bridge/parade-ps8640.c
> index 191cc196c9d1..20d8e606d543 100644
> --- a/drivers/gpu/drm/bridge/parade-ps8640.c
> +++ b/drivers/gpu/drm/bridge/parade-ps8640.c
> @@ -455,6 +455,7 @@ static int ps8640_bridge_attach(struct drm_bridge *bridge,
> goto err_dsi_attach;
> }
>
> + ps_bridge->aux.drm_dev = bridge->dev;
> ret = drm_dp_aux_register(&ps_bridge->aux);
> if (ret) {
> dev_err(dev, "failed to register DP AUX channel: %d\n", ret);
>
prev parent reply other threads:[~2021-11-10 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 10:20 [PATCH] drm/bridge: parade-ps8640: Assign drm_device to dp aux channel AngeloGioacchino Del Regno
2021-11-10 13:02 ` Dafna Hirschfeld [this message]
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=feb2ebef-5859-db38-8243-a4396770d736@collabora.com \
--to=dafna.hirschfeld@collabora.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.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