From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-V2 1/6] dt: bindings: add bcm2835-memory-controller documentation
Date: Fri, 20 May 2016 14:16:45 -0500 [thread overview]
Message-ID: <20160520191645.GA14779@rob-hp-laptop> (raw)
In-Reply-To: <1463586030-2778-2-git-send-email-kernel@martin.sperl.org>
On Wed, May 18, 2016 at 03:40:25PM +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>
>
> Changelog:
> V2 -> V3: added additional clock
> (for the Controller internal PLL)
> added clock-names
> added additional register ranges for the
> SDRAM Adress and Data PHY
> added reg-names
> ---
> .../memory-controllers/brcm,bcm2835-sdram.txt | 30 ++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/memory-controllers/brcm,bcm2835-sdram.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-05-20 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 15:40 [PATCH-V2 0/6] ARM: memory: bcm: add sdram driver kernel at martin.sperl.org
2016-05-18 15:40 ` [PATCH-V2 1/6] dt: bindings: add bcm2835-memory-controller documentation kernel at martin.sperl.org
2016-05-20 19:16 ` Rob Herring [this message]
2016-05-18 15:40 ` [PATCH-V2 2/6] memory: bcm2835: add bcm2835-memory controller kernel at martin.sperl.org
2016-05-18 15:40 ` [PATCH-V2 3/6] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt kernel at martin.sperl.org
2016-05-18 15:40 ` [PATCH-V2 4/6] ARM: bcm2835_defconfig: add bcm2835-sdram controller kernel at martin.sperl.org
2016-05-18 15:40 ` [PATCH-V2 5/6] ARM: multi_v7_defconfig: bcm2835: add bcm2835-sdram driver kernel at martin.sperl.org
2016-05-18 15:40 ` [PATCH-V2 6/6] memory: bcm2835: expose register ranges via debugfs kernel at martin.sperl.org
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=20160520191645.GA14779@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