linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [5.0-rc3] arm64: sun50i: h6: Pine H64 uart2 vs. emac
@ 2019-01-23 11:16 Andreas Färber
  2019-01-24 11:19 ` Chen-Yu Tsai
  0 siblings, 1 reply; 2+ messages in thread
From: Andreas Färber @ 2019-01-23 11:16 UTC (permalink / raw)
  To: linux-arm-kernel; +Cc: Maxime Ripard, Chen-Yu Tsai

Hi guys,

In 5.0 the Pine H64's Ethernet has become usable (thanks for your work).

I'm now trying to use the Pi-2 UART pins (supposedly PD19/PD20 UART2);
however the H6 .dtsi reserves those pins in ext_rgmii_pins, causing an
error. If I overwrite its pins property (which is a little cumbersome,
any chance we can split them off into a separate node?) Ethernet is no
longer working. I'm guessing that's related to MDIO/PHY, as the
interface does show up, just doesn't get the link up.

Is it not possible to use Ethernet and GPIO header at the same time,
unlike the original Pine64+, or am I missing some required DT change?

Thanks,
Andreas


        fragment@0 {
                reg = <0>;

                target = <&pio>;

                __overlay__ {
                        uart2_pins: uart2-pins {
                                pins = "PD19", "PD20";
                                function = "uart2";
                        };
                };
        };

        fragment@1 {
                reg = <1>;

                target = <&ext_rgmii_pins>;

                __overlay__ {
                        pins = "PD0", "PD1", "PD2", "PD3", "PD4",
                               "PD5", "PD7", "PD8", "PD9", "PD10",
                               "PD11", "PD12", "PD13"/*, "PD19", "PD20"*/;
                };
        };

        fragment@2 {
                reg = <2>;

                target = <&uart2>;

                __overlay__ {
                        status = "okay";
                        pinctrl-names = "default";
                        pinctrl-0 = <&uart2_pins>;
                };
        };


-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [5.0-rc3] arm64: sun50i: h6: Pine H64 uart2 vs. emac
  2019-01-23 11:16 [5.0-rc3] arm64: sun50i: h6: Pine H64 uart2 vs. emac Andreas Färber
@ 2019-01-24 11:19 ` Chen-Yu Tsai
  0 siblings, 0 replies; 2+ messages in thread
From: Chen-Yu Tsai @ 2019-01-24 11:19 UTC (permalink / raw)
  To: Andreas Färber; +Cc: Maxime Ripard, linux-arm-kernel

On Wed, Jan 23, 2019 at 7:16 PM Andreas Färber <afaerber@suse.de> wrote:
>
> Hi guys,
>
> In 5.0 the Pine H64's Ethernet has become usable (thanks for your work).
>
> I'm now trying to use the Pi-2 UART pins (supposedly PD19/PD20 UART2);
> however the H6 .dtsi reserves those pins in ext_rgmii_pins, causing an
> error. If I overwrite its pins property (which is a little cumbersome,
> any chance we can split them off into a separate node?) Ethernet is no
> longer working. I'm guessing that's related to MDIO/PHY, as the
> interface does show up, just doesn't get the link up.

Correct, the pins happen to be the MDIO data and clock pins.

> Is it not possible to use Ethernet and GPIO header at the same time,
> unlike the original Pine64+, or am I missing some required DT change?

Looks like it won't be possible. I suggest using UART3 instead, which
are pins PD23/PD24, and correspond to pins 37/38 on the GPIO header.

ChenYu

> Thanks,
> Andreas
>
>
>         fragment@0 {
>                 reg = <0>;
>
>                 target = <&pio>;
>
>                 __overlay__ {
>                         uart2_pins: uart2-pins {
>                                 pins = "PD19", "PD20";
>                                 function = "uart2";
>                         };
>                 };
>         };
>
>         fragment@1 {
>                 reg = <1>;
>
>                 target = <&ext_rgmii_pins>;
>
>                 __overlay__ {
>                         pins = "PD0", "PD1", "PD2", "PD3", "PD4",
>                                "PD5", "PD7", "PD8", "PD9", "PD10",
>                                "PD11", "PD12", "PD13"/*, "PD19", "PD20"*/;
>                 };
>         };
>
>         fragment@2 {
>                 reg = <2>;
>
>                 target = <&uart2>;
>
>                 __overlay__ {
>                         status = "okay";
>                         pinctrl-names = "default";
>                         pinctrl-0 = <&uart2_pins>;
>                 };
>         };
>
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-01-24 11:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-23 11:16 [5.0-rc3] arm64: sun50i: h6: Pine H64 uart2 vs. emac Andreas Färber
2019-01-24 11:19 ` Chen-Yu Tsai

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).