From: "Ondřej Jirman" <megi@xff.cz>
To: saravanak@google.com, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, mripard@kernel.org, wens@csie.org,
jernej.skrabec@gmail.com, gregkh@linuxfoundation.org,
rafael@kernel.org, linux-kernel@vger.kernel.org,
andre.przywara@arm.com
Subject: fw_devlink=on and sunxi HDMI
Date: Sun, 16 May 2021 19:05:39 +0200 [thread overview]
Message-ID: <20210516170539.2yxe43qwezonuo3r@core> (raw)
Hello,
Linux 5.13-rc1 again has fw_devlink=on enabled by default. I've found that this
breaks probing display pipeline and HDMI output on sunxi boards, because of
fwnode_link between hdmi and hdmi-phy nodes.
HDMI device probe keeps being avoided with these repeated messages in dmesg:
platform 1ee0000.hdmi: probe deferral - supplier 1ef0000.hdmi-phy not ready
Both nodes have their own compatible, but are implemented by a single
struct device.
This looks like a kind of situation that's expected to break fw_devlink
expectations by my reading of the the e-mails about trying the fw_devlink=on
during 5.12 cycle.
Is this supposed to be solved by implementing the PHY node as it's own
device or by breaking the fwnode_link between the hdmi phy and hdmi nodes?
Seems like second solution would be quicker now that rc1 is out.
Where would be a good place to break that fwnode_link in code?
Or can the fw_devlink code be made aware of this situation, where two fwnodes
are implemented by the same Linux device, somehow?
Relevant references:
https://elixir.bootlin.com/linux/v5.13-rc1/source/drivers/gpu/drm/sun4i/sun8i_hdmi_phy.c#L600
https://elixir.bootlin.com/linux/v5.13-rc1/source/drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c#L212
https://elixir.bootlin.com/linux/v5.13-rc1/source/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi#L1176
kind regards,
o.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-05-16 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 17:05 Ondřej Jirman [this message]
2021-05-17 6:32 ` fw_devlink=on and sunxi HDMI Saravana Kannan
2021-05-17 8:29 ` Ondřej Jirman
2021-05-18 14:04 ` Maxime Ripard
2021-05-19 21:29 ` Saravana Kannan
2021-05-19 22:00 ` Ondřej Jirman
2021-05-19 22:15 ` Saravana Kannan
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=20210516170539.2yxe43qwezonuo3r@core \
--to=megi@xff.cz \
--cc=andre.przywara@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=wens@csie.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