Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1713325

Re: [RFC 2/5] i3c: Add core I3C infrastructure

From Geert Uytterhoeven <geert@linux-m68k.org>
Newsgroups linux.kernel
Subject Re: [RFC 2/5] i3c: Add core I3C infrastructure
Date 2017-08-16 23:10 +0200
Message-ID <ufdJF-3Is-15@gated-at.bofh.it> (permalink)
References (6 earlier) <u9FfB-4tk-21@gated-at.bofh.it> <u9FyX-4zN-31@gated-at.bofh.it> <u9GbE-52o-31@gated-at.bofh.it> <u9GEF-5cQ-1@gated-at.bofh.it> <u9GY1-5zt-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Aug 1, 2017 at 5:01 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
>> I'm perfectly fine with the I3C / I2C framework separation. The only
>> minor problem I had with that was the inaccuracy of the
>> sysfs/device-model representation: we don't have one i2c and one i3c
>> bus, we just have one i3c bus with a mix of i2c and i3c devices.
>
> I understand that. What if I2C had the same seperation between the "bus"
> and the "master"?

There can be multiple masters on an i2c bus.  But not on an i3c bus, due
to SCL being push/pull.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [RFC 2/5] i3c: Add core I3C infrastructure Geert Uytterhoeven <geert@linux-m68k.org> - 2017-08-16 23:10 +0200
  Re: [RFC 2/5] i3c: Add core I3C infrastructure Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-08-17 09:50 +0200

csiph-web