From: Rob Herring <robherring2@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Doug Thompson <dougthompson@xmission.com>,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH 1/2] edac: add support for Calxeda highbank memory controller
Date: Thu, 07 Jun 2012 20:12:51 -0500 [thread overview]
Message-ID: <4FD15193.8080800@gmail.com> (raw)
In-Reply-To: <4FCFDB12.3090403@redhat.com>
Mauro,
On 06/06/2012 05:34 PM, Mauro Carvalho Chehab wrote:
> Hi Rob,
>
> Em 06-06-2012 19:02, Rob Herring escreveu:
>> 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>
>> ---
>> .../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 | 238 ++++++++++++++++++++
>> 5 files changed, 271 insertions(+), 1 deletion(-)
>> create mode 100644 Documentation/devicetree/bindings/arm/calxeda/mem-ctrlr.txt
>> create mode 100644 drivers/edac/highbank_mc_edac.c
[snip]
>> +
>> +static struct mcidev_sysfs_attribute highbank_mc_sysfs_attributes[] = {
>> + {
>> + .attr = {
>> + .name = "inject_ctrl",
>> + .mode = (S_IRUGO | S_IWUSR)
>> + },
>> + .store = highbank_mc_inject_ctrl_store,
>> + },
>> + {
>> + .attr = {.name = NULL} /* End of list */
>> + }
>> +};
>
> This won't work after the kobj->struct device conversion patches that are at
> -next tree, as this struct will not exist anymore.
>
> Also, as this is for error injection, the better is to use debugfs.
>
> It shouldn't be hard to change it to use debugfs. If you want an example, you
> can take a look on this patch:
>
> http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-edac.git;a=commitdiff;h=303f3e2113d81d49feef9c0803c2958d41513f14
>
I've got this working, but don't really like the resulting debugfs
layout. I end-up with something like this (using dev_name() of platform
driver):
/mc0/fake*
/fff00000.memory-controller/inject_ctrl
It would be nice if there was a top level edac directory and any entries
I add are added under mcX. I can do that for the next version if that's
okay.
Rob
next prev parent reply other threads:[~2012-06-08 1:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 22:02 [PATCH 0/2] EDAC support for Calxeda Highbank Rob Herring
2012-06-06 22:02 ` [PATCH 1/2] edac: add support for Calxeda highbank memory controller Rob Herring
2012-06-06 22:34 ` Mauro Carvalho Chehab
2012-06-06 22:56 ` Rob Herring
2012-06-07 12:43 ` Borislav Petkov
2012-06-07 12:44 ` Borislav Petkov
2012-06-11 15:22 ` Mauro Carvalho Chehab
2012-06-08 1:12 ` Rob Herring [this message]
2012-06-11 15:25 ` Mauro Carvalho Chehab
2012-06-06 22:02 ` [PATCH 2/2] edac: add support for Calxeda highbank L2 cache ecc Rob Herring
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=4FD15193.8080800@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rob.herring@calxeda.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 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).