Jump to content

sunxi and sunxi64 NEXT dropping 4.14.y for 4.17.y?


Igor
 Share

Recommended Posts

4.17.y is, even not LTS, but probably better than heavily patched 4.14.y in any way. Shall we do this switch now and start preparing 4.18.y on a DEV?

Link to comment
Share on other sites

When discussing a problem make sure to provide full logs!

17 minutes ago, zador.blood.stained said:

but I would prefer to do it in a separate repository branch


That's fine. I want to know for automated build process ... currently, it's broken and the simplest way is to attach DEV to 4.17.y and leave as is until development branch is matured enough to merge. 

Link to comment
Share on other sites

On 6/18/2018 at 2:24 AM, zador.blood.stained said:

Yes, we need to start working on 4.17 or 4.18 (which in addition has basic DVFS for H3), but I would prefer to do it in a separate repository branch (I already created one and cleaned up obviously obsolete patches there) rather than in the "dev" kernel target.

 

BTW, I built 64-bit 4.17.2 in the dev branch today and did some light testing using an Orange PI Zero Plus 2 H5.

 

Most things worked well (816MHz, HDMI display, WIFI, LEDs). The only thing I saw that was nonfunctional was the USB ports.

 

Looking at the DT, the USB ports & PHY are listed but disabled:

 

                usb@1c1b400 {
                        phy-names = "usb";
                        resets = <0x3 0x13 0x3 0x17>;
                        interrupts = <0x0 0x4b 0x4>;
                        clocks = <0x3 0x22 0x3 0x26 0x3 0x5d>;
                        compatible = "allwinner,sun8i-h3-ohci", "generic-ohci";
                        status = "disabled";
                        phys = <0x11 0x1>;
                        reg = <0x1c1b400 0x100>;
                        phandle = <0x36>;
                };

                phy@1c19400 {
                        clock-names = "usb0_phy", "usb1_phy", "usb2_phy", "usb3_phy";
                        reg-names = "phy_ctrl", "pmu0", "pmu1", "pmu2", "pmu3";
                        resets = <0x3 0x0 0x3 0x1 0x3 0x2 0x3 0x3>;
                        clocks = <0x3 0x58 0x3 0x59 0x3 0x5a 0x3 0x5b>;
                        #phy-cells = <0x1>;
                        compatible = "allwinner,sun8i-h3-usb-phy";
                        status = "disabled";
                        reg = <0x1c19400 0x2c 0x1c1a800 0x4 0x1c1b800 0x4 0x1c1c800 0x4 0x1c1d800 0x4>;
                        phandle = <0x11>;
                        reset-names = "usb0_reset", "usb1_reset", "usb2_reset", "usb3_reset";
                };
 

I'm not that familiar with DT, so not sure if the USB status is being disabled in u-boot and passed into the kernel, or if a kernel patch is needed to fix this.

 

I'm happy to test potential fixes, else just passing along test findings.

 

-JB

twitter: @JBrooksBSI 

 

Link to comment
Share on other sites

4 hours ago, martinayotte said:

To enable those USB ports, you need to use overlays by adding them in /boot/armbianEnv.txt

 

Both the next & dev branches contain identical overlay lines in /boot/armbianEnv.txt:

 

overlay_prefix=sun50i-h5
overlays=usbhost2 usbhost3
 

USB is working with kernel 4.14.41 + u-boot v2017.11, but not with kernel 4.17.2 + u-boot 2018.03.

 

-JB

Link to comment
Share on other sites

Just now, John Brooks said:

Both the next & dev branches contain identical overlay lines in /boot/armbianEnv.txt:

 

overlay_prefix=sun50i-h5
overlays=usbhost2 usbhost3
 

USB is working with kernel 4.14.41 + u-boot v2017.11, but not with kernel 4.17.2 + u-boot 2018.03.

 

-JB

 

BTW, I noticed that there is a USB-related patch which is disabled for both the 4.14 next and 4.17 dev branches:

 

fix-usb-phy-probe.patch.disabled

 

I enabled the patch as a test, but it throws compiler errors due to requiring a probe index:

 

-int sunxi_usb_phy_probe(void)

+int sunxi_usb_phy_probe(int i)  

 

-JB

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...