From: "Andy Yan" <andyshrk@163.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
mripard@kernel.org, neil.armstrong@linaro.org,
dri-devel@lists.freedesktop.org, dianders@chromium.org,
jani.nikula@intel.com, lyude@redhat.com, jonathanh@nvidia.com,
p.zabel@pengutronix.de, simona@ffwll.ch, victor.liu@nxp.com,
rfoss@kernel.org, chunkuang.hu@kernel.org,
cristian.ciocaltea@collabora.com,
Laurent.pinchart@ideasonboard.com, linux-arm-msm@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
freedreno@lists.freedesktop.org,
"Andy Yan" <andy.yan@rock-chips.com>
Subject: Re:Re: [PATCH v3 2/2] drm/bridge: Pass down connector to drm bridge detect hook
Date: Tue, 15 Jul 2025 13:54:29 +0800 (CST) [thread overview]
Message-ID: <23a4efde.4f62.1980ca61c5e.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <85ple2ju6m.wl-ashutosh.dixit@intel.com>
Hi Dixit,
At 2025-07-15 06:15:13, "Dixit, Ashutosh" <ashutosh.dixit@intel.com> wrote:
>On Thu, 03 Jul 2025 14:27:43 -0700, Dmitry Baryshkov wrote:
>>
>> On Thu, Jul 03, 2025 at 08:49:53PM +0800, Andy Yan wrote:
>
>Hi Andy,
>
>> > From: Andy Yan <andy.yan@rock-chips.com>
>> >
>> > In some application scenarios, we hope to get the corresponding
>> > connector when the bridge's detect hook is invoked.
>> >
>> > In most cases, we can get the connector by drm_atomic_get_connector_for_encoder
>> > if the encoder attached to the bridge is enabled, however there will
>> > still be some scenarios where the detect hook of the bridge is called
>> > but the corresponding encoder has not been enabled yet. For instance,
>> > this occurs when the device is hot plug in for the first time.
>> >
>> > Since the call to bridge's detect is initiated by the connector, passing
>> > down the corresponding connector directly will make things simpler.
>> >
>> > Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>> > ---
>> >
>>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>
>This seems to be breaking 'make allmodconfig'. This is what is being seen:
>
>../drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c: In function ‘ge_b850v3_lvds_detect’:
>../drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c:145:16: error: too few arguments to function ‘ge_b850v3_lvds_bridge_detect’
> 145 | return ge_b850v3_lvds_bridge_detect(&ge_b850v3_lvds_ptr->bridge);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>../drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c:124:1: note: declared here
> 124 | ge_b850v3_lvds_bridge_detect(struct drm_bridge *bridge, struct drm_connector *connector)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>../drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c:146:1: error: control reaches end of non-void function [-Werror=return-type]
> 146 | }
> | ^
>
>Could you please post a fix for this. Maybe do 'make allmodconfig' to check
>if you haven't missed anything else.
Thanks for catching this. I have sent a fix for this:
https://lore.kernel.org/dri-devel/20250715054754.800765-1-andyshrk@163.com/T/#u
And before releasing the fix patch this time, I had already ensured that the "make allmodconfig" compilation was successful.
Many thanks.
>
>Thanks.
>--
>Ashutosh
next prev parent reply other threads:[~2025-07-15 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 12:49 [PATCH v3 0/2] " Andy Yan
2025-07-03 12:49 ` [PATCH v3 1/2] drm/bridge: Make dp/hdmi_audio_* callback keep the same paramter order with get_modes Andy Yan
2025-07-03 12:49 ` [PATCH v3 2/2] drm/bridge: Pass down connector to drm bridge detect hook Andy Yan
2025-07-03 21:27 ` Dmitry Baryshkov
2025-07-14 22:15 ` Dixit, Ashutosh
2025-07-15 5:54 ` Andy Yan [this message]
2025-07-14 10:24 ` Re:[PATCH v3 0/2] " Andy Yan
2025-07-14 15:25 ` [PATCH " Dmitry Baryshkov
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=23a4efde.4f62.1980ca61c5e.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andy.yan@rock-chips.com \
--cc=ashutosh.dixit@intel.com \
--cc=chunkuang.hu@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lyude@redhat.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=victor.liu@nxp.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
all inboxes | Powered by JetHome®