From: jlu@pengutronix.de (Jan Lübbe)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs
Date: Thu, 22 Jun 2017 16:11:35 +0200 [thread overview]
Message-ID: <1498140695.2533.76.camel@pengutronix.de> (raw)
In-Reply-To: <1497014062.3536.52.camel@pengutronix.de>
Hi Chris,
On Fr, 2017-06-09 at 15:14 +0200, Jan L?bbe wrote:
> > +static void mvebu_init_csrows(struct mem_ctl_info *mci,
> > + struct mvebu_mc_pdata *pdata)
> [...]
> > + devtype = (ctl >> 20) & 0x3;
> > + switch (devtype) {
> > + case 0x0:
> > + dimm->dtype = DEV_X32;
> > + break;
> > + case 0x2: /* could be X8 too, but no way to tell
> */
> > + dimm->dtype = DEV_X16;
> > + break;
> > + case 0x3:
> > + dimm->dtype = DEV_X4;
> > + break;
> > + default:
> > + dimm->dtype = DEV_UNKNOWN;
> > + break;
> > + }
> This register is documented as reserved? I pulled the X8/X16
> information from the Address Control Register (CSnStruct bits).
Do you have more information on how to decode the Bus width?
It's not clear from the MV78230/78x60 docs:
- The SDRAM Configuration Register, offset 15 bit is:
0 = Half (32 bit data bus)
1 = Full (64 bit data bus)
- The SDRAM Address Control Register, offsets 0-1, 4-5, 8-9 and 12-13
(for CS 0, 1, 3 and 4):
0 = X8
1 = X16
2 and 3 are not documented
Is this clearer in your documentation, so that we can have the same code
handle both variants? Otherwise, we'd probably need separate DT
compatibles.
Regards,
Jan
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2017-06-22 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 4:11 [RFC PATCH 0/4] EDAC support for Marvell Armada SoCs Chris Packham
2017-06-08 4:11 ` [RFC PATCH 1/4] EDAC: mvebu: Add driver " Chris Packham
2017-06-09 10:39 ` Borislav Petkov
2017-06-09 13:14 ` Jan Lübbe
[not found] ` <1497016569.3536.84.camel@pengutronix.de>
2017-06-09 16:13 ` DMA-safety for edac_atomic_scrub on ARM Rob Herring
2017-06-11 22:37 ` [RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs Chris Packham
2017-06-22 14:11 ` Jan Lübbe [this message]
2017-06-22 21:43 ` Chris Packham
2017-06-08 4:11 ` [RFC PATCH 2/4] ARM: l2x0: support parity-enable/disable on aurora Chris Packham
2017-06-08 4:11 ` [RFC PATCH 3/4] ARM: l2x0: add arm,ecc-enable property for aurora Chris Packham
2017-06-09 8:58 ` Jan Lübbe
2017-06-11 22:55 ` [RFC PATCH 3/4] ARM: l2x0: add arm, ecc-enable " Chris Packham
2017-06-22 14:46 ` [RFC PATCH 3/4] ARM: l2x0: add arm,ecc-enable " Jan Lübbe
2017-06-22 21:50 ` [RFC PATCH 3/4] ARM: l2x0: add arm, ecc-enable " Chris Packham
2017-06-09 16:29 ` Rob Herring
2017-06-08 4:11 ` [RFC PATCH 4/4] ARM: dts: enable l2c parity and ecc protection on 98dx3236 Chris Packham
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=1498140695.2533.76.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).