From: Corentin Labbe <clabbe.montjoie@gmail.com> To: Linus Walleij <linus.walleij@linaro.org> Cc: Hans Ulli Kroll <ulli.kroll@googlemail.com>, Linux ARM <linux-arm-kernel@lists.infradead.org>, linux-kernel <linux-kernel@vger.kernel.org> Subject: Re: gemini: sl3516: Mainlining of NS 2502 Date: Tue, 6 Apr 2021 14:05:19 +0200 [thread overview] Message-ID: <YGxOf8pKN8Ip/kCl@Red> (raw) In-Reply-To: <CACRpkdZ_barDrLvD2UBKo+GA-F+g72uMQx8CfRK2YLRodpeyUA@mail.gmail.com> Le Tue, Apr 06, 2021 at 10:15:51AM +0200, Linus Walleij a écrit : > On Mon, Apr 5, 2021 at 8:39 PM Corentin Labbe <clabbe.montjoie@gmail.com> wrote: > > > I own an Edimax NS 2502, which is a NAS based on StormLinix 3516. > > I successfully upgraded it with a recent Linux. > > Pretty cool! > > > mdio0: ethernet-phy { > > compatible = "virtual,mdio-gpio"; > > gpios = <&gpio0 22 GPIO_ACTIVE_HIGH>, /* MDC */ > > <&gpio0 21 GPIO_ACTIVE_HIGH>; /* MDIO */ > > #address-cells = <1>; > > #size-cells = <0>; > > phy0: ethernet-phy@1 { > > reg = <1>; > > device_type = "ethernet-phy"; > > }; > > }; > > This looks like the most typical way to attach an MDIO phy. > > I always try to identify the exact component used on the board. Do you have > a high res board photo? > Hello You could find photos at http://kernel.montjoie.ovh/gemini/ There are also photos of another SL3516 SoC based device (a SSI 1328 NAS), but I fail to setup a serial on it, so I keep it for later. > Realtek RTL82111 is the most common configuration. > > Compare to the D-Linux DNS-313 DTS: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/gemini-dlink-dns-313.dts > > Try just copying the whole pinctrl-gmii section! > > > > syscon: syscon@40000000 { > > pinctrl { > > /* > > * gpio0agrp cover line 0-4 > > * gpio0bgrp cover line 5 > > */ > > gpio0_default_pins: pinctrl-gpio0 { > > mux { > > function = "gpio0"; > > groups = "gpio0agrp", > > "gpio0bgrp"; > > }; > > }; > > Change groups to > > groups = "gpio0agrp", "gpio0bgrp", "gpio0hgrp"; > > So you mux in group h which is where the GPIO 21, 22 go out > to the MDIO on 3516 IIUC. The right mux out is pretty important, > if you have vendor source code, please share so I can check how > they set it up. > No change, probably due to all pinctrl-gemini 40000000.syscon:pinctrl: could not map pin config for "R8 GMAC0 RXDV" Please see http://kernel.montjoie.ovh/gemini/bootlog6.txt , I have added some pr_info in gmac. I have put in the directory, the final dtb which I use. The vendor source could be found at https://www.edimax.com/edimax/mw/cufiles/files/download/OpenSourceCode/transfer/Wireless/NAS/NAS-GPL-source.zip > > BUT neither ethernet nor USB works. > > For USB try this patch: > https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git/commit/?h=gemini-usb&id=cbaf6cdf770b90de5f10bfa5112c679f1dffe948 > One of the USB port is now working. > Pls report progress! I hope we can mainline this device. > I hope too. Note that I have also started to work on the gemini crypto driver. Thanks for your help
WARNING: multiple messages have this Message-ID (diff)
From: Corentin Labbe <clabbe.montjoie@gmail.com> To: Linus Walleij <linus.walleij@linaro.org> Cc: Hans Ulli Kroll <ulli.kroll@googlemail.com>, Linux ARM <linux-arm-kernel@lists.infradead.org>, linux-kernel <linux-kernel@vger.kernel.org> Subject: Re: gemini: sl3516: Mainlining of NS 2502 Date: Tue, 6 Apr 2021 14:05:19 +0200 [thread overview] Message-ID: <YGxOf8pKN8Ip/kCl@Red> (raw) In-Reply-To: <CACRpkdZ_barDrLvD2UBKo+GA-F+g72uMQx8CfRK2YLRodpeyUA@mail.gmail.com> Le Tue, Apr 06, 2021 at 10:15:51AM +0200, Linus Walleij a écrit : > On Mon, Apr 5, 2021 at 8:39 PM Corentin Labbe <clabbe.montjoie@gmail.com> wrote: > > > I own an Edimax NS 2502, which is a NAS based on StormLinix 3516. > > I successfully upgraded it with a recent Linux. > > Pretty cool! > > > mdio0: ethernet-phy { > > compatible = "virtual,mdio-gpio"; > > gpios = <&gpio0 22 GPIO_ACTIVE_HIGH>, /* MDC */ > > <&gpio0 21 GPIO_ACTIVE_HIGH>; /* MDIO */ > > #address-cells = <1>; > > #size-cells = <0>; > > phy0: ethernet-phy@1 { > > reg = <1>; > > device_type = "ethernet-phy"; > > }; > > }; > > This looks like the most typical way to attach an MDIO phy. > > I always try to identify the exact component used on the board. Do you have > a high res board photo? > Hello You could find photos at http://kernel.montjoie.ovh/gemini/ There are also photos of another SL3516 SoC based device (a SSI 1328 NAS), but I fail to setup a serial on it, so I keep it for later. > Realtek RTL82111 is the most common configuration. > > Compare to the D-Linux DNS-313 DTS: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/gemini-dlink-dns-313.dts > > Try just copying the whole pinctrl-gmii section! > > > > syscon: syscon@40000000 { > > pinctrl { > > /* > > * gpio0agrp cover line 0-4 > > * gpio0bgrp cover line 5 > > */ > > gpio0_default_pins: pinctrl-gpio0 { > > mux { > > function = "gpio0"; > > groups = "gpio0agrp", > > "gpio0bgrp"; > > }; > > }; > > Change groups to > > groups = "gpio0agrp", "gpio0bgrp", "gpio0hgrp"; > > So you mux in group h which is where the GPIO 21, 22 go out > to the MDIO on 3516 IIUC. The right mux out is pretty important, > if you have vendor source code, please share so I can check how > they set it up. > No change, probably due to all pinctrl-gemini 40000000.syscon:pinctrl: could not map pin config for "R8 GMAC0 RXDV" Please see http://kernel.montjoie.ovh/gemini/bootlog6.txt , I have added some pr_info in gmac. I have put in the directory, the final dtb which I use. The vendor source could be found at https://www.edimax.com/edimax/mw/cufiles/files/download/OpenSourceCode/transfer/Wireless/NAS/NAS-GPL-source.zip > > BUT neither ethernet nor USB works. > > For USB try this patch: > https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git/commit/?h=gemini-usb&id=cbaf6cdf770b90de5f10bfa5112c679f1dffe948 > One of the USB port is now working. > Pls report progress! I hope we can mainline this device. > I hope too. Note that I have also started to work on the gemini crypto driver. Thanks for your help _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-06 12:05 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-05 18:39 gemini: sl3516: Mainlining of NS 2502 Corentin Labbe 2021-04-05 18:39 ` Corentin Labbe 2021-04-05 20:36 ` Andrew Lunn 2021-04-05 20:36 ` Andrew Lunn 2021-04-06 9:06 ` Corentin Labbe 2021-04-06 9:06 ` Corentin Labbe 2021-04-06 8:15 ` Linus Walleij 2021-04-06 8:15 ` Linus Walleij 2021-04-06 12:05 ` Corentin Labbe [this message] 2021-04-06 12:05 ` Corentin Labbe 2021-04-07 9:34 ` Linus Walleij 2021-04-07 9:34 ` Linus Walleij 2021-05-05 19:26 ` Corentin Labbe 2021-05-05 19:26 ` Corentin Labbe 2021-05-05 23:56 ` Linus Walleij 2021-05-05 23:56 ` Linus Walleij 2021-05-06 9:02 ` Daniel Palmer 2021-05-06 9:02 ` Daniel Palmer 2021-05-12 20:14 ` Corentin Labbe 2021-05-12 20:14 ` Corentin Labbe
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=YGxOf8pKN8Ip/kCl@Red \ --to=clabbe.montjoie@gmail.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=ulli.kroll@googlemail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.