Re: WDS stopped working in 21.02, looking for bug in netifd
Felix, I took the last openwrt snapshot and compiled netifd from master with your patch applied and installed it. Result: After boot wlan0.sta1 was DOWN. After "/etc/init.d/network restart" it was UP and the connection worked! After another "/etc/init.d/network restart" it was DOWN again. After reboot it was UP again and working. After "/etc/init.d/network restart" it was DOWN again. - D.H. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] ramips: fix ralink_i2s_debugfs_remove declaration
Correct ralink_i2s_debugfs_remove declaration in ralink patches when
CONFIG_DEBUG_FS is not selected.
Signed-off-by: Eneas U de Queiroz
---
Fixes the following error, when compiling without DEBUG_FS:
sound/soc/ralink/ralink-i2s.c:678:53: warning: 'struct fsl_ssi_dbg' declared
inside parameter list will not be visible outside of this definition or
declaration
static inline void ralink_i2s_debugfs_remove(struct fsl_ssi_dbg *ssi_dbg)
^~~
sound/soc/ralink/ralink-i2s.c: In function 'ralink_i2s_probe':
sound/soc/ralink/ralink-i2s.c:935:28: error: passing argument 1 of
'ralink_i2s_debugfs_remove' from incompatible pointer type
[-Werror=incompatible-pointer-types]
ralink_i2s_debugfs_remove(i2s);
^~~
sound/soc/ralink/ralink-i2s.c:678:66: note: expected 'struct fsl_ssi_dbg *' but
argument is of type 'struct ralink_i2s *'
static inline void ralink_i2s_debugfs_remove(struct fsl_ssi_dbg *ssi_dbg)
^~~
sound/soc/ralink/ralink-i2s.c: In function 'ralink_i2s_remove':
sound/soc/ralink/ralink-i2s.c:947:28: error: passing argument 1 of
'ralink_i2s_debugfs_remove' from incompatible pointer type
[-Werror=incompatible-pointer-types]
ralink_i2s_debugfs_remove(i2s);
^~~
sound/soc/ralink/ralink-i2s.c:678:66: note: expected 'struct fsl_ssi_dbg *' but
argument is of type 'struct ralink_i2s *'
static inline void ralink_i2s_debugfs_remove(struct fsl_ssi_dbg *ssi_dbg)
^~~
At top level:
sound/soc/ralink/ralink-i2s.c:146:13: warning: 'ralink_i2s_dump_regs' defined
but not used [-Wunused-function]
static void ralink_i2s_dump_regs(struct ralink_i2s *i2s)
^~~~
cc1: some warnings being treated as errors
make[7]: *** [scripts/Makefile.build:280: sound/soc/ralink/ralink-i2s.o] Error 1
make[6]: *** [scripts/Makefile.build:497: sound/soc/ralink] Error 2
make[5]: *** [scripts/Makefile.build:497: sound/soc] Error 2
make[4]: *** [Makefile:1822: sound] Error 2
.../linux/ramips/patches-5.10/835-asoc-add-mt7620-support.patch | 2 +-
.../linux/ramips/patches-5.4/0048-asoc-add-mt7620-support.patch | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ramips/patches-5.10/835-asoc-add-mt7620-support.patch
b/target/linux/ramips/patches-5.10/835-asoc-add-mt7620-support.patch
index 255c8d751a..680b678168 100644
--- a/target/linux/ramips/patches-5.10/835-asoc-add-mt7620-support.patch
+++ b/target/linux/ramips/patches-5.10/835-asoc-add-mt7620-support.patch
@@ -738,7 +738,7 @@ Signed-off-by: John Crispin
+ return 0;
+}
+
-+static inline void ralink_i2s_debugfs_remove(struct fsl_ssi_dbg *ssi_dbg)
++static inline void ralink_i2s_debugfs_remove(struct ralink_i2s *i2s)
+{
+}
+#endif
diff --git a/target/linux/ramips/patches-5.4/0048-asoc-add-mt7620-support.patch
b/target/linux/ramips/patches-5.4/0048-asoc-add-mt7620-support.patch
index cffdc4f4a1..4b9c877a7f 100644
--- a/target/linux/ramips/patches-5.4/0048-asoc-add-mt7620-support.patch
+++ b/target/linux/ramips/patches-5.4/0048-asoc-add-mt7620-support.patch
@@ -738,7 +738,7 @@ Signed-off-by: John Crispin
+ return 0;
+}
+
-+static inline void ralink_i2s_debugfs_remove(struct fsl_ssi_dbg *ssi_dbg)
++static inline void ralink_i2s_debugfs_remove(struct ralink_i2s *i2s)
+{
+}
+#endif
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: WDS stopped working in 21.02, looking for bug in netifd
Please test if applying this change to netifd fixes the issue. I am currently building the toolchain for the current snapshot, so I can test on the current snapshot. So far I have only been able to test the patch on 21.02. Since the patch does not apply cleanly I tried to versions of the patch. Version 1: Apply everything except the line with dev->bpdu_filer = <...>. With this version, it seems that now the interface is *always* in state DOWN after booting and it never works even if manually set to UP. Version 2: Apply only the last two hunks of the patch. With this version, I still get random UP/DOWN behaviour at boot, but now "/etc/init.d/network restart" seems to sometimes give me a working state with the interface UP and the connection working, which I am quite sure I never had before. But since the whole behaviour has a random element of course I can not be 100% sure. I will try with the snapshot as soon as possible. D.H. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH v2] realtek: fix RTL8231 gpio expander for high GPIOs
On Mon, 2021-09-20 at 20:13 +0300, Paul Fertser wrote:
> GPIOs > 31 require special handling. This patch fixes both the
> initialisation and direction get/set operations.
>
> Signed-off-by: Paul Fertser
> ---
>
> Notes:
> Changes from v1:
> - Do not modify high GPIOs direction bits on init
Thanks for the update.
Reviewed-by: Sander Vanheule
>
> .../realtek/files-5.4/drivers/gpio/gpio-rtl8231.c | 13 -
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
> b/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
> index 031f60f5307c..a8ffcdc31368 100644
> --- a/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
> +++ b/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
> @@ -106,12 +106,11 @@ static int rtl8231_pin_dir(struct rtl8231_gpios *gpios,
> u32 gpio,
> u32 dir)
> u32 v;
> int pin_sel_addr = RTL8231_GPIO_PIN_SEL(gpio);
> int pin_dir_addr = RTL8231_GPIO_DIR(gpio);
> - int pin = gpio % 16;
> - int dpin = pin;
> + int dpin = gpio % 16;
>
> if (gpio > 31) {
> pr_debug("WARNING: HIGH pin\n");
> - dpin = pin << 5;
> + dpin += 5;
> pin_dir_addr = pin_sel_addr;
> }
>
> @@ -140,7 +139,7 @@ static int rtl8231_pin_dir_get(struct rtl8231_gpios
> *gpios, u32
> gpio, u32 *dir)
>
> if (gpio > 31) {
> pin_dir_addr = RTL8231_GPIO_PIN_SEL(gpio);
> - pin = pin << 5;
> + pin += 5;
> }
>
> v = rtl8231_read(gpios, pin_dir_addr);
> @@ -240,6 +239,8 @@ void rtl8231_gpio_set(struct gpio_chip *gc, unsigned int
> offset, int
> value)
>
> int rtl8231_init(struct rtl8231_gpios *gpios)
> {
> + u32 v;
> +
> pr_info("%s called, MDIO bus ID: %d\n", __func__, gpios->smi_bus_id);
>
> gpios->reg_cached = 0;
> @@ -253,9 +254,11 @@ int rtl8231_init(struct rtl8231_gpios *gpios)
> sw_w32_mask(3, 1, RTL838X_DMY_REG5);
> }
>
> - /*Select GPIO functionality for pins 0-15, 16-31 and 32-37 */
> + /* Select GPIO functionality for pins 0-34 */
> rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(0), 0x);
> rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(16), 0x);
> + v = rtl8231_read(gpios, RTL8231_GPIO_PIN_SEL(32));
> + rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(32), v | 0x7);
>
> return 0;
> }
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] realtek: fix RTL8231 gpio expander for high GPIOs
Hi Sander, Thank you for review, it made me think about consistency. On Mon, Sep 20, 2021 at 05:45:06PM +0200, Sander Vanheule wrote: > On Fri, 2021-09-17 at 16:11 +0300, Paul Fertser wrote: > > rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(0), 0x); > > rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(16), 0x); > > + rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(32), 7 | (7 << 5)); > > Pins 35-36 cannot serve as LED output, but their GPIO direction can still be > changed. > Since the select bit for pins 35-36 should always read '1' (the GPIO pin > function), this > should probably be: > > rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(32), 0x1f | (0x1f << 5)); So we are not changing the direction for GPIOs 0-31 and it's probably a good thing since probably the bootloader has already configured them in some desired way. Guess the same idea should be applied to high GPIOs too, please see my v2. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2] realtek: fix RTL8231 gpio expander for high GPIOs
GPIOs > 31 require special handling. This patch fixes both the
initialisation and direction get/set operations.
Signed-off-by: Paul Fertser
---
Notes:
Changes from v1:
- Do not modify high GPIOs direction bits on init
.../realtek/files-5.4/drivers/gpio/gpio-rtl8231.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
b/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
index 031f60f5307c..a8ffcdc31368 100644
--- a/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
+++ b/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c
@@ -106,12 +106,11 @@ static int rtl8231_pin_dir(struct rtl8231_gpios *gpios,
u32 gpio, u32 dir)
u32 v;
int pin_sel_addr = RTL8231_GPIO_PIN_SEL(gpio);
int pin_dir_addr = RTL8231_GPIO_DIR(gpio);
- int pin = gpio % 16;
- int dpin = pin;
+ int dpin = gpio % 16;
if (gpio > 31) {
pr_debug("WARNING: HIGH pin\n");
- dpin = pin << 5;
+ dpin += 5;
pin_dir_addr = pin_sel_addr;
}
@@ -140,7 +139,7 @@ static int rtl8231_pin_dir_get(struct rtl8231_gpios *gpios,
u32 gpio, u32 *dir)
if (gpio > 31) {
pin_dir_addr = RTL8231_GPIO_PIN_SEL(gpio);
- pin = pin << 5;
+ pin += 5;
}
v = rtl8231_read(gpios, pin_dir_addr);
@@ -240,6 +239,8 @@ void rtl8231_gpio_set(struct gpio_chip *gc, unsigned int
offset, int value)
int rtl8231_init(struct rtl8231_gpios *gpios)
{
+ u32 v;
+
pr_info("%s called, MDIO bus ID: %d\n", __func__, gpios->smi_bus_id);
gpios->reg_cached = 0;
@@ -253,9 +254,11 @@ int rtl8231_init(struct rtl8231_gpios *gpios)
sw_w32_mask(3, 1, RTL838X_DMY_REG5);
}
- /*Select GPIO functionality for pins 0-15, 16-31 and 32-37 */
+ /* Select GPIO functionality for pins 0-34 */
rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(0), 0x);
rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(16), 0x);
+ v = rtl8231_read(gpios, RTL8231_GPIO_PIN_SEL(32));
+ rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(32), v | 0x7);
return 0;
}
--
2.17.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: WDS stopped working in 21.02, looking for bug in netifd
On 2021-09-20 16:46, Daniel Haid wrote:
> I have continued investigating.
>
> After all, it seems that the interface being down is just a symptom.
>
> I summarize my current findings:
>
> With the 21.02 netifd version, there seems to be a bug concerting WDS.
> The bug has the following effect:
>
> I have openwrt 21.02 running on one system running as WDS AP and another
> one running as WDS Client. The WDS Client is running and its
> configuration never changed.
>
> After booting the WDS AP, there are two possibilities for in what state
> the system can be, I call them NON-WORKING and WORKING. The probability
> seems to be about 50% to be in one or the other state after booting.
>
> To find out in which state I am after booting, I look for the interface
> wlan0.sta1. If it is UP, then we are in state WORKING. If it is DOWN,
> then we are in state NON-WORKING.
>
> Using ping, in state WORKING, the AP can reach the Client. In state
> NON-WORKING, the AP cannot reach the Client.
>
> In state WORKING, the interface wlan0.sta1 can be set to DOWN and UP
> again, and the AP can then again ping the Client, but only after waiting
> about 4 minutes for the Client to reconnect to the AP (in my last mail,
> I wrote that it did not work, but I just did not wait long enough).
>
> In state NON-WORKING, I can set the interface wlan0.sta1 to UP, but this
> will not help. The ip command will show that the interface is UP, but
> the AP can not ping the Client, no matter how long I wait after setting
> the state to UP.
>
> If I turn off the Client, wait for the interface wlan0.sta1 to be
> removed on the AP, and then restart the Client, then the interface
> wlan0.sta1 will be created again, in state DOWN. Everything is again as
> in the state NON-WORKING.
>
> To reliably reach the state NON-WORKING, run "/etc/init.d/network restart".
>
> Changing the function wireless_interface_handle_link such that it does
> not call interface_handle_link when it is called from
> wireless_device_hotplug_event fixes the bug.
>
> But I do not understand what is happening.
>
> I am not subscribed to the list; please send Cc to me.
Please test if applying this change to netifd fixes the issue.
Thanks,
- Felix
---
--- a/wireless.c
+++ b/wireless.c
@@ -328,14 +328,14 @@ static void wireless_interface_handle_link(struct
wireless_interface *vif, const
if (!ifname)
ifname = vif->ifname;
- if (up) {
+ if (up && ifname != vif->ifname) {
struct device *dev = device_get(ifname, 2);
if (dev) {
dev->wireless_isolate = vif->isolate;
dev->wireless_proxyarp = vif->proxyarp;
dev->wireless = true;
dev->wireless_ap = vif->ap_mode;
- dev->bpdu_filter = dev->wireless_ap && ifname ==
vif->ifname;
+ dev->bpdu_filter = dev->wireless_ap;
}
}
@@ -793,6 +793,13 @@ wireless_interface_init_config(struct wireless_interface
*vif)
if ((cur = tb[VIF_ATTR_NETWORK]))
vif->network = cur;
+ cur = tb[VIF_ATTR_MODE];
+ if (cur)
+ vif->ap_mode = !strcmp(blobmsg_get_string(cur), "ap");
+
+ if (!vif->ap_mode)
+ return;
+
cur = tb[VIF_ATTR_ISOLATE];
if (cur)
vif->isolate = blobmsg_get_bool(cur);
@@ -801,9 +808,6 @@ wireless_interface_init_config(struct wireless_interface
*vif)
if (cur)
vif->proxyarp = blobmsg_get_bool(cur);
- cur = tb[VIF_ATTR_MODE];
- if (cur)
- vif->ap_mode = !strcmp(blobmsg_get_string(cur), "ap");
}
/* vlist update call for wireless interface list */
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [patch] elfutils: enable host build
On 31.08.2021 10:04, Lucian Cristian wrote: frr 8.0 needs host libelf dev add option for host build tested on x86, ramips, kirkwood Signed-off-by: Lucian Cristian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel Bump for this basic patch Regards, Lucian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] realtek: fix RTL8231 gpio expander for high GPIOs
Hi Paul, Thanks for the patch. One comment below. On Fri, 2021-09-17 at 16:11 +0300, Paul Fertser wrote: > GPIOs > 31 require special handling. This patch fixes both the > initialisation (defaulting to input) and direction get/set operations. > > Runtime-tested on D-Link DGS-1210-10P-R1 which has "reset" button on > GPIO[33]. > > Signed-off-by: Paul Fertser > --- > .../realtek/files-5.4/drivers/gpio/gpio-rtl8231.c | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c > b/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c > index 031f60f5307c..ddb8894663ec 100644 > --- a/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c > +++ b/target/linux/realtek/files-5.4/drivers/gpio/gpio-rtl8231.c > @@ -253,9 +252,10 @@ int rtl8231_init(struct rtl8231_gpios *gpios) > sw_w32_mask(3, 1, RTL838X_DMY_REG5); > } > > - /*Select GPIO functionality for pins 0-15, 16-31 and 32-37 */ > + /*Select GPIO functionality for pins 0-15, 16-31 and 32-34 */ > rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(0), 0x); > rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(16), 0x); > + rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(32), 7 | (7 << 5)); > Pins 35-36 cannot serve as LED output, but their GPIO direction can still be changed. Since the select bit for pins 35-36 should always read '1' (the GPIO pin function), this should probably be: rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(32), 0x1f | (0x1f << 5)); Best, Sander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: WDS stopped working in 21.02, looking for bug in netifd
I have continued investigating. After all, it seems that the interface being down is just a symptom. I summarize my current findings: With the 21.02 netifd version, there seems to be a bug concerting WDS. The bug has the following effect: I have openwrt 21.02 running on one system running as WDS AP and another one running as WDS Client. The WDS Client is running and its configuration never changed. After booting the WDS AP, there are two possibilities for in what state the system can be, I call them NON-WORKING and WORKING. The probability seems to be about 50% to be in one or the other state after booting. To find out in which state I am after booting, I look for the interface wlan0.sta1. If it is UP, then we are in state WORKING. If it is DOWN, then we are in state NON-WORKING. Using ping, in state WORKING, the AP can reach the Client. In state NON-WORKING, the AP cannot reach the Client. In state WORKING, the interface wlan0.sta1 can be set to DOWN and UP again, and the AP can then again ping the Client, but only after waiting about 4 minutes for the Client to reconnect to the AP (in my last mail, I wrote that it did not work, but I just did not wait long enough). In state NON-WORKING, I can set the interface wlan0.sta1 to UP, but this will not help. The ip command will show that the interface is UP, but the AP can not ping the Client, no matter how long I wait after setting the state to UP. If I turn off the Client, wait for the interface wlan0.sta1 to be removed on the AP, and then restart the Client, then the interface wlan0.sta1 will be created again, in state DOWN. Everything is again as in the state NON-WORKING. To reliably reach the state NON-WORKING, run "/etc/init.d/network restart". Changing the function wireless_interface_handle_link such that it does not call interface_handle_link when it is called from wireless_device_hotplug_event fixes the bug. But I do not understand what is happening. I am not subscribed to the list; please send Cc to me. D.H. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: WDS stopped working in 21.02, looking for bug in netifd
I have investigated a bit more. Even without the "fix", after each reboot WDS there seems to be about a 50% chance of WDS working. To reliably reproduce the bug, it is necessary to do /etc/init.d/network restart with the WDS client connected. Now what I noticed is that using the netifd version with the bug, after the network restart the interface wlan0.sta1 is DOWN (and the WDS client not reachable) while using the version with the "fix" the interface wlan0.sta1 is UP (and the WDS client is reachable). However, in the version with the bug, if I manually set the interface to UP with "ip link set up dev wlan0.sta1", it now says that the interface is UP, but the WDS client is still not reachable. On the other hand, if use a version with the "fix", then initally the WDS client is reachable. But if I now issue ip link set down dev wlan0.sta1 ip link set up dev wlan0.sta1 then the WDS client is not reachable anymore! Who creates these interfaces "wlan0.sta1"? Maybe we are not allowed to set them to DOWN after they have been created. Or after setting them to UP there is some further initalization required which netifd does not do, but the original process that creates these interfaces does? I will investigate further. I am also grateful for any suggestions. I am not subscribed to the list; please send Cc to me. D.H. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH v4 0/6] at91: add support for sama5d2 icp, sama5d27 wlsom1 ek and sam9x60ek
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On 20.09.2021 12:27, Claudiu Beznea wrote: > Hi, > > This series adds support for SAMA5D2 ICP, SAMA5D27-WLSOM1-EK and > SAM9X60EK boards. > > Since SAM9X60's kernel support is included in 5.10 but not on 5.4 > 1st (patch 1/6) switches to kernel 5.10. > > Patches 2/6, 5/6 updates the kernel config for sam9x SoCs and sam9x60. > > Patch 3/6, 4/6, 6/6 adds the boards support. > > Thank you, > Claudiu Beznea Forgot to mention: Changes in v4: - avoid selecting kernel features as modules Changes in v3: - squash patches "at91: use make kernel_menuconfig and save for sam9x kernel config" and "at91: enable CONFIG_ARCH_AT91 and specific sam9x SoCs" from v2 into "at91: kernel: bump to 5.10" - keep only SoC specific and boot specific flags in pach "at91: enable specific sam9x kernel config flags" Changes in v2: - changed series title from "at91: add support for sama5d2 icp and" to "at91: add support for sama5d2 icp, sama5d27 wlsom1 ek and sam9x60ek" - bump at91 to kernel 5.10 - adds sam9x60 and sam9x60ek specific support - drop patch 1/3 from v1 > > Claudiu Beznea (6): > at91: kernel: bump to 5.10 > at91: enable specific sam9x kernel config flags > at91: add support for sama5d2 icp board > at91: add support for sama5d27-wlsom1-ek board > at91: enable kernel config for sam9x60 > at91: add support for sam9x60-ek board > > package/boot/at91bootstrap/Makefile | 42 +++ > package/boot/uboot-at91/Makefile | 35 +++ > target/linux/at91/Makefile| 2 +- > .../at91/files/arch/arm/boot/dts/wb45n.dts| 220 -- > .../at91/files/arch/arm/boot/dts/wb50n.dts| 113 --- > .../at91/files/arch/arm/boot/dts/wb50n.dtsi | 205 - > target/linux/at91/image/sam9x.mk | 14 +- > target/linux/at91/image/sama5.mk | 23 ++ > .../101-ARM-at91-build-dtb-for-q5xr5.patch| 10 + > .../101-ARM-at91-build-dtb-for-q5xr5.patch| 10 - > .../102-ARM-at91-build-dtb-for-wb45n.patch| 12 - > ...2-ARM-at91-wb45n-fix-duplicate-label.patch | 20 -- > .../103-ARM-at91-build-dtb-for-wb50n.patch| 12 - > ...3-ARM-at91-wb50n-fix-duplicate-label.patch | 39 --- > target/linux/at91/sam9x/config-default| 286 ++ > 15 files changed, 345 insertions(+), 698 deletions(-) > delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb45n.dts > delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dts > delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dtsi > create mode 04 target/linux/at91/patches-5.10 > create mode 100644 > target/linux/at91/patches-5.10/101-ARM-at91-build-dtb-for-q5xr5.patch > delete mode 04 target/linux/at91/patches-5.4 > delete mode 100644 > target/linux/at91/patches-5.4/101-ARM-at91-build-dtb-for-q5xr5.patch > delete mode 100644 > target/linux/at91/patches-5.4/102-ARM-at91-build-dtb-for-wb45n.patch > delete mode 100644 > target/linux/at91/patches-5.4/102-ARM-at91-wb45n-fix-duplicate-label.patch > delete mode 100644 > target/linux/at91/patches-5.4/103-ARM-at91-build-dtb-for-wb50n.patch > delete mode 100644 > target/linux/at91/patches-5.4/103-ARM-at91-wb50n-fix-duplicate-label.patch > --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v4 5/6] at91: enable kernel config for sam9x60
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Enable kernel config for SAM9X60. Signed-off-by: Claudiu Beznea --- target/linux/at91/sam9x/config-default | 29 -- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/target/linux/at91/sam9x/config-default b/target/linux/at91/sam9x/config-default index a9f66766b1f2..aa29527d3467 100644 --- a/target/linux/at91/sam9x/config-default +++ b/target/linux/at91/sam9x/config-default @@ -15,6 +15,7 @@ CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARM=y +CONFIG_ARM_CPU_SUSPEND=y CONFIG_ARM_HAS_SG_CHAIN=y CONFIG_ARM_L1_CACHE_SHIFT=5 CONFIG_ARM_PATCH_PHYS_VIRT=y @@ -22,6 +23,8 @@ CONFIG_ARM_THUMB=y CONFIG_ARM_UNWIND=y # CONFIG_AT91RM9200_WATCHDOG is not set CONFIG_AT91SAM9X_WATCHDOG=y +# CONFIG_AT91_ADC is not set +CONFIG_AT91_SAMA5D2_ADC=y CONFIG_AT91_SOC_ID=y # CONFIG_AT91_SOC_SFR is not set CONFIG_ATMEL_AIC5_IRQ=y @@ -30,16 +33,19 @@ CONFIG_ATMEL_CLOCKSOURCE_PIT=y CONFIG_ATMEL_CLOCKSOURCE_TCB=y CONFIG_ATMEL_EBI=y CONFIG_ATMEL_PIT=y +CONFIG_ATMEL_PM=y CONFIG_ATMEL_SDRAMC=y CONFIG_ATMEL_SSC=y CONFIG_ATMEL_ST=y CONFIG_ATMEL_TCB_CLKSRC=y CONFIG_ATMEL_TCLIB=y CONFIG_AT_HDMAC=y -# CONFIG_AT_XDMAC is not set +CONFIG_AT_XDMAC=y CONFIG_AUTO_ZRELADDR=y CONFIG_BINFMT_FLAT_ARGVP_ENVP_ON_STACK=y +CONFIG_BLK_PM=y CONFIG_CLKDEV_LOOKUP=y +CONFIG_CLKSRC_MMIO=y CONFIG_CLONE_BACKWARDS=y CONFIG_COMMON_CLK=y CONFIG_COMMON_CLK_AT91=y @@ -60,6 +66,7 @@ CONFIG_CPU_CP15_MMU=y # CONFIG_CPU_DCACHE_WRITETHROUGH is not set CONFIG_CPU_NO_EFFICIENT_FFS=y CONFIG_CPU_PABRT_LEGACY=y +CONFIG_CPU_PM=y CONFIG_CPU_THUMB_CAPABLE=y CONFIG_CPU_TLB_V4WBI=y CONFIG_CPU_USE_DOMAINS=y @@ -89,8 +96,10 @@ CONFIG_EEPROM_AT24=y CONFIG_EXT4_FS=y CONFIG_FIXED_PHY=y CONFIG_FIX_EARLYCON_MEM=y +CONFIG_FREEZER=y CONFIG_FS_IOMAP=y CONFIG_FS_MBCACHE=y +CONFIG_FW_CACHE=y CONFIG_FW_LOADER_PAGED_BUF=y CONFIG_GENERIC_ALLOCATOR=y CONFIG_GENERIC_ATOMIC64=y @@ -132,6 +141,11 @@ CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=y CONFIG_I2C_COMPAT=y CONFIG_I2C_GPIO=y +CONFIG_IIO=y +CONFIG_IIO_BUFFER=y +CONFIG_IIO_KFIFO_BUF=y +CONFIG_IIO_TRIGGER=y +CONFIG_IIO_TRIGGERED_BUFFER=y CONFIG_INITRAMFS_SOURCE="" CONFIG_INPUT=y CONFIG_INPUT_KEYBOARD=y @@ -156,11 +170,13 @@ CONFIG_MDIO_DEVRES=y CONFIG_MEMFD_CREATE=y CONFIG_MEMORY=y CONFIG_MFD_AT91_USART=y +CONFIG_MFD_ATMEL_FLEXCOM=y CONFIG_MFD_ATMEL_HLCDC=y CONFIG_MFD_ATMEL_SMC=y CONFIG_MFD_CORE=y CONFIG_MFD_SYSCON=y CONFIG_MICREL_PHY=y +CONFIG_MICROCHIP_PIT64B=y CONFIG_MIGRATION=y CONFIG_MMC=y CONFIG_MMC_ATMELMCI=y @@ -205,6 +221,12 @@ CONFIG_PHYLINK=y CONFIG_PINCTRL=y CONFIG_PINCTRL_AT91=y # CONFIG_PINCTRL_AT91PIO4 is not set +CONFIG_PINCTRL_MCP23S08=y +CONFIG_PINCTRL_MCP23S08_I2C=y +CONFIG_PINCTRL_MCP23S08_SPI=y +CONFIG_PM=y +CONFIG_PM_CLK=y +CONFIG_PM_SLEEP=y CONFIG_POWER_RESET=y CONFIG_POWER_RESET_AT91_POWEROFF=y CONFIG_POWER_RESET_AT91_RESET=y @@ -220,6 +242,7 @@ CONFIG_RATIONAL=y CONFIG_REGMAP=y CONFIG_REGMAP_I2C=y CONFIG_REGMAP_MMIO=y +CONFIG_REGMAP_SPI=y CONFIG_REGULATOR=y CONFIG_REGULATOR_FIXED_VOLTAGE=y CONFIG_RTC_CLASS=y @@ -227,7 +250,7 @@ CONFIG_RTC_DRV_AT91RM9200=y CONFIG_RTC_DRV_AT91SAM9=y CONFIG_RTC_I2C_AND_SPI=y CONFIG_RTC_MC146818_LIB=y -# CONFIG_SAMA5D4_WATCHDOG is not set +CONFIG_SAMA5D4_WATCHDOG=y # CONFIG_SERIAL_8250 is not set CONFIG_SERIAL_ATMEL=y CONFIG_SERIAL_ATMEL_CONSOLE=y @@ -256,6 +279,8 @@ CONFIG_SPLIT_PTLOCK_CPUS=99 CONFIG_SRAM=y CONFIG_SRAM_EXEC=y CONFIG_SRCU=y +CONFIG_SUSPEND=y +CONFIG_SUSPEND_FREEZER=y CONFIG_SWPHY=y CONFIG_SYS_SUPPORTS_APM_EMULATION=y CONFIG_TICK_CPU_ACCOUNTING=y -- 2.23.0 --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v4 6/6] at91: add support for sam9x60-ek board
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Add support for SAM9X60-EK board. Hardware: - SoC: SAM9X60 - RAM: Winbond W972GG6KB-25 (2Gbit DDR2) - NAND Flash: Micron MT29F4G08ABAEA - QSPI Flash: Microchip SST26VF064B - EEPROM: Microchip 24AA02E48 - SDMMC: One standard 4-bit SD card interface - USB: two stacked Type-A connectors with power switches, one micro-B USB device - CAN: 2 interfaces (Microchip MCP2542) - Ethernet: one 10/100Mbps - WiFi/BT: one optional WiFi/Bluetooth interface - Audio: one ClassD port - Display: one 24-bit LCD interface - Camera: one 12-bit image sensor interface - IO: one IO expander (Microchip MCP23008) - Debug ports: one J-Link-OB + CDC, one JTAG interface - Leds: one RGB LED - Buttons: 4 push button switches - Expansion: one PIO connector, one mikrobus connector - Power management: two power regulators, two power consumption measurement devices Flashing: - follow the procedure at [1] [1] https://www.linux4sam.org/bin/view/Linux4SAM/Sam9x60EKMainPage#Create_a_SD_card_with_the_demo Signed-off-by: Claudiu Beznea --- package/boot/at91bootstrap/Makefile | 14 ++ package/boot/uboot-at91/Makefile| 14 ++ target/linux/at91/image/sam9x.mk| 13 +++-- 3 files changed, 39 insertions(+), 2 deletions(-) diff --git a/package/boot/at91bootstrap/Makefile b/package/boot/at91bootstrap/Makefile index 8711acd286bd..2d77f7099721 100644 --- a/package/boot/at91bootstrap/Makefile +++ b/package/boot/at91bootstrap/Makefile @@ -40,6 +40,18 @@ define AT91Bootstrap/at91sam9x5eksd_uboot BUILD_DEVICES:=atmel_at91sam9x25ek atmel_at91sam9x35ek endef +define AT91Bootstrap/sam9x60eknf_uboot + NAME:=AT91Bootstrap for SAM9X60-EK board (NandFlash) + BUILD_SUBTARGET:=sam9x + BUILD_DEVICES:=microchip_sam9x60ek +endef + +define AT91Bootstrap/sam9x60eksd_uboot + NAME:=AT91Bootstrap for SAM9X60-EK board (SDcard) + BUILD_SUBTARGET:=sam9x + BUILD_DEVICES:=microchip_sam9x60ek +endef + define AT91Bootstrap/sama5d2_icpdf_qspi_uboot TITLE:=AT91Bootstrap for SAMA5D2 ICP board (QSPI Flash) BUILD_SUBTARGET:=sama5 @@ -145,6 +157,8 @@ endef AT91BOOTSTRAP_TARGETS := \ at91sam9x5eknf_uboot \ at91sam9x5eksd_uboot \ + sam9x60eknf_uboot \ + sam9x60eksd_uboot \ sama5d2_icpdf_qspi_uboot \ sama5d2_icpsd_uboot \ sama5d2_xplaineddf_uboot \ diff --git a/package/boot/uboot-at91/Makefile b/package/boot/uboot-at91/Makefile index 5aade7de9cf9..ed929794bdb1 100644 --- a/package/boot/uboot-at91/Makefile +++ b/package/boot/uboot-at91/Makefile @@ -47,6 +47,18 @@ define U-Boot/at91sam9x5ek_mmc atmel_at91sam9x35ek endef +define U-Boot/sam9x60ek_nandflash + NAME:=SAM9X60-EK board (NandFlash) + BUILD_SUBTARGET:=sam9x + BUILD_DEVICES:=microchip_sam9x60ek +endef + +define U-Boot/sam9x60ek_mmc + NAME:=SAM9X60-EK board (SDcard) + BUILD_SUBTARGET:=sam9x + BUILD_DEVICES:=microchip_sam9x60ek +endef + define U-Boot/sama5d3_xplained_nandflash NAME:=SAMA5D3 Xplained board (NandFlash) BUILD_SUBTARGET:=sama5 @@ -135,6 +147,8 @@ UBOOT_TARGETS := \ at91sam9m10g45ek_nandflash \ at91sam9x5ek_nandflash \ at91sam9x5ek_mmc \ + sam9x60ek_nandflash \ + sam9x60ek_mmc \ sama5d3_xplained_nandflash \ sama5d3_xplained_mmc \ sama5d2_icp_mmc \ diff --git a/target/linux/at91/image/sam9x.mk b/target/linux/at91/image/sam9x.mk index 6f10123bbaae..b6c5e33ac44f 100644 --- a/target/linux/at91/image/sam9x.mk +++ b/target/linux/at91/image/sam9x.mk @@ -16,11 +16,11 @@ define Build/at91-sdcard ::$(DEVICE_NAME)-fit.itb mcopy -i $@.boot \ - $(BIN_DIR)/u-boot-at91sam9x5ek_mmc/u-boot.bin \ + $(BIN_DIR)/u-boot-$(if $(findstring sam9x60,$@),$(DEVICE_DTS:at91-%=%),at91sam9x5ek)_mmc/u-boot.bin \ ::u-boot.bin mcopy -i $@.boot \ - $(BIN_DIR)/at91bootstrap-at91sam9x5eksd_uboot/at91bootstrap.bin \ + $(BIN_DIR)/at91bootstrap-$(if $(findstring sam9x60,$@),$(DEVICE_DTS:at91-%=%),at91sam9x5ek)sd_uboot/at91bootstrap.bin \ ::BOOT.bin $(CP) uboot-env.txt $@-uboot-env.txt @@ -112,6 +112,15 @@ define Device/atmel_at91sam9x35ek endef TARGET_DEVICES += atmel_at91sam9x35ek +define Device/microchip_sam9x60ek + $(Device/evaluation-dtb) + DEVICE_VENDOR := Microchip + DEVICE_MODEL := SAM9X60-EK + DEVICE_DTS := at91-sam9x60ek + $(Device/evaluation-sdimage) +endef +TARGET_DEVICES += microchip_sam9x60ek + define Device/calamp_lmu5000 $(Device/production) DEVICE_VENDOR := CalAmp -- 2.23.0 --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v4 1/6] at91: kernel: bump to 5.10
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Bump at91 targets to kernel v5.10. With this patches and files for
wb45n and wb50n were removed as they are now included in upstream
kernel. Along with:
- this the kernel config for sam9x targets has been refreshed (with
make kernel_menuconfig + save);
- CONFIG_ARCH_AT91 and specific sam9x SoCs (AT91RM9200, AT91SAM9,
SAM9X60) has been enabled such that sam9x SoCs to be able to boot.
Signed-off-by: Claudiu Beznea
---
target/linux/at91/Makefile| 2 +-
.../at91/files/arch/arm/boot/dts/wb45n.dts| 220 --
.../at91/files/arch/arm/boot/dts/wb50n.dts| 113 -
.../at91/files/arch/arm/boot/dts/wb50n.dtsi | 205
target/linux/at91/image/sam9x.mk | 1 +
target/linux/at91/image/sama5.mk | 1 +
.../101-ARM-at91-build-dtb-for-q5xr5.patch| 10 +
.../101-ARM-at91-build-dtb-for-q5xr5.patch| 10 -
.../102-ARM-at91-build-dtb-for-wb45n.patch| 12 -
...2-ARM-at91-wb45n-fix-duplicate-label.patch | 20 --
.../103-ARM-at91-build-dtb-for-wb50n.patch| 12 -
...3-ARM-at91-wb50n-fix-duplicate-label.patch | 39
target/linux/at91/sam9x/config-default| 105 -
13 files changed, 57 insertions(+), 693 deletions(-)
delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb45n.dts
delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dts
delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dtsi
create mode 04 target/linux/at91/patches-5.10
create mode 100644
target/linux/at91/patches-5.10/101-ARM-at91-build-dtb-for-q5xr5.patch
delete mode 04 target/linux/at91/patches-5.4
delete mode 100644
target/linux/at91/patches-5.4/101-ARM-at91-build-dtb-for-q5xr5.patch
delete mode 100644
target/linux/at91/patches-5.4/102-ARM-at91-build-dtb-for-wb45n.patch
delete mode 100644
target/linux/at91/patches-5.4/102-ARM-at91-wb45n-fix-duplicate-label.patch
delete mode 100644
target/linux/at91/patches-5.4/103-ARM-at91-build-dtb-for-wb50n.patch
delete mode 100644
target/linux/at91/patches-5.4/103-ARM-at91-wb50n-fix-duplicate-label.patch
diff --git a/target/linux/at91/Makefile b/target/linux/at91/Makefile
index fe6a93244a5f..e4da7fb7e7da 100644
--- a/target/linux/at91/Makefile
+++ b/target/linux/at91/Makefile
@@ -10,7 +10,7 @@ BOARDNAME:=Microchip (Atmel AT91)
FEATURES:=ext4 squashfs targz usb usbgadget ubifs
SUBTARGETS:=sama5 sam9x
-KERNEL_PATCHVER:=5.4
+KERNEL_PATCHVER:=5.10
include $(INCLUDE_DIR)/target.mk
diff --git a/target/linux/at91/files/arch/arm/boot/dts/wb45n.dts
b/target/linux/at91/files/arch/arm/boot/dts/wb45n.dts
deleted file mode 100644
index fd9d260f2ab5..
--- a/target/linux/at91/files/arch/arm/boot/dts/wb45n.dts
+++ /dev/null
@@ -1,220 +0,0 @@
-// SPDX-License-Identifier: GPL-2.0-or-later
-/*
- * wb45n.dts - Device Tree file for WB45NBT board
- *
- * Copyright (C) 2015 Laird
- */
-
-/dts-v1/;
-#include "at91sam9g25.dtsi"
-
-/ {
- model = "Laird Workgroup Bridge 45N - Atmel AT91SAM (dt)";
- compatible = "laird,wb45n", "laird,wbxx", "atmel,at91sam9x5",
"atmel,at91sam9";
-
- chosen {
- bootargs = "console=ttyS0,115200 root=/dev/mtdblock1 rw
rootfstype=ubifs ubi.mtd=1 root=ubi0:rootfs";
- };
-
- memory {
- reg = <0x2000 0x400>;
- };
-
- clocks {
- #address-cells = <1>;
- #size-cells = <1>;
- ranges;
-
- main_clock: clock@0 {
- compatible = "atmel,osc", "fixed-clock";
- clock-frequency = <1200>;
- };
-
- slow_xtal {
- clock-frequency = <32768>;
- };
-
- main_xtal {
- clock-frequency = <1200>;
- };
- };
-
- ahb {
- apb {
-
- rstc@fe00 {
- compatible = "atmel,sama5d3-rstc";
- };
-
- pinctrl@f400 {
- nand {
- pinctrl_nand: nand-0 {
- atmel,pins =
- ; /* PD5 gpio RDY/BUSY pin pull_up */
- };
- };
-
- usb2 {
- pinctrl_board_usb2: usb2-board {
- atmel,pins =
- ; /* PB11 gpio vbus sense,
deglitch */
- };
-
[PATCH v4 2/6] at91: enable specific sam9x kernel config flags
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Enable specific sam9x kernel config flags. Signed-off-by: Claudiu Beznea --- target/linux/at91/sam9x/config-default | 168 +++-- 1 file changed, 159 insertions(+), 9 deletions(-) diff --git a/target/linux/at91/sam9x/config-default b/target/linux/at91/sam9x/config-default index d8b5c31dc7e5..a9f66766b1f2 100644 --- a/target/linux/at91/sam9x/config-default +++ b/target/linux/at91/sam9x/config-default @@ -1,7 +1,6 @@ CONFIG_ALIGNMENT_TRAP=y CONFIG_ARCH_32BIT_OFF_T=y CONFIG_ARCH_AT91=y -CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_KEEP_MEMBLOCK=y CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y @@ -12,6 +11,8 @@ CONFIG_ARCH_MULTI_V4_V5=y CONFIG_ARCH_MULTI_V5=y CONFIG_ARCH_NR_GPIO=0 CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y +CONFIG_ARCH_SELECT_MEMORY_MODEL=y +CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARM=y CONFIG_ARM_HAS_SG_CHAIN=y @@ -20,8 +21,9 @@ CONFIG_ARM_PATCH_PHYS_VIRT=y CONFIG_ARM_THUMB=y CONFIG_ARM_UNWIND=y # CONFIG_AT91RM9200_WATCHDOG is not set -# CONFIG_AT91SAM9X_WATCHDOG is not set +CONFIG_AT91SAM9X_WATCHDOG=y CONFIG_AT91_SOC_ID=y +# CONFIG_AT91_SOC_SFR is not set CONFIG_ATMEL_AIC5_IRQ=y CONFIG_ATMEL_AIC_IRQ=y CONFIG_ATMEL_CLOCKSOURCE_PIT=y @@ -29,9 +31,12 @@ CONFIG_ATMEL_CLOCKSOURCE_TCB=y CONFIG_ATMEL_EBI=y CONFIG_ATMEL_PIT=y CONFIG_ATMEL_SDRAMC=y +CONFIG_ATMEL_SSC=y CONFIG_ATMEL_ST=y CONFIG_ATMEL_TCB_CLKSRC=y -# CONFIG_ATMEL_TCLIB is not set +CONFIG_ATMEL_TCLIB=y +CONFIG_AT_HDMAC=y +# CONFIG_AT_XDMAC is not set CONFIG_AUTO_ZRELADDR=y CONFIG_BINFMT_FLAT_ARGVP_ENVP_ON_STACK=y CONFIG_CLKDEV_LOOKUP=y @@ -39,6 +44,7 @@ CONFIG_CLONE_BACKWARDS=y CONFIG_COMMON_CLK=y CONFIG_COMMON_CLK_AT91=y CONFIG_COMPAT_32BIT_TIME=y +CONFIG_CONFIGFS_FS=y CONFIG_CPU_32v4T=y CONFIG_CPU_32v5=y CONFIG_CPU_ABRT_EV4T=y @@ -57,17 +63,34 @@ CONFIG_CPU_PABRT_LEGACY=y CONFIG_CPU_THUMB_CAPABLE=y CONFIG_CPU_TLB_V4WBI=y CONFIG_CPU_USE_DOMAINS=y +CONFIG_CRC16=y CONFIG_CRC7=y CONFIG_CRC_CCITT=y CONFIG_CRC_ITU_T=y +CONFIG_CRYPTO_CRC32C=y +CONFIG_CRYPTO_DEFLATE=y +CONFIG_CRYPTO_GF128MUL=y +CONFIG_CRYPTO_HASH_INFO=y +CONFIG_CRYPTO_LZO=y +CONFIG_CRYPTO_NULL2=y CONFIG_CRYPTO_RNG2=y +CONFIG_CRYPTO_ZSTD=y CONFIG_DEBUG_INFO=y CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S" +CONFIG_DMADEVICES=y +CONFIG_DMA_ENGINE=y +CONFIG_DMA_OF=y +CONFIG_DMA_OPS=y CONFIG_DMA_REMAP=y CONFIG_DTC=y CONFIG_EDAC_ATOMIC_SCRUB=y CONFIG_EDAC_SUPPORT=y +CONFIG_EEPROM_AT24=y +CONFIG_EXT4_FS=y +CONFIG_FIXED_PHY=y CONFIG_FIX_EARLYCON_MEM=y +CONFIG_FS_IOMAP=y +CONFIG_FS_MBCACHE=y CONFIG_FW_LOADER_PAGED_BUF=y CONFIG_GENERIC_ALLOCATOR=y CONFIG_GENERIC_ATOMIC64=y @@ -96,33 +119,73 @@ CONFIG_HARDIRQS_SW_RESEND=y CONFIG_HAS_DMA=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT_MAP=y +CONFIG_HW_RANDOM=y +CONFIG_HW_RANDOM_ATMEL=y CONFIG_HZ=128 CONFIG_HZ_FIXED=128 CONFIG_HZ_PERIODIC=y +CONFIG_I2C=y +CONFIG_I2C_ALGOBIT=y +CONFIG_I2C_AT91=y +# CONFIG_I2C_AT91_SLAVE_EXPERIMENTAL is not set +CONFIG_I2C_BOARDINFO=y +CONFIG_I2C_CHARDEV=y +CONFIG_I2C_COMPAT=y +CONFIG_I2C_GPIO=y CONFIG_INITRAMFS_SOURCE="" +CONFIG_INPUT=y +CONFIG_INPUT_KEYBOARD=y CONFIG_IRQCHIP=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_IRQ_WORK=y +CONFIG_JBD2=y +CONFIG_LEDS_GPIO=y +CONFIG_LEDS_PWM=y +CONFIG_LEDS_TRIGGER_CPU=y +CONFIG_LEDS_TRIGGER_GPIO=y CONFIG_LIBFDT=y +CONFIG_LLD_VERSION=0 CONFIG_LOCK_DEBUGGING_SUPPORT=y +CONFIG_LZO_COMPRESS=y +CONFIG_LZO_DECOMPRESS=y +CONFIG_MACB=y +CONFIG_MDIO_BUS=y +CONFIG_MDIO_DEVICE=y +CONFIG_MDIO_DEVRES=y CONFIG_MEMFD_CREATE=y CONFIG_MEMORY=y -# CONFIG_MFD_AT91_USART is not set +CONFIG_MFD_AT91_USART=y +CONFIG_MFD_ATMEL_HLCDC=y CONFIG_MFD_ATMEL_SMC=y +CONFIG_MFD_CORE=y CONFIG_MFD_SYSCON=y -# CONFIG_MICROCHIP_PIT64B is not set +CONFIG_MICREL_PHY=y CONFIG_MIGRATION=y CONFIG_MMC=y -# CONFIG_MMC_ATMELMCI is not set +CONFIG_MMC_ATMELMCI=y CONFIG_MMC_BLOCK=y CONFIG_MMC_SDHCI=y CONFIG_MMC_SDHCI_OF_AT91=y CONFIG_MMC_SDHCI_PLTFM=y CONFIG_MODULES_USE_ELF_REL=y +CONFIG_MTD_CMDLINE_PARTS=y +CONFIG_MTD_DATAFLASH=y +# CONFIG_MTD_DATAFLASH_OTP is not set +# CONFIG_MTD_DATAFLASH_WRITE_VERIFY is not set +CONFIG_MTD_SPI_NOR=y +CONFIG_MTD_UBI=y +CONFIG_MTD_UBI_BEB_LIMIT=20 +# CONFIG_MTD_UBI_BLOCK is not set +CONFIG_MTD_UBI_FASTMAP=y +CONFIG_MTD_UBI_GLUEBI=y +CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_KUSER_HELPERS=y CONFIG_NEED_PER_CPU_KM=y +CONFIG_NLS=y +CONFIG_NVMEM=y +CONFIG_NVMEM_SYSFS=y CONFIG_OF=y CONFIG_OF_ADDRESS=y CONFIG_OF_EARLY_FLATTREE=y @@ -130,40 +193,127 @@ CONFIG_OF_FLATTREE=y CONFIG_OF_GPIO=y CONFIG_OF_IRQ=y CONFIG_OF_KOBJ=y +CONFIG_OF_MDIO=y CONFIG_OF_NET=y CONFIG_OLD_SIGACTION=y CONFIG_OLD_SIGSUSPEND3=y CONFIG_PAGE_OFFSET=0xC000 CONFIG
[PATCH v4 3/6] at91: add support for sama5d2 icp board
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Add support for SAMA5D2 ICP board. Hardware: - SoC: SAMA5D27 - RAM: 512 MB DDR3L - MMC: One stanard SD card interface - USB: One USB host switch 4 ports with power switch, One USB device type Micro-AB - CAN: 2 interfaces - Ethernet: One Gigabit Ethernet PHY through HSIC, One ETH switchport, One EtherCAT interface - WiFi/BT: Footprint for IEEE 802.11 b/g/n Wi-Fi plus Bluetooth module (Wi-Fi/BT), suitable for Microchip WILC3000-MR110CA or WILC3000-MR110UA - Debug port: One J-Link-OB/J-Link-CDC, one JTAG interface - Leds: one RGB LED - Buttons: reset, wakeup, 2 user buttons - Expansion: one PIOBU/PIO connector, 3 mikrobus sockets - Power mangament: PMIC (MCP16502), one power consumption device (PAC1934) Not working in Linux: - EtherCAT interface: there is no Linux support integrated - PAC1934: driver available at [1] but not integrated in Linux Flashing: - follow the procedure at [2] [1] https://ww1.microchip.com/downloads/en/DeviceDoc/pac193x_linux_driver.zip [2] https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d2IcpMainPage#Create_a_SD_card_with_the_demo Signed-off-by: Claudiu Beznea --- package/boot/at91bootstrap/Makefile | 14 ++ package/boot/uboot-at91/Makefile| 7 +++ target/linux/at91/image/sama5.mk| 11 +++ 3 files changed, 32 insertions(+) diff --git a/package/boot/at91bootstrap/Makefile b/package/boot/at91bootstrap/Makefile index f66472fa9c29..56e14c57703c 100644 --- a/package/boot/at91bootstrap/Makefile +++ b/package/boot/at91bootstrap/Makefile @@ -40,6 +40,18 @@ define AT91Bootstrap/at91sam9x5eksd_uboot BUILD_DEVICES:=atmel_at91sam9x25ek atmel_at91sam9x35ek endef +define AT91Bootstrap/sama5d2_icpdf_qspi_uboot + TITLE:=AT91Bootstrap for SAMA5D2 ICP board (QSPI Flash) + BUILD_SUBTARGET:=sama5 + BUILD_DEVICES:=microchip_sama5d2-icp +endef + +define AT91Bootstrap/sama5d2_icpsd_uboot + TITLE:=AT91Bootstrap for SAMA5D2 ICP board (SDcard) + BUILD_SUBTARGET:=sama5 + BUILD_DEVICES:=microchip_sama5d2-icp +endef + define AT91Bootstrap/sama5d2_xplaineddf_uboot TITLE:=AT91Bootstrap for SAMA5D2 Xplained board (SPI Flash) BUILD_SUBTARGET:=sama5 @@ -121,6 +133,8 @@ endef AT91BOOTSTRAP_TARGETS := \ at91sam9x5eknf_uboot \ at91sam9x5eksd_uboot \ + sama5d2_icpdf_qspi_uboot \ + sama5d2_icpsd_uboot \ sama5d2_xplaineddf_uboot \ sama5d2_xplaineddf_qspi_uboot \ sama5d2_xplainedsd_uboot \ diff --git a/package/boot/uboot-at91/Makefile b/package/boot/uboot-at91/Makefile index a8a71239a398..193f26dae471 100644 --- a/package/boot/uboot-at91/Makefile +++ b/package/boot/uboot-at91/Makefile @@ -59,6 +59,12 @@ define U-Boot/sama5d3_xplained_mmc BUILD_DEVICES:=microchip_sama5d3-xplained endef +define U-Boot/sama5d2_icp_mmc + NAME:=SAMA5D2 ICP board (SDCard) + BUILD_SUBTARGET:=sama5 + BUILD_DEVICES:=microchip_sama5d2-icp +endef + define U-Boot/sama5d2_xplained_spiflash NAME:=SAMA5D2 Xplained board (SPI Flash) BUILD_SUBTARGET:=sama5 @@ -119,6 +125,7 @@ UBOOT_TARGETS := \ at91sam9x5ek_mmc \ sama5d3_xplained_nandflash \ sama5d3_xplained_mmc \ + sama5d2_icp_mmc \ sama5d2_xplained_mmc \ sama5d2_xplained_spiflash \ sama5d4_xplained_mmc \ diff --git a/target/linux/at91/image/sama5.mk b/target/linux/at91/image/sama5.mk index f8e05aae9343..ae3494332139 100644 --- a/target/linux/at91/image/sama5.mk +++ b/target/linux/at91/image/sama5.mk @@ -54,6 +54,17 @@ define Build/at91-sdcard rm -f $@.img $@.boot $@-uboot.env $@-uboot-env.txt) endef +define Device/microchip_sama5d2-icp + $(Device/evaluation-dtb) + DEVICE_VENDOR := Microchip + DEVICE_MODEL := SAMA5D2 ICP + DEVICE_DTS := at91-sama5d2_icp + SUPPORTED_DEVICES := microchip,sama5d2-icp + KERNEL_SIZE := 6144k + $(Device/evaluation-sdimage) +endef +TARGET_DEVICES += microchip_sama5d2-icp + define Device/microchip_sama5d2-xplained $(Device/evaluation-dtb) DEVICE_VENDOR := Microchip -- 2.23.0 --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v4 0/6] at91: add support for sama5d2 icp, sama5d27 wlsom1 ek and sam9x60ek
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi, This series adds support for SAMA5D2 ICP, SAMA5D27-WLSOM1-EK and SAM9X60EK boards. Since SAM9X60's kernel support is included in 5.10 but not on 5.4 1st (patch 1/6) switches to kernel 5.10. Patches 2/6, 5/6 updates the kernel config for sam9x SoCs and sam9x60. Patch 3/6, 4/6, 6/6 adds the boards support. Thank you, Claudiu Beznea Claudiu Beznea (6): at91: kernel: bump to 5.10 at91: enable specific sam9x kernel config flags at91: add support for sama5d2 icp board at91: add support for sama5d27-wlsom1-ek board at91: enable kernel config for sam9x60 at91: add support for sam9x60-ek board package/boot/at91bootstrap/Makefile | 42 +++ package/boot/uboot-at91/Makefile | 35 +++ target/linux/at91/Makefile| 2 +- .../at91/files/arch/arm/boot/dts/wb45n.dts| 220 -- .../at91/files/arch/arm/boot/dts/wb50n.dts| 113 --- .../at91/files/arch/arm/boot/dts/wb50n.dtsi | 205 - target/linux/at91/image/sam9x.mk | 14 +- target/linux/at91/image/sama5.mk | 23 ++ .../101-ARM-at91-build-dtb-for-q5xr5.patch| 10 + .../101-ARM-at91-build-dtb-for-q5xr5.patch| 10 - .../102-ARM-at91-build-dtb-for-wb45n.patch| 12 - ...2-ARM-at91-wb45n-fix-duplicate-label.patch | 20 -- .../103-ARM-at91-build-dtb-for-wb50n.patch| 12 - ...3-ARM-at91-wb50n-fix-duplicate-label.patch | 39 --- target/linux/at91/sam9x/config-default| 286 ++ 15 files changed, 345 insertions(+), 698 deletions(-) delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb45n.dts delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dts delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dtsi create mode 04 target/linux/at91/patches-5.10 create mode 100644 target/linux/at91/patches-5.10/101-ARM-at91-build-dtb-for-q5xr5.patch delete mode 04 target/linux/at91/patches-5.4 delete mode 100644 target/linux/at91/patches-5.4/101-ARM-at91-build-dtb-for-q5xr5.patch delete mode 100644 target/linux/at91/patches-5.4/102-ARM-at91-build-dtb-for-wb45n.patch delete mode 100644 target/linux/at91/patches-5.4/102-ARM-at91-wb45n-fix-duplicate-label.patch delete mode 100644 target/linux/at91/patches-5.4/103-ARM-at91-build-dtb-for-wb50n.patch delete mode 100644 target/linux/at91/patches-5.4/103-ARM-at91-wb50n-fix-duplicate-label.patch -- 2.23.0 --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v4 4/6] at91: add support for sama5d27-wlsom1-ek board
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Add support for SAMA5D27 WLSOM1-EK board. Hardware: - SIP: SAMA5D27C-LD2G-CU including SAMA5D27 MPU and 2Gbit LPDDR2-SDRAM - MMC: one standard SD card interface - Flash: 64 Mb serial quad I/O flash memory (SST26VF064BEUIT-104I/MF) with embedded EUI-48 and EUI-64 MAC addresses - USB: one USB device, one USB host one HSIC interface - Ethernet: 1x10/100Mbps port - WiFi/BT: IEEE 802.11 b/g/n Wi-Fi plus Bluetooth (Wi-Fi/BT) module (ATWILC3000-MR110UA) - Crypto: one ATECC608B-TNGTLS secure element - Video: one LCD RGB 18-bit interface, one ISC 12-bit camera interface - Debug port: one JTAG interface, one UART interface, one WILC UART interface - Leds: one RGB LED - Buttons: start, reset, wakeup, user buttons - Expansion: one tamper connector, one mikrobus interface, 2 XPRO PTC connector - Power managament: PMIC (MCP16502) Flashing: - follow procedure at [1] [1] https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d27WLSom1EKMainPage#Create_a_SD_card_with_the_demo Signed-off-by: Claudiu Beznea --- package/boot/at91bootstrap/Makefile | 14 ++ package/boot/uboot-at91/Makefile| 14 ++ target/linux/at91/image/sama5.mk| 11 +++ 3 files changed, 39 insertions(+) diff --git a/package/boot/at91bootstrap/Makefile b/package/boot/at91bootstrap/Makefile index 56e14c57703c..8711acd286bd 100644 --- a/package/boot/at91bootstrap/Makefile +++ b/package/boot/at91bootstrap/Makefile @@ -118,6 +118,18 @@ define AT91Bootstrap/sama5d27_som1_ekqspi_uboot BUILD_DEVICES:=microchip_sama5d27-som1-ek endef +define AT91Bootstrap/sama5d27_wlsom1_eksd_uboot + TITLE:=AT91Bootstrap for SAMA5D27 WLSOM1 Ek (SDcard0) + BUILD_SUBTARGET:=sama5 + BUILD_DEVICES:=microchip_sama5d27-wlsom1-ek +endef + +define AT91Bootstrap/sama5d27_wlsom1_ekdf_qspi_uboot + TITLE:=AT91Bootstrap for SAMA5D27 WLSOM1 Ek (QSPI Flash) + BUILD_SUBTARGET:=sama5 + BUILD_DEVICES:=microchip_sama5d27-wlsom1-ek +endef + define AT91Bootstrap/sama5d2_ptc_eknf_uboot TITLE:=AT91Bootstrap for SAMA5D2 PTC EK (Nand Flash) BUILD_SUBTARGET:=sama5 @@ -145,6 +157,8 @@ AT91BOOTSTRAP_TARGETS := \ sama5d4_xplainedsd_uboot_secure \ sama5d27_som1_eksd1_uboot \ sama5d27_som1_ekqspi_uboot \ + sama5d27_wlsom1_eksd_uboot \ + sama5d27_wlsom1_ekdf_qspi_uboot \ sama5d2_ptc_eknf_uboot \ sama5d2_ptc_eksd_uboot diff --git a/package/boot/uboot-at91/Makefile b/package/boot/uboot-at91/Makefile index 193f26dae471..5aade7de9cf9 100644 --- a/package/boot/uboot-at91/Makefile +++ b/package/boot/uboot-at91/Makefile @@ -107,6 +107,18 @@ define U-Boot/sama5d27_som1_ek_qspiflash BUILD_DEVICES:=microchip_sama5d27-som1-ek endef +define U-Boot/sama5d27_wlsom1_ek_mmc + NAME:=SAMA5D27 WLSOM1 Ek (SDCard) + BUILD_SUBTARGET:=sama5 + BUILD_DEVICES:=microchip_sama5d27-wlsom1-ek +endef + +define U-Boot/sama5d27_wlsom1_ek_qspiflash + NAME:=SAMA5D27 WLSOM1 Ek (QSPI Flash) + BUILD_SUBTARGET:=sama5 + BUILD_DEVICES:=microchip_sama5d27-wlsom1-ek +endef + define U-Boot/sama5d2_ptc_ek_nandflash NAME:=SAMA5D2 PTC Ek (Nand Flash) BUILD_SUBTARGET:=sama5 @@ -133,6 +145,8 @@ UBOOT_TARGETS := \ sama5d4_xplained_nandflash\ sama5d27_som1_ek_mmc1 \ sama5d27_som1_ek_qspiflash \ + sama5d27_wlsom1_ek_mmc \ + sama5d27_wlsom1_ek_qspiflash \ sama5d2_ptc_ek_nandflash \ sama5d2_ptc_ek_mmc diff --git a/target/linux/at91/image/sama5.mk b/target/linux/at91/image/sama5.mk index ae3494332139..9078db525f97 100644 --- a/target/linux/at91/image/sama5.mk +++ b/target/linux/at91/image/sama5.mk @@ -87,6 +87,17 @@ define Device/microchip_sama5d27-som1-ek endef TARGET_DEVICES += microchip_sama5d27-som1-ek +define Device/microchip_sama5d27-wlsom1-ek + $(Device/evaluation-dtb) + DEVICE_VENDOR := Microchip + DEVICE_MODEL := SAMA5D27 WSOM1 Ek + DEVICE_DTS := at91-sama5d27_wlsom1_ek + SUPPORTED_DEVICES := microchip,sama5d27-wlsom1-ek + KERNEL_SIZE := 6144k + $(Device/evaluation-sdimage) +endef +TARGET_DEVICES += microchip_sama5d27-wlsom1-ek + define Device/microchip_sama5d2-ptc-ek $(Device/evaluation-dtb) DEVICE_VENDOR := Microchip -- 2.23.0 --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
