@mkshevetskiy I'm applying the patches and
drivers/pinctrl/airoha/pinctrl-airoha.cis confusing in the patches for mediatek tree╭─sirherobrine23@matheus-note /mnt/Data/airoha_e…
In RouterOS, it seems that it keeps the SPI in control of the NOR (SPI cs0) and the active NAND in (SP0 cs1). Regarding the medium, I'm not very sure how it's handled since I don't have access…
@Sirherobrine23 your tod_1pps patch is not good enougth. Here is proper variant. @merbanan Am I right about pin 21 ?
--- a/drivers/pinctrl/airoha/pinctrl-en7523.c
+++ b/drivers/pinctrl/…
In theory you can reset and configure the phy in uboot and then never touch it in linux. But that sounds stupid and there should be enough other pins to support bit bang mdio from other…
I'm currently working on my internet connection, so there will be times when I won't be able to respond.
in the mikrotik case mdio uses the same pin as spi_cs1.
We have an…
in the microtic case mdio uses the same pin as spi_cs1.
We have an ugly hack in our old u-boot to avoid it
- save values of RG_GPIO_2ND_I2C_MODE (1FA20210), RG_GPIO_SPI_CS1_MODE(1FA20214),…
your probably missed
&switch {
pinctrl-names = "default";
pinctrl-0 = <&mdio_pins>;
status = "okay";
};
&pinctrl {
gpio-ranges = <&pinctrl 0 12 28>;
mdio_pins:…
it should be
&pinctrl { gpio-ranges = <&pinctrl 0 12 28>; // <== you probably missed it ... }
This table is the list of GPIOs that we have mapped. In some devices we use PINs 11 and 10, and they are not mapped because when we use
&pinctrlto map the GPIO, it takes the pin from…
Actually airoha pin muxing does not require actual pin knowlegde, it operates using function and groups only.
So you can do some bad practice:
- define fake pin (because you dont know proper…
This changes breaks a lot en7523 pinctrl driver. Some notes
- pin number used in gpioX_pins should match with pin number used in PINCTRL_PIN, but
static const int gpio0_pins[] = { 12…
Is there any official announcement from Airoha? I am working on porting your pinctrl driver to u-boot. From my point of view it's better keep using en7523 name.