linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Jeremy Linton <jeremy.linton@arm.com>, linux-mmc@vger.kernel.org
Cc: bcm-kernel-feedback-list@broadcom.com, sbranden@broadcom.com,
	rjui@broadcom.com, ulf.hansson@linaro.org,
	adrian.hunter@intel.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, f.fainelli@gmail.com
Subject: Re: [PATCH] mmc: sdhci-iproc: Add ACPI bindings for the rpi4
Date: Fri, 8 Jan 2021 13:27:21 -0800	[thread overview]
Message-ID: <1d4a4c55-59dc-b81d-3e92-7cdc036b789c@gmail.com> (raw)
In-Reply-To: <20210108211339.1724769-1-jeremy.linton@arm.com>



On 1/8/2021 1:13 PM, Jeremy Linton wrote:
> The rpi4 has a Arasan controller it carries over
> from the rpi3, and a newer eMMC2 controller.
> Because of a couple "quirks" it seems wiser to bind
> these controllers to the same driver that DT is using
> on this platform rather than the generic sdhci_acpi
> driver with PNP0D40.
> 
> So, we use BCM2847 for the older Arasan and BRCME88C
> for the newer eMMC2.
> 
> With this change linux is capable of utilizing the
> SD card slot, and the wifi on this platform
> with linux.
> 
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>

As far as ACPI ID's go:

Acked-by: Florian Fainelli <f.fainelli@gmail.com>
-- 
Florian

  reply	other threads:[~2021-01-08 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 21:13 [PATCH] mmc: sdhci-iproc: Add ACPI bindings for the rpi4 Jeremy Linton
2021-01-08 21:27 ` Florian Fainelli [this message]
2021-01-09  1:10 ` kernel test robot
2021-01-09  3:18   ` Jeremy Linton
2021-01-09 11:07 ` Stefan Wahren
2021-01-11  3:39   ` Jeremy Linton
2021-01-11  8:45     ` Ard Biesheuvel
2021-01-11 12:23     ` Stefan Wahren
2021-01-11 21:43       ` Jeremy Linton

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=1d4a4c55-59dc-b81d-3e92-7cdc036b789c@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=jeremy.linton@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=ulf.hansson@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).