From: "Jernej Škrabec" <jernej.skrabec-gGgVlfcn5nU@public.gmane.org>
To: Maxime Ripard <maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
Cc: Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org>,
Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [PATCH 5/5] ARM: sun8i: dts: drop A64 HDMI PHY fallback compatible from R40 DT
Date: Mon, 10 Sep 2018 16:32:30 +0200 [thread overview]
Message-ID: <1926288.mXGsSvSKgU@jernej-laptop> (raw)
In-Reply-To: <20180910142354.5ldexkvnan6ohz4x@flea>
Dne ponedeljek, 10. september 2018 ob 16:23:54 CEST je Maxime Ripard
napisal(a):
> On Fri, Sep 07, 2018 at 03:22:34PM +0800, Icenowy Zheng wrote:
> > The R40 HDMI PHY seems to be different to the A64 one, the A64 one
> > has no input mux, but the R40 one has.
> >
> > Drop the A64 fallback compatible from the HDMI PHY node in R40 DT.
> >
> > Signed-off-by: Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org>
> > ---
> >
> > arch/arm/boot/dts/sun8i-r40.dtsi | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/sun8i-r40.dtsi
> > b/arch/arm/boot/dts/sun8i-r40.dtsi index ffd9f00f74a4..5f547c161baf
> > 100644
> > --- a/arch/arm/boot/dts/sun8i-r40.dtsi
> > +++ b/arch/arm/boot/dts/sun8i-r40.dtsi
> > @@ -800,8 +800,7 @@
> >
> > };
> >
> > hdmi_phy: hdmi-phy@1ef0000 {
> >
> > - compatible = "allwinner,sun8i-r40-hdmi-phy",
> > - "allwinner,sun50i-a64-hdmi-phy";
> > + compatible = "allwinner,sun8i-r40-hdmi-phy";
>
> If you could use the A64 phy before, you can still use it now.
Not exactly. Given that we don't know how to switch between HDMI PHY clock
parents on A64 (if it is actually connected at all, there is no information
about that in manual and AW didn't answered our questions, despite asking them
through different channels), A64 compatible will be associated with quirk,
which will tell that only one clock parent is usable.
However, R40 HDMI PHY has definetly two clock parents, as it was tested by me
and Icenowy and we know how to switch between them without issues.
Technically, we could have A64 compatible there, but that would mean only
single PHY parent is considered instead of two.
Best regards,
Jernej
next prev parent reply other threads:[~2018-09-10 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 7:22 [PATCH 0/5] Fix A64 HDMI PHY device tree binding Icenowy Zheng
2018-09-07 7:22 ` [PATCH 2/5] drm: sun4i: drop second PLL from A64 HDMI PHY Icenowy Zheng
2018-09-07 7:22 ` [PATCH 3/5] dt-bindings: sun4i-drm: add compatible for R40 " Icenowy Zheng
[not found] ` <20180907072234.48282-1-icenowy-h8G6r0blFSE@public.gmane.org>
2018-09-07 7:22 ` [PATCH 1/5] dt-bindings: sun4i-drm: drop second PLL from A64 HDMI PHY binding Icenowy Zheng
[not found] ` <20180907072234.48282-2-icenowy-h8G6r0blFSE@public.gmane.org>
2018-09-10 14:22 ` Maxime Ripard
2018-09-07 7:22 ` [PATCH 4/5] drm/sun4i: add support for R40 HDMI PHY Icenowy Zheng
2018-09-10 5:03 ` [PATCH 0/5] Fix A64 HDMI PHY device tree binding Chen-Yu Tsai
2018-09-07 7:22 ` [PATCH 5/5] ARM: sun8i: dts: drop A64 HDMI PHY fallback compatible from R40 DT Icenowy Zheng
[not found] ` <20180907072234.48282-6-icenowy-h8G6r0blFSE@public.gmane.org>
2018-09-10 14:23 ` Maxime Ripard
2018-09-10 14:32 ` Jernej Škrabec [this message]
2018-09-17 14:54 ` Maxime Ripard
2018-09-17 22:57 ` Icenowy Zheng
2018-09-19 16:20 ` [linux-sunxi] " Chen-Yu Tsai
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=1926288.mXGsSvSKgU@jernej-laptop \
--to=jernej.skrabec-gggvlfcn5nu@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=icenowy-h8G6r0blFSE@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=wens-jdAy2FN1RRM@public.gmane.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