December 2019 - U-Boot

[U-Boot] [PATCH v2 00/14] dm: add support of new binding in gpio and pincontrol
by Patrick Delaunay 10 Jan '20

10 Jan '20

Hi, I create this patchset to prepare alignment of stm32mp157c-ev1 device-tree with the linux kernel v5.4. One node for touch screen support use the IRQ line configuration using the new kernel binding introduced by the linux kernel commit ede033e1e863c from v5.1 ('dt-bindings: gpio: document the new pull-up/pull-down flags') https://github.com/torvalds/linux/commit/ede033e1e863c gt9147: goodix_ts@5d { compatible = "goodix,gt9147"; reg = <0x5d>; status = "okay"; irq-gpios = <&stmfx_pinctrl 14 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>; irq-flags = <IRQ_TYPE_EDGE_RISING>; }; In Linux Kernel, the GPIO configuration (pull down/up) are now managed by GPIO lib but they are not yet supported by U-boot in uclass GPIO or pincontrol (when used by gpio-hog). This serie adds the support of theses new defines (with ops get_config/set_config) added in kernel GPIO binding and adds the test in sandbox. NB: In a second phase, the removed set_open_drain/get_open_drain API could be replaced by the new ops get_config/set_config. I also align the gpio binding file with the version from the latest kernel v5.3 (I don't think I remove any U-Boot specific part with this patch) I move the added information on gpio hog code in a new file doc/README.gpio. To have functional test, I convert pinctrl-generic to livetree otherwise the pins are not correctly configured in sandbox, when CONFIG_OF_LIVE is activated. For the test on gpio I add information for pin configuration in output of the command "pinmux status" with a simple pincontrol driver associated to GPIO driver. NB: after rebase on master branch, the sandbox test "ut dm power_domain" is failing; it was not the case for v2019.10. => ut dm power_domain Test: dm_test_power_domain: power-domain.c ../test/dm/test-main.c:73, dm_test_destroy(): 0 == uclass_destroy(uc): Expected 0, got -22 ../test/dm/test-main.c:108, dm_do_test(): 0 == dm_test_destroy(uts): Expected 0, got 1 ../test/dm/test-main.c:170, dm_test_main(): 0 == dm_do_test(uts, test, 1): Expected 0, got 1 I think it is linked to commit 52edfed65de9 ("dm: core: device: switch off power domain after device removal") After some investigation : 1/ pincontrol is remove in uclass_destroy(0) 2/ power domain is removed in uclass_destroy(0) 3/ device_chld_unbind() dev_power_domain_off -> probe power domain (again) --> pinctrl_select_state() in device_probe() ---> pincontrol is probed (again) 4/ at the end of dev_power_domain_off() function the power domain is unbind in dev_power_domain_off device_remove(pd.dev, DM_REMOVE_NORMAL); So power domain driver is correctly removed but it is not the case for the pincontrol driver and that cause the issue. The problem occurs after my serie only because I introduce a second pincontrol driver for sandbox, so the dynamic changes but my serie is not the root cause of the issue, it should be investigated by power domain users. Workaround to allow test execution: "dm: core: device: don't probe pinctrl for power domain" My working branch: https://github.com/patrickdelaunay/u-boot/tree/dm CI-Travis build: https://travis-ci.org/patrickdelaunay/u-boot/builds/616716294 Issue for tbs2910 board not reproduced locally with buildman +u-boot.imx exceeds file size limit: 1405+ limit: 0x5fc00 bytes 1406+ actual: 0x60c00 bytes 1407+ excess: 0x1000 bytes Regards Patrick Delaunay Changes in v2: - use the dev_ API instead of ofnode_ function. - Identify property with a new struct ofprop as proposed by Simon Glass - Add dev_ iterate functions - Change dev_ functions in pinctrl-generic - remove the unused GPIOD_REQUESTED - remove the open_drain API and ops - add gpio descriptor initialization helper - change the proposed ops for pin config to set_dir_flags/get_dir_flags - reused the existing API dm_gpio_set_dir_flags/dm_gpio_set_dir - add a new API dm_gpio_get_dir_flags - simplify sandbox GPIO driver: save dir_flags (GPIOD_...) and remove internal flags (GPIOF_...); the previous path "gpio: sandbox: cleanup flag support" is no more needed - add unitary test in dm_test_gpio for set_dir_flags - add some function check in dm_test_gpio_phandles - dm_test_gpio_pin_config change to dm_test_gpio_get_dir_flags - Adapt sandbox_pinctrl_gpio driver with the saved dir_flags in sandbox gpio driver - rebase on v2020.01-rc3 Patrick Delaunay (14): dm: pinctrl: convert pinctrl-single to livetree dm: core: add ofnode and dev function to iterate on node property dm: pinctrl: migrate pinctrl-generic to livetree dt-bindings: gpio: document the new pull-up/pull-down flags gpio: remove GPIOD_REQUESTED gpio: remove the open_drain API and ops gpio: add gpio descriptor initialization helper gpio: add ops for configuration with dir flags dt-bindings: gpio: alignment with kernel v5.3 pinctrl: sandbox: Add mux information in get_pin_muxing test: dm: update test for pins configuration in pinctrl node gpio: sandbox: cleanup binding support test: dm: update test for pins configuration in gpio test: pinmux: add pincontrol-gpio for pin configuration arch/sandbox/dts/test.dts | 85 +++++-- arch/sandbox/include/asm/gpio.h | 38 +-- doc/README.gpio | 42 ++++ doc/device-tree-bindings/gpio/gpio.txt | 304 ++++++++++++---------- drivers/core/of_access.c | 32 +++ drivers/core/ofnode.c | 48 ++++ drivers/core/read.c | 16 ++ drivers/gpio/gpio-uclass.c | 192 ++++++++++---- drivers/gpio/mpc8xxx_gpio.c | 22 -- drivers/gpio/sandbox.c | 321 +++++++++++++++++++----- drivers/pinctrl/pinctrl-generic.c | 30 +-- drivers/pinctrl/pinctrl-sandbox.c | 44 +++- drivers/pinctrl/pinctrl-single.c | 27 +- include/asm-generic/gpio.h | 104 ++++---- include/dm/of_access.h | 40 +++ include/dm/ofnode.h | 63 ++++- include/dm/read.h | 67 +++++ include/dt-bindings/gpio/gpio.h | 6 + include/dt-bindings/gpio/sandbox-gpio.h | 24 ++ test/dm/gpio.c | 69 ++++- test/dm/test-fdt.c | 2 +- test/py/tests/test_pinmux.py | 38 ++- 22 files changed, 1216 insertions(+), 398 deletions(-) create mode 100644 doc/README.gpio create mode 100644 include/dt-bindings/gpio/sandbox-gpio.h -- 2.17.1

3 26

[PATCH] binman: fix default filename of u-boot-with-ucode-ptr in documentation
by Masahiro Yamada 10 Jan '20

10 Jan '20

The suffix should be ".bin" instead of ".dtb" . Signed-off-by: Masahiro Yamada <masahiroy(a)kernel.org> Reviewed-by: Bin Meng <bmeng.cn(a)gmail.com> --- tools/binman/README.entries | 2 +- tools/binman/etype/u_boot_with_ucode_ptr.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/binman/README.entries b/tools/binman/README.entries index 1099433521..26050da770 100644 --- a/tools/binman/README.entries +++ b/tools/binman/README.entries @@ -971,7 +971,7 @@ Entry: u-boot-with-ucode-ptr: U-Boot with embedded microcode pointer -------------------------------------------------------------------- Properties / Entry arguments: - - filename: Filename of u-boot-nodtb.dtb (default 'u-boot-nodtb.dtb') + - filename: Filename of u-boot-nodtb.bin (default 'u-boot-nodtb.bin') - optional-ucode: boolean property to make microcode optional. If the u-boot.bin image does not include microcode, no error will be generated. diff --git a/tools/binman/etype/u_boot_with_ucode_ptr.py b/tools/binman/etype/u_boot_with_ucode_ptr.py index cb7dbc68db..960a5efeb4 100644 --- a/tools/binman/etype/u_boot_with_ucode_ptr.py +++ b/tools/binman/etype/u_boot_with_ucode_ptr.py @@ -18,7 +18,7 @@ class Entry_u_boot_with_ucode_ptr(Entry_blob): """U-Boot with embedded microcode pointer Properties / Entry arguments: - - filename: Filename of u-boot-nodtb.dtb (default 'u-boot-nodtb.dtb') + - filename: Filename of u-boot-nodtb.bin (default 'u-boot-nodtb.bin') - optional-ucode: boolean property to make microcode optional. If the u-boot.bin image does not include microcode, no error will be generated. -- 2.17.1

3 2

[PATCH] dm: Add a debug message when devices are skipped pre-reloc
by Sean Anderson 10 Jan '20

10 Jan '20

This adds a message to lists_bind_fdt when it skips initializing a device pre-relocation. I've had a couple errors where a device didn't initialize properly because one of its dependencies was missing. Signed-off-by: Sean Anderson <seanga2(a)gmail.com> --- drivers/core/lists.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/core/lists.c b/drivers/core/lists.c index 4681b3e5dd..68204c303f 100644 --- a/drivers/core/lists.c +++ b/drivers/core/lists.c @@ -176,8 +176,10 @@ int lists_bind_fdt(struct udevice *parent, ofnode node, struct udevice **devp, if (pre_reloc_only) { if (!dm_ofnode_pre_reloc(node) && - !(entry->flags & DM_FLAG_PRE_RELOC)) + !(entry->flags & DM_FLAG_PRE_RELOC)) { + log_debug("Skipping device pre-relocation\n"); return 0; + } } log_debug(" - found match at '%s': '%s' matches '%s'\n", -- 2.24.1

4 3

[PATCH] Include missing headers for fdt_support.h
by Sean Anderson 10 Jan '20

10 Jan '20

fdt_support.h is missing declarations for bd_t. Including asm/u-boot.h pulls in the definition. Signed-off-by: Sean Anderson <seanga2(a)gmail.com> --- include/fdt_support.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/fdt_support.h b/include/fdt_support.h index 2286ea7793..3f4bc643d4 100644 --- a/include/fdt_support.h +++ b/include/fdt_support.h @@ -9,6 +9,7 @@ #ifdef CONFIG_OF_LIBFDT +#include <asm/u-boot.h> #include <linux/libfdt.h> u32 fdt_getprop_u32_default_node(const void *fdt, int off, int cell, -- 2.23.0

2 1

[PATCH] log: Include missing header for log.h
by Sean Anderson 10 Jan '20

10 Jan '20

log.h references cmd_tbl_t but command.h was not included Signed-off-by: Sean Anderson <seanga2(a)gmail.com> --- include/log.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/log.h b/include/log.h index d8f18a6afd..820cdcc3a2 100644 --- a/include/log.h +++ b/include/log.h @@ -9,6 +9,7 @@ #ifndef __LOG_H #define __LOG_H +#include <command.h> #include <dm/uclass-id.h> #include <linux/list.h> -- 2.24.1

3 2

[PATCH 00/19] dm: core: Fully separate ofdata_to_platdata() from probe()
by Simon Glass 10 Jan '20

10 Jan '20

At present ofdata_to_platdata() is done as part of device_probe(). Drivers are supposed to read their platdata in the ofdata_to_platdata method() but this requirement is not always followed. Having these methods separate helps deal with of-platdata, where the probe() method is common to both DT/of-platdata operation, but the ofdata_to_platdata() method is implemented differently. Another case has come up where this separate is useful. Generation of ACPI tables uses the of-platdata but does not want to probe the device. Probing would cause U-Boot to violate one of its design principles, viz that it should only probe devices that are used. For ACPI we want to generate a table for each device, even if U-Boot does not use it. In fact it may not even be possible to probe the device - e.g. an SD card which is not present will cause an error on probe, yet we still must tell Linux about the SD card connector in case it is used while Linux is running. This series splits out the ofdata_to_platdata() part of device_probe() so that it can be used separately from device_probe(). Thus devices now go through two distinct states when probing: reading platform data and actually touching the hardware to bring the device up. This should not break existing boards since the operations still happen in mostly the same order. The main change is that parents and uclasses are probed after ofdata_to_platdata() is called. HOWEVER it is quite possible that some boards break the rules and due to a series of unfortunate events, something will break. Two boards were found in this category already. SO this series may require some tidying up from board maintainers, if problems arise. Note that there are cases where devices must be probed in the ofdata_to_platdata() method. An example is where a GPIO is selected - this obviously requires that the GPIO device is probed. One board was found to burst its size limit with this series, despite the very small size increase. The patches to remove use of BUG_ON() are to ensure that this series passes tests. Simon Glass (19): common: Add a noisy assert() dm: core: Use assert_noisy() in devres usb: Drop use of BUG_ON() and WARN_ON() x86: apl: Avoid accessing the PCI bus before it is probed pci: Print a warning if the bus is accessed before probing aspeed: ast2500: Read clock ofdata in the correct method dm: core: Don't clear active flag twice when probe() fails dm: core: Move ofdata_to_platdata() call earlier dm: core: Allocate parent data separate from probing parent dm: core: Add a comment for DM_FLAG_OF_PLATDATA dm: core: Export a new function to read platdata dm: core: Add a new flag to track platform data dm: devres: Create a new devres header file test: Add functions to find the amount of allocated memory dm: devres: Convert to use logging dm: test: Add a test driver for devres dm: devres: Add tests dm: devres: Use an enum for the allocation phase dm: devres: Add a new OFDATA phase arch/sandbox/dts/test.dts | 4 + arch/x86/cpu/apollolake/p2sb.c | 20 +- arch/x86/cpu/apollolake/pmc.c | 20 +- drivers/clk/aspeed/clk_ast2500.c | 4 +- drivers/core/device-remove.c | 1 + drivers/core/device.c | 56 +++-- drivers/core/devres.c | 57 ++++- drivers/pci/pci-uclass.c | 13 ++ drivers/usb/gadget/composite.c | 4 + drivers/usb/gadget/f_mass_storage.c | 4 + drivers/usb/musb-new/musb_core.c | 4 + drivers/usb/musb-new/musb_gadget_ep0.c | 2 +- include/dm/device-internal.h | 16 ++ include/dm/device.h | 259 +--------------------- include/dm/devres.h | 289 +++++++++++++++++++++++++ include/dm/uclass-id.h | 1 + include/log.h | 15 ++ include/test/test.h | 10 + include/test/ut.h | 16 ++ test/dm/Makefile | 1 + test/dm/devres.c | 186 ++++++++++++++++ test/dm/test-fdt.c | 58 +++++ test/ut.c | 14 ++ 23 files changed, 760 insertions(+), 294 deletions(-) create mode 100644 include/dm/devres.h create mode 100644 test/dm/devres.c -- 2.24.1.735.g03f4e72817-goog

3 40

[PATCH] stm32mp1: configs: Make all boot devices in distro boot conditional
by Marek Vasut 10 Jan '20

10 Jan '20

Not all systems have all the boot devices enabled, e.g. not all systems have MTD devices and thus do not enable UBI. Make all the boot devices in the distro bootcmd conditional to avoid failures. Signed-off-by: Marek Vasut <marex(a)denx.de> Cc: Patrick Delaunay <patrick.delaunay(a)st.com> Cc: Patrice Chotard <patrice.chotard(a)st.com> --- include/configs/stm32mp1.h | 34 ++++++++++++++++++++++++++++------ 1 file changed, 28 insertions(+), 6 deletions(-) diff --git a/include/configs/stm32mp1.h b/include/configs/stm32mp1.h index d42a7860be..dfc397c63c 100644 --- a/include/configs/stm32mp1.h +++ b/include/configs/stm32mp1.h @@ -98,12 +98,34 @@ #if !defined(CONFIG_SPL_BUILD) -#define BOOT_TARGET_DEVICES(func) \ - func(MMC, mmc, 1) \ - func(UBIFS, ubifs, 0) \ - func(MMC, mmc, 0) \ - func(MMC, mmc, 2) \ - func(PXE, pxe, na) +#ifdef CONFIG_CMD_MMC +#define BOOT_TARGET_DEVICE_MMC0(func) func(MMC, mmc, 0) +#define BOOT_TARGET_DEVICE_MMC1(func) func(MMC, mmc, 1) +#define BOOT_TARGET_DEVICE_MMC2(func) func(MMC, mmc, 2) +#else +#define BOOT_TARGET_DEVICE_MMC0(func) +#define BOOT_TARGET_DEVICE_MMC1(func) +#define BOOT_TARGET_DEVICE_MMC2(func) +#endif + +#ifdef CONFIG_NET +#define BOOT_TARGET_DEVICE_PXE(func) func(PXE, pxe, na) +#else +#define BOOT_TARGET_DEVICE_PXE(func) +#endif + +#ifdef CONFIG_CMD_UBIFS +#define BOOT_TARGET_DEVICE_UBIFS(func) func(UBIFS, ubifs, 0) +#else +#define BOOT_TARGET_DEVICE_UBIFS(func) +#endif + +#define BOOT_TARGET_DEVICES(func) \ + BOOT_TARGET_DEVICE_MMC1(func) \ + BOOT_TARGET_DEVICE_UBIFS(func) \ + BOOT_TARGET_DEVICE_MMC0(func) \ + BOOT_TARGET_DEVICE_MMC2(func) \ + BOOT_TARGET_DEVICE_PXE(func) /* * bootcmd for stm32mp1: -- 2.24.1

2 4

[U-Boot] [PATCH v2 1/4] dm: spi: Return 0 if driver does not implement ops->cs_info
by Bin Meng 09 Jan '20

09 Jan '20

If an SPI controller driver does not implement ops->cs_info, that probably means any chip select number could be valid, hence let's return 0 for spi_cs_info(). Signed-off-by: Bin Meng <bmeng.cn(a)gmail.com> Reviewed-by: Jagan Teki <jagan(a)amarulasolutions.com> --- Changes in v2: - update spi-howto.rst to reflect the code changes doc/driver-model/spi-howto.rst | 4 ++-- drivers/spi/spi-uclass.c | 7 +++---- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/driver-model/spi-howto.rst b/doc/driver-model/spi-howto.rst index a538fdc..7e64fae 100644 --- a/doc/driver-model/spi-howto.rst +++ b/doc/driver-model/spi-howto.rst @@ -634,8 +634,8 @@ method for cs_info() to deal with this. If you don't provide it, then the device tree will be used to determine what chip selects are valid. Return -ENODEV if the supplied chip select is invalid, or 0 if it is valid. -If you don't provide the cs_info() method, -ENODEV is assumed for all -chip selects that do not appear in the device tree. +If you don't provide the cs_info() method, 0 is assumed for all chip selects +that do not appear in the device tree. Test it diff --git a/drivers/spi/spi-uclass.c b/drivers/spi/spi-uclass.c index 88cb2a1..24de0b5 100644 --- a/drivers/spi/spi-uclass.c +++ b/drivers/spi/spi-uclass.c @@ -237,11 +237,10 @@ int spi_cs_info(struct udevice *bus, uint cs, struct spi_cs_info *info) return ops->cs_info(bus, cs, info); /* - * We could assume there is at least one valid chip select, but best - * to be sure and return an error in this case. The driver didn't - * care enough to tell us. + * We could assume there is at least one valid chip select. + * The driver didn't care enough to tell us. */ - return -ENODEV; + return 0; } int spi_find_bus_and_cs(int busnum, int cs, struct udevice **busp, -- 2.7.4

2 15

[PATCH] imx: dts: tbs2910: add u-boot dtsi to shrink image size
by Anatolij Gustschin 09 Jan '20

09 Jan '20

Use U-Boot specific board dtsi to remove some not used nodes and properties. With this change applied considerable size reduction has been observed: $ ./tools/buildman/buildman -b tbs2910 -f tbs2910 || \ ./tools/buildman/buildman -b tbs2910 -sS tbs2910 ... Summary of 2 commits for 1 boards (1 thread, 12 jobs per thread) 01: Merge branch '2019-12-05-master-imports' arm: w+ tbs2910 02: imx: dts: tbs2910: add u-boot dtsi to shrink image size arm: (for 1/1 boards) all -24448.0 text -24448.0 Signed-off-by: Anatolij Gustschin <agust(a)denx.de> --- This patch was only build-tested, maybe this removes to much and needs some tweaking. I'd appreciate if someone could test it on actual hardware and finish the work, so we hopefully can solve frequent CI build breakage caused by this target. arch/arm/dts/imx6q-tbs2910-u-boot.dtsi | 219 +++++++++++++++++++++++++ 1 file changed, 219 insertions(+) create mode 100644 arch/arm/dts/imx6q-tbs2910-u-boot.dtsi diff --git a/arch/arm/dts/imx6q-tbs2910-u-boot.dtsi b/arch/arm/dts/imx6q-tbs2910-u-boot.dtsi new file mode 100644 index 0000000000..3e9307f17f --- /dev/null +++ b/arch/arm/dts/imx6q-tbs2910-u-boot.dtsi @@ -0,0 +1,219 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* + * U-Boot specific modifications for original tbs2910 DTS. + * This drops not used nodes/properties to reduce the image size. + */ + +/ { + /delete-property/ model; + /delete-property/ compatible; + + aliases { + /delete-property/ can0; + /delete-property/ can1; + /delete-property/ gpio3; + /delete-property/ gpio4; + /delete-property/ gpio5; + /delete-property/ ipu1; + /delete-property/ mmc3; + /delete-property/ spi0; + /delete-property/ spi1; + /delete-property/ spi2; + /delete-property/ spi3; + /delete-property/ spi4; + /delete-property/ serial2; + /delete-property/ serial3; + /delete-property/ serial4; + /delete-property/ video1; + }; + + /delete-node/ cpus; + /delete-node/ capture-subsystem; + /delete-node/ chosen; + /delete-node/ display-subsystem; + /delete-node/ fan; + /delete-node/ ir_recv; + /delete-node/ leds; + /delete-node/ memory; + /delete-node/ sound-sgtl5000; + /delete-node/ sound-spdif; + + soc { + u-boot,dm-pre-reloc; + /delete-property/ ranges; + /delete-node/ timer@a00600; + + aips-bus@2000000 { + /delete-property/ ranges; + /delete-node/ aipstz@207c000; + spba-bus@2000000 { + /delete-property/ ranges; + /delete-node/ spba@203c000; + }; + }; + + aips-bus@2100000 { + /delete-property/ ranges; + /delete-node/ aipstz@217c000; + /delete-node/ mlb@218c000; + /delete-node/ romcp@21ac000; + /delete-node/ tzasc@21d0000; + /delete-node/ tzasc@21d4000; + /delete-node/ vdoa@21e4000; + }; + }; +}; + +&anatop { + /delete-node/ regulator-1p1; + /delete-node/ regulator-2p5; + /delete-node/ regulator-3p0; + /delete-node/ regulator-vddcore; + /delete-node/ regulator-vddpu; + /delete-node/ regulator-vddsoc; +}; + +&sata { + /delete-property/ clocks; + /delete-property/ clock-names; + /delete-property/ interrupts; + /delete-property/ interrupts; + /delete-property/ fsl,transmit-level-mV; + /delete-property/ fsl,transmit-boost-mdB; + /delete-property/ fsl,transmit-atten-16ths; + /delete-property/ fsl,receive-eq-mdB; +}; + +&pcie { + /delete-property/ reg-names; + /delete-property/ device_type; + /delete-property/ bus-range; + /delete-property/ ranges; + /delete-property/ num-lanes; + /delete-property/ interrupts; + /delete-property/ interrupt-names; + /delete-property/ #interrupt-cells; + /delete-property/ interrupt-map-mask; + /delete-property/ interrupt-map; + /delete-property/ clocks; + /delete-property/ clock-names; +}; + +&uart1 { + /delete-property/ interrupts; + /delete-property/ clocks; + /delete-property/ clock-names; + /delete-property/ dmas; + /delete-property/ dma-names; +}; + +&uart2 { + /delete-property/ interrupts; + /delete-property/ clocks; + /delete-property/ clock-names; + /delete-property/ dmas; + /delete-property/ dma-names; +}; + +/delete-node/ &L2; +/delete-node/ &asrc; +/delete-node/ &audmux; +/delete-node/ &can1; +/delete-node/ &can2; +/delete-node/ &crypto; +/delete-node/ &dcic1; +/delete-node/ &dcic2; +/delete-node/ &dma_apbh; +/delete-node/ &ecspi1; +/delete-node/ &ecspi2; +/delete-node/ &ecspi3; +/delete-node/ &ecspi4; +/delete-node/ &ecspi5; +/delete-node/ &epit1; +/delete-node/ &epit2; +/delete-node/ &esai; +/delete-node/ &gpt; +/delete-node/ &gpio4; +/delete-node/ &gpio5; +/delete-node/ &gpio6; +/delete-node/ &gpu_3d; +/delete-node/ &gpu_2d; +/delete-node/ &gpu_vg; +/delete-node/ &gpmi; +/delete-node/ &ipu2; +/delete-node/ &kpp; +/delete-node/ &ldb; +/delete-node/ &mipi_csi; +/delete-node/ &mmdc0; +/delete-node/ &mmdc1; +/delete-node/ &ocotp; +/delete-node/ &ocram; +/delete-node/ &pinctrl_gpio_fan; +/delete-node/ &pinctrl_ir; +/delete-node/ &pinctrl_gpio_leds; +/delete-node/ &pinctrl_sgtl5000; +/delete-node/ &pinctrl_spdif; +/delete-node/ &pmu; +/delete-node/ &pwm1; +/delete-node/ &pwm2; +/delete-node/ &pwm3; +/delete-node/ &pwm4; +/delete-node/ &sdma; +/delete-node/ &reg_2p5v; +/delete-node/ &sgtl5000; +/delete-node/ &snvs; +/delete-node/ &spdif; +/delete-node/ &src; +/delete-node/ &ssi1; +/delete-node/ &ssi2; +/delete-node/ &ssi3; +/delete-node/ &tempmon; +/delete-node/ &uart3; +/delete-node/ &uart4; +/delete-node/ &uart5; +/delete-node/ &usbh2; +/delete-node/ &usbh3; +/delete-node/ &usdhc1; +/delete-node/ &vpu; +/delete-node/ &wdog2; +/delete-node/ &weim; + +&gpr { + /delete-node/ ipu1_csi0_mux; + /delete-node/ ipu2_csi1_mux; +}; + +&gpc { + /delete-node/ pgc; +}; + +&hdmi { + /delete-node/ port@2; + /delete-node/ port@3; +}; + +&mipi_dsi { + ports { + /delete-node/ port@2; + /delete-node/ port@3; + }; +}; + +&ipu1 { + u-boot,dm-pre-reloc; + /delete-property/ interrupts; + /delete-property/ clocks; + /delete-property/ clock-names; + /delete-property/ resets; + /delete-node/ port@0; + /delete-node/ port@1; + + port@2 { + /delete-node/ endpoint@3; + /delete-node/ endpoint@4; + }; + port@3 { + /delete-node/ endpoint@3; + /delete-node/ endpoint@4; + }; +}; -- 2.17.1

4 6

[PATCH v2 1/2] Add GigaDevice gd25q128 128Mbit chip to spi-nor id table.
by Mauro Condarelli 09 Jan '20

09 Jan '20

From: MCon <mc5686(a)mclink.it> Tested on VoCore2 Signed-off-by: MCon <mc5686(a)mclink.it> Signed-off-by: Mauro Condarelli <mc5686(a)mclink.it> --- Changes in v2: None drivers/mtd/spi/spi-nor-ids.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c index d3b84574ac..973b6f86c9 100644 --- a/drivers/mtd/spi/spi-nor-ids.c +++ b/drivers/mtd/spi/spi-nor-ids.c @@ -107,6 +107,11 @@ const struct flash_info spi_nor_ids[] = { SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB) }, + { + INFO("gd25q128", 0xc84018, 0, 64 * 1024, 256, + SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | + SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB) + }, { INFO("gd25lq128", 0xc86018, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_DUAL_READ | -- 2.24.1

4 9