Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1673076
| From | Chris Packham <Chris.Packham@alliedtelesis.co.nz> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs |
| Date | 2017-06-22 23:50 +0200 |
| Message-ID | <tVi9c-1Mr-15@gated-at.bofh.it> (permalink) |
| References | <tPX5n-7J4-3@gated-at.bofh.it> <tPX5o-7J4-11@gated-at.bofh.it> <tQrZw-1Zf-3@gated-at.bofh.it> <tVb7H-5Qr-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 23/06/17 02:37, Jan Lübbe wrote:
> 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)
For the integrated version it still is just half and full but half == 16
and full == 32.
> - 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
This definition is the same for the integrated version.
> 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.
I think we do need to use the compatible string to decide how to
interpret full/half.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs Jan Lübbe <jlu@pengutronix.de> - 2017-06-22 16:20 +0200 Re: [RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs Chris Packham <Chris.Packham@alliedtelesis.co.nz> - 2017-06-22 23:50 +0200
csiph-web