From: Corey Minyard <cminyard@mvista.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: f4bug@amsat.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 2/2] i2c/smbus_eeprom: Add feature bit to SPD data
Date: Sun, 18 Jul 2021 13:03:29 -0500 [thread overview]
Message-ID: <20210718180329.GM3431@minyard.net> (raw)
In-Reply-To: <19d42ade295d5297aa624a9eb757b8df18cf64d6.1626367844.git.balaton@eik.bme.hu>
On Thu, Jul 15, 2021 at 06:50:44PM +0200, BALATON Zoltan wrote:
> Add the differential clock input feature bit to the generated SPD
> data. Most guests don't seem to care but pegasos2 firmware version 1.2
> checks for this bit and stops with unsupported module type error if
> it's not present. Since this feature is likely present on real memory
> modules add it in the general code rather than patching the generated
> SPD data in pegasos2 board only.
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
I checked this all out and it looks correct to me. I can take it in my
tree, if necessary. Feature freeze is in two days, so probably not for
6.1, though it could be pushed into there if its needed in 6.1.
Or:
Acked-by: Corey Minyard <cminyard@mvista.com>
if someone else wants to take it. This particular code really doesn't
belong in eeprom.c, I don't think, but I'm not sure where else to put
it. And I can look in the SPD tables as well as anyone :).
corey
> ---
> I've tested it with the firmware of pegasos2, sam460ex, fuloong2e and
> g3beige (latter is not upstream yet) that are the only ones using this
> function currently. Probably this could go in via PPC tree with my
> other pegasos2 fix if respective maitainers ack this patch.
>
> hw/i2c/smbus_eeprom.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/i2c/smbus_eeprom.c b/hw/i2c/smbus_eeprom.c
> index 4d2bf99207..12c5741f38 100644
> --- a/hw/i2c/smbus_eeprom.c
> +++ b/hw/i2c/smbus_eeprom.c
> @@ -276,7 +276,7 @@ uint8_t *spd_data_generate(enum sdram_type type, ram_addr_t ram_size)
> spd[18] = 12; /* ~CAS latencies supported */
> spd[19] = (type == DDR2 ? 0 : 1); /* reserved / ~CS latencies supported */
> spd[20] = 2; /* DIMM type / ~WE latencies */
> - /* module features */
> + spd[21] = (type < DDR2 ? 0x20 : 0); /* module features */
> /* memory chip features */
> spd[23] = 0x12; /* clock cycle time @ medium CAS latency */
> /* data access time */
> --
> 2.21.4
>
next prev parent reply other threads:[~2021-07-18 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 16:50 [PATCH 0/2] Misc pegasos2 fixes BALATON Zoltan
2021-07-15 16:50 ` [PATCH 2/2] i2c/smbus_eeprom: Add feature bit to SPD data BALATON Zoltan
2021-07-18 6:24 ` David Gibson
2021-07-18 16:56 ` BALATON Zoltan
2021-07-18 18:03 ` Corey Minyard [this message]
2021-07-18 20:39 ` BALATON Zoltan
2021-07-19 2:14 ` David Gibson
2021-07-15 16:50 ` [PATCH 1/2] ppc/pegasos2: Fix spurious warning with -bios BALATON Zoltan
2021-07-18 6:24 ` David Gibson
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=20210718180329.GM3431@minyard.net \
--to=cminyard@mvista.com \
--cc=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).