All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Samuel Holland <samuel@sholland.org>
Cc: u-boot@lists.denx.de, Jagan Teki <jagan@amarulasolutions.com>,
	Icenowy Zheng <icenowy@aosc.io>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 2/2] mmc: sunxi: Remove unnecessary pinmux option dependency
Date: Tue, 24 May 2022 17:15:01 +0100	[thread overview]
Message-ID: <20220524171501.6e02fa49@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <20220410051335.52093-2-samuel@sholland.org>

On Sun, 10 Apr 2022 00:13:34 -0500
Samuel Holland <samuel@sholland.org> wrote:

> Now that the pinmux conflict is handled in the board code (by skipping
> setup for the one conflicting MMC controller), the driver does not need
> to be entirely disabled based on the UART pinmux.
> 
> Signed-off-by: Samuel Holland <samuel@sholland.org>

Applied to sunxi/master.

Thanks,
Andre

> ---
> 
>  drivers/mmc/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/mmc/Kconfig b/drivers/mmc/Kconfig
> index f04cc44e19..5e2921ce41 100644
> --- a/drivers/mmc/Kconfig
> +++ b/drivers/mmc/Kconfig
> @@ -727,7 +727,7 @@ config ZYNQ_HISPD_BROKEN
>  
>  config MMC_SUNXI
>  	bool "Allwinner sunxi SD/MMC Host Controller support"
> -	depends on ARCH_SUNXI && !UART0_PORT_F
> +	depends on ARCH_SUNXI
>  	default y
>  	help
>  	  This selects support for the SD/MMC Host Controller on


  parent reply	other threads:[~2022-05-24 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10  5:13 [PATCH 1/2] sunxi: Skip MMC0 init when its pinmux conflicts with UART0 Samuel Holland
2022-04-10  5:13 ` [PATCH 2/2] mmc: sunxi: Remove unnecessary pinmux option dependency Samuel Holland
2022-04-11  2:03   ` Peng Fan (OSS)
2022-05-24 16:15   ` Andre Przywara [this message]
2022-04-26 12:58 ` [PATCH 1/2] sunxi: Skip MMC0 init when its pinmux conflicts with UART0 Andre Przywara
2022-05-24 16:14 ` Andre Przywara

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=20220524171501.6e02fa49@donnerap.cambridge.arm.com \
    --to=andre.przywara@arm.com \
    --cc=icenowy@aosc.io \
    --cc=jagan@amarulasolutions.com \
    --cc=jh80.chung@samsung.com \
    --cc=peng.fan@nxp.com \
    --cc=samuel@sholland.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.