From: Aleksandr Nogikh <nogikh@google.com>
To: aford173@gmail.com, l.stach@pengutronix.de, inki.dae@samsung.com,
jagan@amarulasolutions.com, m.szyprowski@samsung.com,
airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, dvyukov@google.com
Subject: drivers/gpu/drm/bridge/samsung-dsim.c link error
Date: Thu, 3 Aug 2023 16:42:27 +0200 [thread overview]
Message-ID: <20230803144227.2187749-1-nogikh@google.com> (raw)
Hello,
We've been seing the following linker error on arm64 syzbot instances:
ld.lld: error: undefined symbol: phy_mipi_dphy_get_default_config_for_hsclk
>>> referenced by samsung-dsim.c:731 (drivers/gpu/drm/bridge/samsung-dsim.c:731)
>>> drivers/gpu/drm/bridge/samsung-dsim.o:(samsung_dsim_init) in archive vmlinux.a
Steps to reproduce on the latest linux-next:
$ git checkout next-20230803
$ wget -O '.config' 'https://raw.githubusercontent.com/google/syzkaller/master/dashboard/config/linux/upstream-arm64-kasan.config'
$ make CC=clang ARCH=arm64 LD=ld.lld CROSS_COMPILE=aarch64-linux-gnu- olddefconfig
This also prints:
WARNING: unmet direct dependencies detected for GENERIC_PHY_MIPI_DPHY
Depends on [n]: GENERIC_PHY [=n]
Selected by [y]:
- DRM_NWL_MIPI_DSI [=y] && DRM_BRIDGE [=y] && DRM [=y] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]
- DRM_SAMSUNG_DSIM [=y] && DRM [=y] && DRM_BRIDGE [=y] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]
$ make CC=clang ARCH=arm64 LD=ld.lld CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc)
The kernel should have still compiled fine even despite the message above, right?
Could you please take a look?
--
Thank you!
Aleksandr
next reply other threads:[~2023-08-03 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 14:42 Aleksandr Nogikh [this message]
2023-08-03 15:24 ` Adam Ford
2023-08-04 2:01 ` Randy Dunlap
2023-08-04 2:26 ` Adam Ford
2023-08-04 2:37 ` Randy Dunlap
2023-08-04 2:42 ` Adam Ford
2023-08-04 2:47 ` Randy Dunlap
2023-08-04 10:19 ` Aleksandr Nogikh
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=20230803144227.2187749-1-nogikh@google.com \
--to=nogikh@google.com \
--cc=aford173@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=inki.dae@samsung.com \
--cc=jagan@amarulasolutions.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=syzkaller@googlegroups.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®