From: Wolfram Sang <wsa@the-dreams.de>
To: "Adamski,
Krzysztof (Nokia - PL/Wrocław)" <krzysztof.adamski@nokia.com>,
"Peter Rosin" <peda@axentia.se>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: Two separate i2c transfers
Date: Thu, 14 May 2020 16:50:05 +0200 [thread overview]
Message-ID: <20200514145005.GC1589@ninjato> (raw)
In-Reply-To: <5a17ba7b-b1a5-234d-1cae-4e77132bd15d@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
Hi Krzysztof,
On Thu, May 14, 2020 at 02:41:17PM +0200, Adamski, Krzysztof (Nokia - PL/Wrocław) wrote:
Adding Peter as the mux maintainer to CC.
> I have a problem that I think cannot be currently easily addressed by I2C framework in the kernel and I'm seeking for an
> advice on how to approach this. I have an I2C device that can be accessed from two I2C masters connected to I2C bus
> master selector channels. Both masters must do such a sequence before performing long operation:
I need a diagram of that setup. What is the BMS? A chip? Some software?
Can you draw a graph and give names of chips etc...?
And, of course, why on earth do you need to access the same chip from
two masters within one Linux? :) (That's how I understood it)
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-14 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:41 Two separate i2c transfers Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-14 14:50 ` Wolfram Sang [this message]
2020-05-15 7:04 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 7:53 ` Wolfram Sang
2020-05-15 8:51 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 9:20 ` Wolfram Sang
2020-05-15 9:24 ` Peter Rosin
2020-05-15 9:31 ` Wolfram Sang
2020-05-15 9:46 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 8:02 ` Peter Rosin
2020-05-15 8:36 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
2020-05-15 21:19 ` Peter Rosin
2020-05-17 21:32 ` Peter Rosin
2020-05-19 12:59 ` Adamski, Krzysztof (Nokia - PL/Wrocław)
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=20200514145005.GC1589@ninjato \
--to=wsa@the-dreams.de \
--cc=krzysztof.adamski@nokia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.