From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: bcm2835: Include SDHOST in the device tree.
Date: Sat, 27 Feb 2016 21:17:00 +0300 [thread overview]
Message-ID: <56D1E81C.9040003@cogentembedded.com> (raw)
In-Reply-To: <1456527942-3045-4-git-send-email-eric@anholt.net>
Hello.
On 02/27/2016 02:05 AM, Eric Anholt wrote:
> It's disabled by default, and will be enabled by a particular board's
> DT. The DMA channels are also currently left out, because our DMA
> engine support doesn't yet include slave SG, and there doesn't appear
> to be a clean way to include "does slave SG" in the channel
> request/config process.
>
> Signed-off-by: Eric Anholt <eric@anholt.net>
> ---
> arch/arm/boot/dts/bcm283x.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi
> index 597a78f..7b2721b 100644
> --- a/arch/arm/boot/dts/bcm283x.dtsi
> +++ b/arch/arm/boot/dts/bcm283x.dtsi
> @@ -366,6 +366,14 @@
> status = "disabled";
> };
>
> + sdhost: sdhost at 7e202000 {
Please just sd at 7e202000 to better comply with ePAPR.
[...]
MBR, Sergei
next prev parent reply other threads:[~2016-02-27 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 23:05 [PATCH 0/4] bcm2835 SDHOST controller Eric Anholt
2016-02-26 23:05 ` [PATCH 1/4] dt-bindings: Add binding for brcm,bcm2835-sdhost Eric Anholt
2016-03-03 22:02 ` Rob Herring
2016-02-26 23:05 ` [PATCH 2/4] mmc: bcm2835-sdhost: Add new driver for the internal SD controller Eric Anholt
2016-02-26 23:05 ` [PATCH 3/4] ARM: bcm2835: Include SDHOST in the device tree Eric Anholt
2016-02-27 18:17 ` Sergei Shtylyov [this message]
2016-02-26 23:05 ` [PATCH 4/4] ARM: bcm2835: Enable SDHOST by default Eric Anholt
2016-02-29 10:09 ` [PATCH 0/4] bcm2835 SDHOST controller Martin Sperl
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=56D1E81C.9040003@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.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).