From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gregory CLEMENT Date: Sun, 16 Dec 2018 10:26:57 +0100 Subject: [U-Boot] [PATCH v4 6/7] MSCC: add board support for the Luton based evaluation board In-Reply-To: <9dc41cb5-847f-efbd-e58b-da46bda17864@gmail.com> (Daniel Schwierzeck's message of "Sat, 15 Dec 2018 18:13:28 +0100") References: <20181214151651.2974-1-gregory.clement@bootlin.com> <20181214151651.2974-7-gregory.clement@bootlin.com> <9dc41cb5-847f-efbd-e58b-da46bda17864@gmail.com> Message-ID: <87lg4pkeji.fsf@bootlin.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de Hi Daniel, =20 On sam., d=C3=A9c. 15 2018, Daniel Schwierzeck wrote: > Am 14.12.18 um 16:16 schrieb Gregory CLEMENT: >> Adding the support for the Luton boards PCB91 which share common code wi= th >> the Ocelots boards, including board code, device tree and configuration. >>=20 >> Signed-off-by: Gregory CLEMENT >> --- >> MAINTAINERS | 1 + >> arch/mips/dts/luton_pcb091.dts | 36 ++++++++++++++ >> arch/mips/dts/mscc,luton.dtsi | 87 ++++++++++++++++++++++++++++++++++ >> arch/mips/mach-mscc/Kconfig | 2 + >> board/mscc/luton/Kconfig | 14 ++++++ >> board/mscc/luton/Makefile | 3 ++ >> board/mscc/luton/luton.c | 28 +++++++++++ >> configs/mscc_luton_defconfig | 66 ++++++++++++++++++++++++++ >> 8 files changed, 237 insertions(+) >> create mode 100644 arch/mips/dts/luton_pcb091.dts >> create mode 100644 arch/mips/dts/mscc,luton.dtsi >> create mode 100644 board/mscc/luton/Kconfig >> create mode 100644 board/mscc/luton/Makefile >> create mode 100644 board/mscc/luton/luton.c >> create mode 100644 configs/mscc_luton_defconfig >>=20 > >> diff --git a/configs/mscc_luton_defconfig b/configs/mscc_luton_defconfig >> new file mode 100644 >> index 0000000000..47fe12b6ee >> --- /dev/null >> +++ b/configs/mscc_luton_defconfig >> @@ -0,0 +1,66 @@ >> +CONFIG_MIPS=3Dy >> +CONFIG_SYS_TEXT_BASE=3D0x40000000 >> +CONFIG_SYS_MALLOC_F_LEN=3D0x2000 >> +CONFIG_DEBUG_UART_BOARD_INIT=3Dy >> +CONFIG_DEBUG_UART_BASE=3D0x70100000 >> +CONFIG_DEBUG_UART_CLOCK=3D208333333 >> +CONFIG_ARCH_MSCC=3Dy >> +CONFIG_TARGET_LUTON_PCB091=3Dy >> +CONFIG_DDRTYPE_MT47H128M8HQ=3Dy >> +CONFIG_SYS_LITTLE_ENDIAN=3Dy >> +CONFIG_MIPS_BOOT_FDT=3Dy >> +CONFIG_DEFAULT_DEVICE_TREE=3D"luton_pcb091" >> +CONFIG_DEBUG_UART=3Dy >> +CONFIG_FIT=3Dy >> +CONFIG_BOOTDELAY=3D3 >> +CONFIG_USE_BOOTARGS=3Dy >> +CONFIG_BOOTARGS=3D"console=3DttyS0,115200" >> +CONFIG_LOGLEVEL=3D7 >> +CONFIG_DISPLAY_CPUINFO=3Dy >> +CONFIG_SYS_PROMPT=3D"pcb091 # " >> +# CONFIG_CMD_BDI is not set >> +# CONFIG_CMD_CONSOLE is not set >> +# CONFIG_CMD_ELF is not set >> +# CONFIG_CMD_EXPORTENV is not set >> +# CONFIG_CMD_IMPORTENV is not set >> +# CONFIG_CMD_CRC32 is not set >> +CONFIG_CMD_MD5SUM=3Dy >> +CONFIG_CMD_MEMINFO=3Dy >> +CONFIG_CMD_MEMTEST=3Dy >> +# CONFIG_CMD_FLASH is not set >> +CONFIG_CMD_GPIO=3Dy >> +CONFIG_CMD_SF=3Dy >> +CONFIG_CMD_SPI=3Dy >> +CONFIG_CMD_DHCP=3Dy >> +# CONFIG_NET_TFTP_VARS is not set >> +# CONFIG_CMD_NFS is not set >> +CONFIG_CMD_PING=3Dy >> +CONFIG_CMD_MTDPARTS=3Dy >> +CONFIG_MTDIDS_DEFAULT=3D"nor0=3Dspi_flash" >> +CONFIG_MTDPARTS_DEFAULT=3D"mtdparts=3Dspi_flash:512k(UBoot),256k(Env),2= 56k(conf),6m at 1m(linux)" >> +# CONFIG_ISO_PARTITION is not set >> +CONFIG_OF_EMBED=3Dy > > this gives now a build warning > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WARNING = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > CONFIG_OF_EMBED is enabled. This option should only > be used for debugging purposes. Please use > CONFIG_OF_SEPARATE for boards in mainline. > See doc/README.fdt-control for more info. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D I did not get this warning. For now I base my series on v2018.11, should I base it on v2019.01-rc1 (i didn't realized it was already released) ? > > > Shall I change it when applying or do you want to test it first and send > a follow-up patch? I'd like to test it to be sure it continue to work. Thanks, Gregory > >> +CONFIG_ENV_IS_IN_SPI_FLASH=3Dy >> +CONFIG_NET_RANDOM_ETHADDR=3Dy >> +CONFIG_CLK=3Dy >> +CONFIG_DM_GPIO=3Dy >> +CONFIG_DM_SPI_FLASH=3Dy >> +CONFIG_SPI_FLASH=3Dy >> +CONFIG_SPI_FLASH_BAR=3Dy >> +CONFIG_SPI_FLASH_GIGADEVICE=3Dy >> +CONFIG_SPI_FLASH_MACRONIX=3Dy >> +CONFIG_SPI_FLASH_SPANSION=3Dy >> +CONFIG_SPI_FLASH_STMICRO=3Dy >> +CONFIG_SPI_FLASH_WINBOND=3Dy >> +CONFIG_SPI_FLASH_MTD=3Dy >> +CONFIG_DM_ETH=3Dy >> +CONFIG_PINCTRL=3Dy >> +CONFIG_PINCONF=3Dy >> +CONFIG_DM_SERIAL=3Dy >> +CONFIG_DEBUG_UART_SHIFT=3D2 >> +CONFIG_SYS_NS16550=3Dy >> +CONFIG_SPI=3Dy >> +CONFIG_DM_SPI=3Dy >> +CONFIG_SOFT_SPI=3Dy >> +CONFIG_LZMA=3Dy >> +CONFIG_XZ=3Dy >>=20 > > --=20 > - Daniel --=20 Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com