From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] dt: bindings: add bcm2835-memory-controller documentation
Date: Mon, 16 May 2016 11:04:17 -0500 [thread overview]
Message-ID: <20160516160417.GA1278@rob-hp-laptop> (raw)
In-Reply-To: <1463056732-5607-2-git-send-email-kernel@martin.sperl.org>
On Thu, May 12, 2016 at 12:38:49PM +0000, kernel at martin.sperl.org wrote:
> From: Martin Sperl <kernel@martin.sperl.org>
>
> Add memory controller dt-binding documentation for the
> bcm2835 soc.
>
> Signed-off-by: Martin Sperl <kernel@martin.sperl.org>
> ---
> .../bindings/memory-controllers/brcm,bcm2835-sdram.txt | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/memory-controllers/brcm,bcm2835-sdram.txt
I'd suspect a DDR controller has more than one clock, but otherwise
looks fine. And this binding is pretty much independent of the
discussion for this series.
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-05-16 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 12:38 [PATCH 0/4] add minimal bcm2835-sdram driver kernel at martin.sperl.org
2016-05-12 12:38 ` [PATCH 1/4] dt: bindings: add bcm2835-memory-controller documentation kernel at martin.sperl.org
2016-05-16 16:04 ` Rob Herring [this message]
2016-05-12 12:38 ` [PATCH 2/4] memory: bcm2835: add bcm2835-memory controller kernel at martin.sperl.org
2016-05-12 12:38 ` [PATCH 3/4] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt kernel at martin.sperl.org
2016-05-12 14:56 ` Stefan Wahren
2016-05-12 16:00 ` Martin Sperl
2016-05-12 12:38 ` [PATCH 4/4] ARM: bcm2835_defconfig: add bcm2835-sdram controller kernel at martin.sperl.org
2016-05-12 14:50 ` [PATCH 0/4] add minimal bcm2835-sdram driver Stefan Wahren
2016-05-12 15:28 ` Martin Sperl
2016-05-12 15:55 ` Stefan Wahren
2016-05-12 16:03 ` Martin Sperl
2016-05-12 18:15 ` Eric Anholt
2016-05-12 19:46 ` 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=20160516160417.GA1278@rob-hp-laptop \
--to=robh@kernel.org \
--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