Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1652722
| From | Chris Packham <chris.packham@alliedtelesis.co.nz> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH v3 0/3] EDAC: mv64x60: updates |
| Date | 2017-05-29 23:30 +0200 |
| Message-ID | <tMAoG-5Nj-9@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
I'm looking at making use of the mv64x60_edac driver for the armada processors. It appears that at least the DRAM ECC error reporting is the same block from the old Marvell Discovery class of processors. On the ARM side I need to get the error interrupts exposed first before I can send my second set of changes for this driver but this first set is just a series of cleanups. Chris Packham (3): EDAC: mv64x60: check driver registration success EDAC: mv64x60: Fix pdata->name EDAC: mv64x60: replace in_le32/out_le32 with readl/writel drivers/edac/mv64x60_edac.c | 94 +++++++++++++++++++++++---------------------- 1 file changed, 49 insertions(+), 45 deletions(-) -- 2.13.0
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
[PATCH v3 0/3] EDAC: mv64x60: updates Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-29 23:30 +0200
[PATCH v3 1/3] EDAC: mv64x60: check driver registration success Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-29 23:30 +0200
Re: [PATCH v3 1/3] EDAC: mv64x60: check driver registration success Chris Packham <Chris.Packham@alliedtelesis.co.nz> - 2017-06-07 07:40 +0200
Re: [PATCH v3 1/3] EDAC: mv64x60: check driver registration success Borislav Petkov <bp@alien8.de> - 2017-06-07 12:00 +0200
[PATCH v3 3/3] EDAC: mv64x60: replace in_le32/out_le32 with readl/writel Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-29 23:30 +0200
Re: [PATCH v3 0/3] EDAC: mv64x60: updates Borislav Petkov <bp@alien8.de> - 2017-05-30 10:00 +0200
csiph-web