From: Conor Dooley <conor@kernel.org>
To: Padmarao Begari <padmarao.begari@microchip.com>
Cc: u-boot@lists.denx.de, jagan@amarulasolutions.com,
rick@andestech.com, ycliang@andestech.com, bmeng.cn@gmail.com,
cyril.jean@microchip.com, conor.dooley@microchip.com,
valentina.fernandezalanis@microchip.com,
nagasuresh.relli@microchip.com
Subject: Re: [PATCH 3/4] riscv: Update Microchip MPFS Icicle Kit support
Date: Wed, 19 Oct 2022 17:09:38 +0100 [thread overview]
Message-ID: <Y1AhQpde8SbY2VIL@spud> (raw)
In-Reply-To: <20221019145322.2274420-4-padmarao.begari@microchip.com>
On Wed, Oct 19, 2022 at 08:23:21PM +0530, Padmarao Begari wrote:
> This patch updates Microchip MPFS Icicle Kit support. For now,
> add Microchip QSPI driver and a small 4MB reservation is
> made at the end of 32-bit DDR to provide some memory for
> the HSS to use.
>
> Signed-off-by: Padmarao Begari <padmarao.begari@microchip.com>
> ---
> board/microchip/mpfs_icicle/Kconfig | 7 +++++++
> configs/microchip_mpfs_icicle_defconfig | 1 +
> 2 files changed, 8 insertions(+)
>
> diff --git a/board/microchip/mpfs_icicle/Kconfig b/board/microchip/mpfs_icicle/Kconfig
> index 092e411215..230f96b033 100644
> --- a/board/microchip/mpfs_icicle/Kconfig
> +++ b/board/microchip/mpfs_icicle/Kconfig
> @@ -50,5 +50,12 @@ config BOARD_SPECIFIC_OPTIONS # dummy
> imply CMD_I2C
> imply DM_I2C
> imply SYS_I2C_MICROCHIP
> + imply SPI
> + imply DM_SPI
> + imply MICROCHIP_QSPI
> + imply MTD_SPI_NAND
> + imply CMD_MTD
> + imply MTD_PARTITIONS
> + imply CMD_MTDPARTS
>
> endif
> diff --git a/configs/microchip_mpfs_icicle_defconfig b/configs/microchip_mpfs_icicle_defconfig
> index 6113c5be80..c295b9bad3 100644
> --- a/configs/microchip_mpfs_icicle_defconfig
> +++ b/configs/microchip_mpfs_icicle_defconfig
> @@ -17,6 +17,7 @@ CONFIG_DISPLAY_BOARDINFO=y
> CONFIG_SYS_CBSIZE=256
> CONFIG_SYS_PBSIZE=282
> CONFIG_SYS_BOOTM_LEN=0x4000000
> +CONFIG_SYS_MEM_TOP_HIDE=0x400000
Ah cool, I'd done my patch for our stuff against v2022.01 and this IIRC
was not a "real" config option then. Nice to see that it got "promoted"
to a kconfig option :)
Stuff here LGTM so:
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
> CONFIG_SYS_RELOC_GD_ENV_ADDR=y
> CONFIG_BOOTP_SEND_HOSTNAME=y
> CONFIG_DM_MTD=y
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-10-19 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 14:53 [PATCH 0/4] Update Microchip PolarFire SoC Padmarao Begari
2022-10-19 14:53 ` [PATCH 1/4] riscv: dts: update memory configuration Padmarao Begari
2022-10-19 15:57 ` Conor Dooley
2022-10-20 5:20 ` Padmarao.Begari
2022-10-19 14:53 ` [PATCH 2/4] riscv: dts: Add QSPI NAND device node Padmarao Begari
2022-10-19 15:28 ` Tudor.Ambarus
2022-10-20 5:22 ` Padmarao.Begari
2022-10-19 15:59 ` Conor Dooley
2022-10-20 5:24 ` Padmarao.Begari
2022-10-19 14:53 ` [PATCH 3/4] riscv: Update Microchip MPFS Icicle Kit support Padmarao Begari
2022-10-19 16:09 ` Conor Dooley [this message]
2022-10-19 14:53 ` [PATCH 4/4] spi: Add Microchip PolarFire SoC QSPI driver Padmarao Begari
2022-10-19 15:16 ` Tudor.Ambarus
2022-10-19 15:47 ` Conor Dooley
2022-10-20 5:27 ` Padmarao.Begari
2022-10-19 16:20 ` Conor Dooley
2022-10-20 5:28 ` Padmarao.Begari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y1AhQpde8SbY2VIL@spud \
--to=conor@kernel.org \
--cc=bmeng.cn@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=jagan@amarulasolutions.com \
--cc=nagasuresh.relli@microchip.com \
--cc=padmarao.begari@microchip.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=valentina.fernandezalanis@microchip.com \
--cc=ycliang@andestech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox