From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, Jean Delvare <khali@linux-fr.org>,
Guenter Roeck <linux@roeck-us.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Rui Wang <ruiv.wang@gmail.com>
Subject: Re: [PATCH v6 4/4] i2c, i2c_imc: Add DIMM bus code
Date: Fri, 21 Feb 2014 15:32:39 +0000 [thread overview]
Message-ID: <20140221153239.20dbb8c2@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <CALCETrWEexCqH5486Qfyt22i5+MZjpETJEMTyg6FO6xOwXuraQ@mail.gmail.com>
> I'm suggesting identifying a range of addresses on a bus with a "port"
> (or whatever it should be called). Multiple ports could claim
> non-overlapping ranges on the same bus.
Which is fine until you meant a mux or a device that can be moved about
by writing to it, or has a wide range of addresses determined by
strapping.
> In this particular case (Intel LGA2011 systems), there's only one sane
> way to wire up the busses, since the memory controller *is* the smbus
> master. According to the JEDEC spec, each DIMM slot is has three pins
Ok that helps a lot for the specific case, and you have at least in
theory got a flag between the OS and BIOS to avoid things like SMM
throwing parties on the smbus while you are using it.
next prev parent reply other threads:[~2014-02-21 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 1:45 [PATCH v6 0/4] iMC SMBUS driver and DIMM bus probing Andy Lutomirski
2013-12-21 1:45 ` [PATCH v6 1/4] Move Intel SNB device ids from sb_edac to pci_ids.h Andy Lutomirski
2013-12-21 1:45 ` [PATCH v6 2/4] sb_edac: Claim a different PCI device Andy Lutomirski
2013-12-21 1:45 ` [PATCH v6 3/4] i2c_imc: New driver for Intel's iMC, found on LGA2011 chips Andy Lutomirski
2014-02-19 15:38 ` Wolfram Sang
2014-02-19 17:10 ` Andy Lutomirski
2013-12-21 1:45 ` [PATCH v6 4/4] i2c, i2c_imc: Add DIMM bus code Andy Lutomirski
2014-02-19 15:16 ` Wolfram Sang
2014-02-19 17:30 ` Andy Lutomirski
2014-02-19 18:51 ` Mauro Carvalho Chehab
2014-02-19 19:03 ` Luck, Tony
2014-02-20 1:39 ` Andy Lutomirski
2014-02-20 16:42 ` Luck, Tony
2014-02-20 23:43 ` Andy Lutomirski
2014-02-28 19:15 ` Mauro Carvalho Chehab
2014-02-28 20:14 ` Andy Lutomirski
2014-02-19 19:26 ` One Thousand Gnomes
2014-02-20 1:30 ` Andy Lutomirski
2014-02-21 15:32 ` One Thousand Gnomes [this message]
2014-02-25 19:54 ` Andy Lutomirski
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=20140221153239.20dbb8c2@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luto@amacapital.net \
--cc=m.chehab@samsung.com \
--cc=ruiv.wang@gmail.com \
--cc=wsa@the-dreams.de \
/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