February 2021 - U-Boot

i2c: i2c-gpio: Fix GPIO output
by Harm Berntsen 21 Feb '21

21 Feb '21

The dm_gpio_set_dir_flags function cannot be used to update the configuration of a GPIO pin because it does a bitwise OR with the existing flags. Looks like commit 788ea834124b ("gpio: add function _dm_gpio_set_dir_flags") has introduced this behaviour and the i2c-gpio driver has been broken since. Signed-off-by: Harm Berntsen <harm.berntsen(a)nedap.com> CC: Heiko Schocher <hs(a)denx.de> CC: Patrick Delaunay <patrick.delaunay(a)st.com> --- drivers/i2c/i2c-gpio.c | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/drivers/i2c/i2c-gpio.c b/drivers/i2c/i2c-gpio.c index 381938c956..9c5e0d4d68 100644 --- a/drivers/i2c/i2c-gpio.c +++ b/drivers/i2c/i2c-gpio.c @@ -50,9 +50,10 @@ static void i2c_gpio_sda_set(struct i2c_gpio_bus *bus, int bit) struct gpio_desc *sda = &bus->gpios[PIN_SDA]; if (bit) - dm_gpio_set_dir_flags(sda, GPIOD_IS_IN); + sda->flags = (sda->flags & ~GPIOD_IS_OUT) | GPIOD_IS_IN; else - dm_gpio_set_dir_flags(sda, GPIOD_IS_OUT); + sda->flags = (sda->flags & (~GPIOD_IS_IN & ~GPIOD_IS_OUT_ACTIVE)) | GPIOD_IS_OUT; + dm_gpio_set_dir(sda); } static void i2c_gpio_scl_set(struct i2c_gpio_bus *bus, int bit) @@ -61,14 +62,16 @@ static void i2c_gpio_scl_set(struct i2c_gpio_bus *bus, int bit) int count = 0; if (bit) { - dm_gpio_set_dir_flags(scl, GPIOD_IS_IN); + scl->flags = (scl->flags & ~GPIOD_IS_OUT) | GPIOD_IS_IN; + dm_gpio_set_dir(scl); while (!dm_gpio_get_value(scl) && count++ < 100000) udelay(1); if (!dm_gpio_get_value(scl)) pr_err("timeout waiting on slave to release scl\n"); } else { - dm_gpio_set_dir_flags(scl, GPIOD_IS_OUT); + scl->flags = (scl->flags & (~GPIOD_IS_IN & ~GPIOD_IS_OUT_ACTIVE)) | GPIOD_IS_OUT; + dm_gpio_set_dir(scl); } } @@ -76,11 +79,11 @@ static void i2c_gpio_scl_set(struct i2c_gpio_bus *bus, int bit) static void i2c_gpio_scl_set_output_only(struct i2c_gpio_bus *bus, int bit) { struct gpio_desc *scl = &bus->gpios[PIN_SCL]; - ulong flags = GPIOD_IS_OUT; + scl->flags = (scl->flags & (~GPIOD_IS_IN & ~GPIOD_IS_OUT_ACTIVE)) | GPIOD_IS_OUT; if (bit) - flags |= GPIOD_IS_OUT_ACTIVE; - dm_gpio_set_dir_flags(scl, flags); + scl->flags |= GPIOD_IS_OUT_ACTIVE; + dm_gpio_set_dir(scl); } static void i2c_gpio_write_bit(struct i2c_gpio_bus *bus, int delay, uchar bit) -- 2.29.2

2 1

[PATCH] i2c: at91: fix crash when using 'i2c probe'
by Eugen Hristev 21 Feb '21

21 Feb '21

When issuing 'i2c probe', the driver was crashing, because at probe there is a request with zero length buffer to write to i2c bus. The xfer_msg function assumes the buffer is always there, and never checks for the buffer length. => i2c dev 0 Setting bus to 0 => i2c probe Valid chip addresses: data abort pc : [<7ffa97dc>] lr : [<7ffa96f8>] reloc pc : [<66f277dc>] lr : [<66f276f8>] sp : 7fb7c110 ip : 7ff87a28 fp : 7ff99938 r10: 00000002 r9 : 7fb7dec0 r8 : 00000000 r7 : e181c600 r6 : 7fb88c20 r5 : 00000000 r4 : 7fb7c128 r3 : 00000000 r2 : 00000001 r1 : 00000000 r0 : 00000009 Flags: nZCv IRQs off FIQs off Mode SVC_32 Code: eb0092f4 e1a00005 e8bd81f0 e594300c (e5d33000) Resetting CPU ... Fixes: 8800e0fa20 ("i2c: atmel: add i2c driver") Signed-off-by: Eugen Hristev <eugen.hristev(a)microchip.com> --- drivers/i2c/at91_i2c.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/i2c/at91_i2c.c b/drivers/i2c/at91_i2c.c index 9d6c6d80e2..dfd649cd57 100644 --- a/drivers/i2c/at91_i2c.c +++ b/drivers/i2c/at91_i2c.c @@ -50,6 +50,10 @@ static int at91_i2c_xfer_msg(struct at91_i2c_bus *bus, struct i2c_msg *msg) u32 i; int ret = 0; + /* if there is no message to send/receive, just exit quietly */ + if (msg->len == 0) + return ret; + readl(&reg->sr); if (is_read) { writel(TWI_CR_START, &reg->cr); -- 2.25.1

2 1

[PATCH] usb: kbd: Also accept keyboards with Interrupt OUT endpoint
by Stefan Brüns 20 Feb '21

20 Feb '21

The OUT endpoint can just be ignored as it is not used, just as the corresponding Set_Report request for IN-only interfaces. E.g. the Linux gadget hid keyboard also provides an interrupt endpoint. Also cleanup confusing debug messages like "found set protocol", which is printed when a keyboard device is found, while the Set_Protocol request is issued quite some time later. Signed-off-by: Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- common/usb_kbd.c | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/common/usb_kbd.c b/common/usb_kbd.c index 60c6027e04..afad260d3d 100644 --- a/common/usb_kbd.c +++ b/common/usb_kbd.c @@ -443,6 +443,7 @@ static int usb_kbd_probe_dev(struct usb_device *dev, unsigned int ifnum) struct usb_interface *iface; struct usb_endpoint_descriptor *ep; struct usb_kbd_pdata *data; + int epNum; if (dev->descriptor.bNumConfigurations != 1) return 0; @@ -458,19 +459,21 @@ static int usb_kbd_probe_dev(struct usb_device *dev, unsigned int ifnum) if (iface->desc.bInterfaceProtocol != USB_PROT_HID_KEYBOARD) return 0; - if (iface->desc.bNumEndpoints != 1) - return 0; + for (epNum = 0; epNum < iface->desc.bNumEndpoints; epNum++) { + ep = &iface->ep_desc[epNum]; - ep = &iface->ep_desc[0]; + /* Check if endpoint is interrupt IN endpoint */ + if ((ep->bmAttributes & 3) != 3) + continue; - /* Check if endpoint 1 is interrupt endpoint */ - if (!(ep->bEndpointAddress & 0x80)) - return 0; + if (ep->bEndpointAddress & 0x80) + break; + } - if ((ep->bmAttributes & 3) != 3) + if (epNum == iface->desc.bNumEndpoints) return 0; - debug("USB KBD: found set protocol...\n"); + debug("USB KBD: found interrupt EP: 0x%x\n", ep->bEndpointAddress); data = malloc(sizeof(struct usb_kbd_pdata)); if (!data) { @@ -498,13 +501,15 @@ static int usb_kbd_probe_dev(struct usb_device *dev, unsigned int ifnum) data->last_report = -1; /* We found a USB Keyboard, install it. */ + debug("USB KBD: set boot protocol\n"); usb_set_protocol(dev, iface->desc.bInterfaceNumber, 0); - debug("USB KBD: found set idle...\n"); #if !defined(CONFIG_SYS_USB_EVENT_POLL_VIA_CONTROL_EP) && \ !defined(CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE) + debug("USB KBD: set idle interval...\n"); usb_set_idle(dev, iface->desc.bInterfaceNumber, REPEAT_RATE / 4, 0); #else + debug("USB KBD: set idle interval=0...\n"); usb_set_idle(dev, iface->desc.bInterfaceNumber, 0, 0); #endif -- 2.30.1

2 1

[PATCH 0/2 v3] Add ESRT and test ESRT creation
by Jose Marinho 20 Feb '21

20 Feb '21

The following 2 commits add the ESRT and provide a test of the functionality. The first commit adds the ESRT as defined in the UEFI 2.8 specification. An empty ESRT is created during the execution of the efi_init_obj_list(). The ESRT is updated when: 1) a FMP protocol is installed in the system: this will add the corresponding entries to the ESRT. 2) a capsule is installed via UpdateCapsule: this should update entries already present in the ESRT. This implementation of the ESRT creation takes input from FMP only. It is assumed that the FMP will maintain the following values across reboot: - LastAttemptVersion. - LastAttemptStatus. The second commit enables testing the ESRT creation in the sandbox platform. That commit is composed of 2 tests. - Test 1 executes from the u-boot shell with "ut lib". - Test 2 executes in the pytest environment. Patch v3: - Address v2 comments. Patch v2: - The ESRT is now regenerated from scratch at every FMP EVT_NOTIFY_SIGNAL and whenever a capsule is updated. - Extended TestEfiCapsuleFirmwareFit::test_efi_capsule_fw3 to verify that the ESRT is correctly populated after an UpdateCapsule. - Addressed v1 comments. Patch v1: - reworked the ESRT creation code, allowing table to resize as FMPs are installed. - registered a callback for the FMP protocol install. - Created a unit test running on the sandbox platform. rfc: initial patch submission CC: Heinrich Schuchardt <xypron.glpk(a)gmx.de> CC: Sughosh Ganu <sughosh.ganu(a)linaro.org> CC: AKASHI Takahiro <takahiro.akashi(a)linaro.org> CC: Ilias Apalodimas <ilias.apalodimas(a)linaro.org> CC: Andre Przywara <andre.przywara(a)arm.com> CC: Alexander Graf <agraf(a)csgraf.de> CC: nd(a)arm.com Jose Marinho (2): efi: Add ESRT to the EFI system table efi: ESRT creation tests cmd/efidebug.c | 68 +++ include/efi_api.h | 21 + include/efi_loader.h | 20 + lib/efi_loader/Kconfig | 7 + lib/efi_loader/Makefile | 1 + lib/efi_loader/efi_capsule.c | 8 + lib/efi_loader/efi_esrt.c | 518 ++++++++++++++++++ lib/efi_loader/efi_setup.c | 6 + test/lib/Makefile | 1 + test/lib/efi_esrt.c | 191 +++++++ .../test_efi_capsule/test_capsule_firmware.py | 4 + 11 files changed, 845 insertions(+) create mode 100644 lib/efi_loader/efi_esrt.c create mode 100644 test/lib/efi_esrt.c -- 2.17.1

1 2

[PATCH v2 2/2] clk: imx8mp Enable EQOS clock
by Arendt, Steffen 20 Feb '21

20 Feb '21

Enable EQOS clock for imx8mp V2 includes if CONFIG .... Signed-off-by: Steffen Arendt <s.arendt(a)sensopart.de<mailto:s.arendt@sensopart.de>> --- diff --git a/drivers/clk/imx/clk-imx8mp.c b/drivers/clk/imx/clk-imx8mp.c index b31afb31c0..1ab5587e4e 100644 --- a/drivers/clk/imx/clk-imx8mp.c +++ b/drivers/clk/imx/clk-imx8mp.c @@ -130,6 +130,16 @@ static const char *imx8mp_ecspi3_sels[] = "osc_24m", "sys_pll2_200m", "sys_pll1 "sys_pll2_250m", "audio_pll2_out", ; #endif +#if CONFIG_IS_ENABLED(DWC_ETH_QOS) +static const char *imx8mp_enet_qos_sels[] = "osc_24m", "sys_pll2_125m", "sys_pll2_50m", + "sys_pll2_100m", "sys_pll1_160m", "audio_pll1_out", + "video_pll1_out", "clk_ext4", ; + +static const char *imx8mp_enet_qos_timer_sels[] = "osc_24m", "sys_pll2_100m", "audio_pll1_out", + "clk_ext1", "clk_ext2", "clk_ext3", + "clk_ext4", "video_pll1_out", ; +#endif + static const char *imx8mp_usdhc1_sels[] = "clock-osc-24m", "sys_pll1_400m", "sys_pll1_800m", "sys_pll2_500m", "sys_pll3_out", "sys_pll1_266m", "audio_pll2_out", "sys_pll1_100m", ; @@ -426,6 +436,13 @@ static int imx8mp_clk_probe(struct udevice *dev) imx_clk_gate4("ecspi3_root_clk", "ecspi3", base + 0x4090, 0)); #endif +#if CONFIG_IS_ENABLED(DWC_ETH_QOS) + clk_dm(IMX8MP_CLK_ENET_QOS, + imx8m_clk_composite("enet_qos", imx8mp_enet_qos_sels, base + 0xa880)); + clk_dm(IMX8MP_CLK_ENET_QOS_TIMER, + imx8m_clk_composite("enet_qos_timer", imx8mp_enet_qos_timer_sels, base + 0xa900)); +#endif + return 0; _____________________________________________________________________________ SensoPart Industriesensorik GmbH Am Wiedenbach 1 79695 Wieden Deutschland Telefon: +49 7673 821 0 Amtsgericht Freiburg HRB 660163 USt-IdNr.: DE 811614252 Gesch?ftsf?hrer: Dr. Theodor Wanner, Thorsten Wanner Informationen gem. Art. 13 DSGVO f?r unsere Kunden, Partner, Lieferanten finden Sie in unserer Erkl?rung zum Datenschutz unter https://www.sensopart.com/de/datenschutz

1 0

Pull request: u-boot-sunxi/master for v2021.04
by Andre Przywara 20 Feb '21

20 Feb '21

Hi Tom, please pull the master branch from u-boot-sunxi, containing some fixes for 2021.04: ------------------------- - H616 clock fix to enable video PLL - sunxi-common.h cleanups - support for UART1 as the console on sun8i - removing wrong linux,stdout-path from DTs ------------------------- Build-tested on all 156 sunxi boards, boot tested on some of them. Thanks, Andre ============== The following changes since commit a1a652e8016426e2d67148cab225cd5ec45189fb: Merge tag 'mmc-2021-2-19' of https://gitlab.denx.de/u-boot/custodians/u-boot-mmc (2021-02-19 11:56:14 -0500) are available in the Git repository at: https://gitlab.denx.de/u-boot/custodians/u-boot-sunxi.git for you to fetch changes up to e036a1d227112565cdf32b5558ac6ccaf5d1633f: fdt/sunxi: Remove OF_STDOUT_PATH (2021-02-19 23:29:47 +0000) ---------------------------------------------------------------- Andre Przywara (1): fdt/sunxi: Remove OF_STDOUT_PATH Jernej Skrabec (1): sunxi: spl: Fix H616 clock initialization Samuel Holland (1): sunxi: Remove dead ifdefs in sunxi-common.h Tobias Schramm (1): sunxi: support boot console on uart1 for sun8i README | 1 - arch/arm/include/asm/arch-sunxi/gpio.h | 1 + arch/arm/mach-sunxi/board.c | 5 +++++ arch/arm/mach-sunxi/clock_sun50i_h6.c | 5 +++++ common/fdt_support.c | 9 +-------- include/configs/sunxi-common.h | 33 --------------------------------- scripts/config_whitelist.txt | 1 - 7 files changed, 12 insertions(+), 43 deletions(-)

2 1

[PATCH 1/1] doc: qfw man-page
by Heinrich Schuchardt 20 Feb '21

20 Feb '21

Provide a man-page for the qfw command. Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- doc/usage/index.rst | 1 + doc/usage/qfw.rst | 89 +++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 90 insertions(+) create mode 100644 doc/usage/qfw.rst diff --git a/doc/usage/index.rst b/doc/usage/index.rst index 5754958d7e..153a8df3f8 100644 --- a/doc/usage/index.rst +++ b/doc/usage/index.rst @@ -27,5 +27,6 @@ Shell commands loady mbr pstore + qfw sbi true diff --git a/doc/usage/qfw.rst b/doc/usage/qfw.rst new file mode 100644 index 0000000000..87463e1e5b --- /dev/null +++ b/doc/usage/qfw.rst @@ -0,0 +1,89 @@ +.. SPDX-License-Identifier: GPL-2.0+ + +qfw command +=========== + +Synopsis +-------- + +:: + + qfw list + qfw cpus + qfw load [kernel_addr [initrd_addr]] + +Description +----------- + +The *qfw* command is used to retrieve information form the QEMU firmware. + +The *qfw list* sub-command displays the QEMU firmware files. + +The *qfw cpus* sub-command displays the available CPUs. + +The *qfw load* command is used to load a kernel and an initial RAM disk. + +kernel_addr + address to which the file specified by the -kernel parameter of QEMU shall + be loaded. Defaults to environment variable *loadaddr* and further to + the value of *CONFIG_LOADADDR*. + +initrd_addr + address to which the file specified by the -initrd parameter of QEMU shall + be loaded. Defaults to environment variable *ramdiskaddr* and further to + the value of *CONFIG_RAMDISK_ADDR*. + +Examples +-------- + +QEMU firmware files are listed via the *qfw list* command: + +:: + + => qfw list + etc/boot-fail-wait + etc/smbios/smbios-tables + etc/smbios/smbios-anchor + etc/e820 + genroms/kvmvapic.bin + genroms/linuxboot.bin + etc/system-states + etc/acpi/tables + etc/table-loader + etc/tpm/log + etc/acpi/rsdp + bootorder + +The available CPUs can be shown via the *qfw cpus* command: + +:: + + => qfw cpu + 2 cpu(s) online + +The *-kernel* and *-initrd* parameters allow to specify a kernel and an +initial RAM disk for QEMU: + +.. code-block:: bash + + $ qemu-system-x86_64 -machine pc-i440fx-2.5 -bios u-boot.rom -m 1G \ + -nographic -kernel vmlinuz -initrd initrd + +Now the kernel and the initial RAM disk can be loaded to the U-Boot memory via +the *qfw load* command and booted thereafter. + +:: + + => qfw load ${kernel_addr_r} ${ramdisk_addr_r} + loading kernel to address 0000000001000000 size 5048f0 initrd 0000000004000000 size 3c94891 + => zboot 1000000 5048f0 4000000 3c94891 + Valid Boot Flag + Magic signature found + Linux kernel version 4.19.0-14-amd64 (debian-kernel(a)lists.debian.org) #1 SMP Debian 4.19.171-2 (2021-01-30) + Building boot_params at 0x00090000 + Loading bzImage at address 100000 (5260160 bytes) + +Configuration +------------- + +The qfw command is only available if CONFIG_CMD_QFW=y. -- 2.30.0

2 1

[RESEND PATCH 00/16] Nokia RX-51: Fix USB TTY console and enable it
by Pali Rohár 20 Feb '21

20 Feb '21

This series contain resensed patches from two patch series: * Nokia RX-51: Fix USB TTY console and enable it * usbtty/musb: Fix file transfers They are rebased on top of master branch. This patch series fix usbtty code (serial console via USB peripheral mode), fix underlying musb peripheral code, fix compilation of CONFIG_USB_DEVICE (used by usbtty), remove unused Nokia RX-51 code to decrease size of U-Boot binary and finally enable usbtty serial console for Nokia RX-51. With this patch series debugging of Nokia RX-51 can be done also via USB serial console. It fixes also stability of musb code and allows usage of file transfers via Kermit protocol on Nokia RX-51. Kermit file transfer via U-Boot loadb command is stable on Nokia N900 and gives about 52kB/s transfer rate. On computer this serial console is accessible via /dev/ttyACM0 device. Pali Rohár (16): serial: usbtty: Fix puts function serial: usbtty: Send urb data in correct order usb: musb: Fix compilation of gadget code usb: musb: Always clear the data toggle bit when configuring ep usb: musb: Fix configuring FIFO for endpoints usb: musb: Read value of PERI_RXCSR to 16bit variable usb: musb: Fix transmission of bigger buffers usb: musb: Fix receiving of bigger buffers usb: musb: Fix handling interrupts for EP0 and SET ADDRESS commmand usb: musb: Ensure that we set musb dynamic FIFO buffer for every endpoint usb: gadget: Use dbg_ep0() macro instead of serial_printf() arm: omap3: Compile lowlevel_init() function only when it is used arm: omap3: Compile s_init() function only when it is used Nokia RX-51: Remove function set_muxconf_regs() Nokia RX-51: Move content of rx51.h to rx51.c Nokia RX-51: Enable usbtty serial console by default Makefile | 1 + arch/arm/mach-omap2/omap3/board.c | 3 + arch/arm/mach-omap2/omap3/lowlevel_init.S | 6 +- board/nokia/rx51/rx51.c | 28 +- board/nokia/rx51/rx51.h | 377 ---------------------- configs/nokia_rx51_defconfig | 7 +- doc/README.nokia_rx51 | 15 +- drivers/serial/usbtty.c | 16 +- drivers/usb/gadget/ep0.c | 16 +- drivers/usb/musb/musb_core.c | 12 +- drivers/usb/musb/musb_udc.c | 61 ++-- include/configs/nokia_rx51.h | 21 +- 12 files changed, 82 insertions(+), 481 deletions(-) delete mode 100644 board/nokia/rx51/rx51.h -- 2.20.1

4 68

[PATCH v2 0/1] Move qfw to DM, add preliminary on Arm
by Asherah Connor 20 Feb '21

20 Feb '21

Version 2 of this series explores moving the QFW driver to the driver model. We configure QFW on Arm from the device tree, while x86 uses a U_BOOT_DRVINFO. All the logic for talking PIO/MMIO/DMA now lives in the QFW driver. I've moved all the static variables from the qfw driver into its priv data section. Is this preferable? It adds some complexity to callers, as they need to obtain and then pass the `struct udevice *' around. I haven't changed much of the calling convention into the driver yet, and so for the most part we still "skip" the device model, instead relying on it just to help us bring the device up and locate it again later. Where we go from here depends on whether we keep it in UCLASS_MISC and whether we feel like it's useful to change the way we call into it further. There are some #ifdef hacks surrounding pause/yield and use of outw/inb/etc. in the driver. It feels like these should still be in arch-specific parts somehow. This is tested as building and working correctly on arm64 and x86_64 qemu. To view the main driver file as of this change in a non-diffed format, see: https://git.src.kameliya.ee/~kameliya/u-boot/tree/qfw-priv/item/drivers/mis… (no changes since v1) Asherah Connor (1): arm: x86: qemu: move qfw to DM, include Arm support arch/arm/Kconfig | 1 + arch/x86/cpu/qemu/cpu.c | 7 +- arch/x86/cpu/qemu/qemu.c | 54 ++------ arch/x86/cpu/qfw_cpu.c | 11 +- cmd/qfw.c | 44 +++--- drivers/misc/Kconfig | 1 + drivers/misc/qfw.c | 287 +++++++++++++++++++++++++++------------ include/qfw.h | 63 +++++---- 8 files changed, 291 insertions(+), 177 deletions(-) -- 2.20.1

2 3

[PATCH 0/5] Add Micronova srl S027_3 board support
by Giulio Benetti 20 Feb '21

20 Feb '21

Add Micronova srl S027_3 board support Giulio Benetti (5): arm: allwinner: dts: a20: add uart2_pa_pins sunxi: allow SYS_BOARD to be set sunxi: add SYS_VENDOR to Kconfig sun7i: add support for Micronova srl s027_3 board pwm: sunxi: enable pwm0 support on sun7i arch/arm/dts/Makefile | 1 + arch/arm/dts/sun7i-a20-s027_3.dts | 272 ++++++++++++++++++++++++++ arch/arm/dts/sun7i-a20.dtsi | 5 + arch/arm/include/asm/arch-sunxi/pwm.h | 3 +- arch/arm/mach-sunxi/Kconfig | 5 + board/micronovasrl/s027_3/MAINTAINERS | 5 + board/micronovasrl/s027_3/Makefile | 8 + board/micronovasrl/s027_3/s027_3.c | 29 +++ configs/micronovasrl-s027_3_defconfig | 37 ++++ 9 files changed, 364 insertions(+), 1 deletion(-) create mode 100644 arch/arm/dts/sun7i-a20-s027_3.dts create mode 100644 board/micronovasrl/s027_3/MAINTAINERS create mode 100644 board/micronovasrl/s027_3/Makefile create mode 100644 board/micronovasrl/s027_3/s027_3.c create mode 100644 configs/micronovasrl-s027_3_defconfig -- 2.25.1

3 17