public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Wolfram Sang <wsa@kernel.org>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	Jean Delvare <jdelvare@suse.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] eeprom: ee1004: Add support for multiple i2c busses
Date: Tue, 19 Dec 2023 22:40:23 +0100	[thread overview]
Message-ID: <3785ae44-8ced-446a-81a6-8be15bcaa04b@gmail.com> (raw)
In-Reply-To: <f1a216a8-e77c-49f2-8838-561349b30ab8@gmail.com>

On 16.11.2023 15:31, Heiner Kallweit wrote:
> There are systems with more than 8 memory slots where the i2c bus for
> SPD is multiplexed. i2c_register_spd() isn't used yet on such systems,
> but it's planned. So we need to extend ee1004 accordingly.
> With this extension a maximum of 8 i2c busses is supported.
> 
> I don't have such a system for testing, therefore I just verified
> that the driver still works on a system with a single i2c bus.
> 
> For the sake of simplicity the extension uses the existing global
> mutex to protect access on all busses. This could be improved,
> but we support 8 busses only, and SPD data is small and rarely
> accessed, so it shouldn't be a problem.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> v2:
> - simplify code by using i2c_set/get_clientdata
> ---

Patch has been applied by Greg and can be set to "handled elsewhere"
in i2c patchwork.

      reply	other threads:[~2023-12-19 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 14:31 [PATCH v2] eeprom: ee1004: Add support for multiple i2c busses Heiner Kallweit
2023-12-19 21:40 ` Heiner Kallweit [this message]

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=3785ae44-8ced-446a-81a6-8be15bcaa04b@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@kernel.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