U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: Eoin Dickson <Eoin.Dickson@microchip.com>
Cc: <u-boot@lists.denx.de>, <rick@andestech.com>,
	<conor.dooley@microchip.com>, <jamie.gibbons@microchip.com>,
	<praveen.kumar@microchip.com>, <cyril.jean@microchip.com>,
	<jagan@amarulasolutions.com>
Subject: Re: [PATCH v1 3/4] configs: beaglev_fire: Enable GPIO and MMC_SPI
Date: Mon, 2 Jun 2025 17:14:53 +0800	[thread overview]
Message-ID: <aD1rjeUa0zC8o9Ua@swlinux02> (raw)
In-Reply-To: <20250522141002.1212408-4-Eoin.Dickson@microchip.com>

Hi Eoin,

On Thu, May 22, 2025 at 07:40:01PM +0530, Eoin Dickson wrote:
> [EXTERNAL MAIL]
> 
> From: Eoin Dickson <eoin.dickson@microchip.com>
> 
> Enable CONFIG_MPFS_GPIO, CONFIG_CMD_GPIO and CONFIG_DM_GPIO and
> CONFIG_MMC_SPI in the beaglev_fire_defconfig.
> 
> Signed-off-by: Eoin Dickson <eoin.dickson@microchip.com>
> ---
>  configs/beaglev_fire_defconfig | 4 ++++
>  1 file changed, 4 insertions(+)

configs/beaglev_fire_defconfig does not exist in upstream repo yet.
Is this config a out-of-tree config?

Best regards,
Leo

  reply	other threads:[~2025-06-02  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 14:09 [PATCH v1 0/4] Add SD card support to the Beagle-V-Fire Eoin Dickson
2025-05-22 14:09 ` [PATCH v1 1/4] gpio: add PolarFire SoC GPIO and Core GPIO driver Eoin Dickson
2025-05-22 14:10 ` [PATCH v1 2/4] spi: coreqspi: add xfer function for PolarFire SoC Eoin Dickson
2025-05-22 14:10 ` [PATCH v1 3/4] configs: beaglev_fire: Enable GPIO and MMC_SPI Eoin Dickson
2025-06-02  9:14   ` Leo Liang [this message]
2025-05-22 14:10 ` [PATCH v1 4/4] riscv: dts: microchip: enable gpio banks in Beagle-V Fire Eoin Dickson
2025-05-22 14:38 ` [PATCH v1 0/4] Add SD card support to the Beagle-V-Fire Conor.Dooley
2025-05-22 20:15   ` Robert Nelson

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=aD1rjeUa0zC8o9Ua@swlinux02 \
    --to=ycliang@andestech.com \
    --cc=Eoin.Dickson@microchip.com \
    --cc=conor.dooley@microchip.com \
    --cc=cyril.jean@microchip.com \
    --cc=jagan@amarulasolutions.com \
    --cc=jamie.gibbons@microchip.com \
    --cc=praveen.kumar@microchip.com \
    --cc=rick@andestech.com \
    --cc=u-boot@lists.denx.de \
    /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