From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v3] edac: add support for Calxeda highbank memory controller
Date: Wed, 27 Jun 2012 09:13:20 -0300 [thread overview]
Message-ID: <4FEAF8E0.3080307@redhat.com> (raw)
In-Reply-To: <4FE9BCF5.4090109@gmail.com>
Em 26-06-2012 10:45, Rob Herring escreveu:
> Mauro,
>
> On 06/13/2012 12:01 PM, Rob Herring wrote:
>> From: Rob Herring <rob.herring@calxeda.com>
>>
>> Add support for memory controller on Calxeda Highbank platforms. Highbank
>> platforms support a single 4GB mini-DIMM with 1-bit correction and 2-bit
>> detection.
>>
>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>> ---
>> v3: fix compile when EDAC_DEBUG is disabled
>
> Ping. linux-next is broken for highbank without this fix.
Patch replaced and merged on my trees (with a minor change, see below).
-next should likely get the fix tomorrow.
Thanks,
Mauro.
>> .../devicetree/bindings/arm/calxeda/mem-ctrlr.txt | 17 ++
>> arch/arm/boot/dts/highbank.dts | 6 +
>> drivers/edac/Kconfig | 9 +-
>> drivers/edac/Makefile | 2 +
>> drivers/edac/highbank_mc_edac.c | 264 ++++++++++++++++++++
>> 5 files changed, 297 insertions(+), 1 deletion(-)
>> create mode 100644 Documentation/devicetree/bindings/arm/calxeda/mem-ctrlr.txt
>> create mode 100644 drivers/edac/highbank_mc_edac.c
>>
>> diff --git a/Documentation/devicetree/bindings/arm/calxeda/mem-ctrlr.txt b/Documentation/devicetree/bindings/arm/calxeda/mem-ctrlr.txt
>> new file mode 100644
>> index 0000000..5c74a0b
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/calxeda/mem-ctrlr.txt
>> @@ -0,0 +1,17 @@
>> +Calxeda DDR memory controller
>> +
>> +Properties:
>> +- compatible : Should be "calxeda,hb-ddr-ctrl"
>> +- reg : Address and size for DDR controller registers.
>> +- interrupts : Interrupt for DDR controller.
>> +
>> +Example:
>> +
>> + memory-controller@fff00000 {
>> + compatible = "calxeda,hb-ddr-ctrl";
>> + reg = <0xfff00000 0x1000>;
>> + interrupts = <0 91 4>;
>> + };
>> +
>> +
>> +
There are some extra blank likes at the end of this file. I removed them.
next prev parent reply other threads:[~2012-06-27 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 2:32 [PATCH v2 0/3] EDAC support for Calxeda Highbank Rob Herring
2012-06-12 2:32 ` Rob Herring
[not found] ` <1339468334-9927-1-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-06-12 2:32 ` [PATCH 1/3] edac: create top-level debugfs directory Rob Herring
2012-06-12 2:32 ` Rob Herring
2012-06-12 2:32 ` [PATCH v2 2/3] edac: add support for Calxeda highbank memory controller Rob Herring
2012-06-12 2:32 ` Rob Herring
2012-06-13 17:01 ` [PATCH v3] " Rob Herring
2012-06-26 13:45 ` Rob Herring
2012-06-27 12:13 ` Mauro Carvalho Chehab [this message]
2012-06-12 2:32 ` [PATCH v2 3/3] edac: add support for Calxeda highbank L2 cache ecc Rob Herring
2012-06-12 2:32 ` Rob Herring
2012-06-12 13:24 ` [PATCH v2 0/3] EDAC support for Calxeda Highbank Mauro Carvalho Chehab
[not found] ` <4FD7430B.6010005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-06-13 14:57 ` Rob Herring
2012-06-13 14:57 ` Rob Herring
2012-06-13 15:36 ` Mauro Carvalho Chehab
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=4FEAF8E0.3080307@redhat.com \
--to=mchehab@redhat.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robherring2@gmail.com \
/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.