Linux-i3c Archive on
 help / color / Atom feed
From: Vitor Soares <>
To: Boris Brezillon <>,
	Przemyslaw Gaj <>
Cc: "" <>,
	"" <>,
	"" <>
Subject: RE: I3C Mastership RFC
Date: Mon, 11 Nov 2019 12:30:45 +0000
Message-ID: <> (raw)
In-Reply-To: <>

Hi Boris and Przemek,

I have a working version for tests purposes. Yet, I have some basic TODOS 
to address during the takeover of the bus.

I don't know if you are aware but the secondary master feature 
description was improved for the spec v1.1 and it makes sense to take a 
look on that.

Regarding the current approach (at least last Patch series and what I 
did) I still don't know if it is the best solution.
I remember in the beginning of secondary master support I discuss with 
Boris about USB OTG vs I2C slave mode and now having a better 
understanding how USB OTG works I think we should address secondary 
master in a similar way. At least for me it seems to be more modular and 
ease to expand.

From: Boris Brezillon <>
Date: Sun, Nov 10, 2019 at 10:30:05

> Hi Przemek,
> On Wed, 6 Nov 2019 10:33:16 +0100
> Przemyslaw Gaj <> wrote:
> > Hi Vitor,
> > 
> > We discussed with Joao in Lyon that you are ready with mastership RFC.
> > The question is when do you think you are able to post this proposal.
> > Our customer needs that and is pushing hard. I would like also to run all
> > the tests in our complex configuration and check how does it work.
> If you need this feature, I'd recommend that you lead the discussion
> (as you did so far) and post a new version. Maybe try to address some of
> the concerns raised by Vitor along the way. I know that you were in
> favor of getting back to one of the previous iteration (discussed
> during ELCE), so please go ahead and do what you think is the more
> appropriate.

I will try to put everything together and send a version so you can take 
a look.

> As part of this work, I'd like you to look at how mastership handover
> is handled in HCI. I'm not asking you to implement an HCI driver, but
> having an idea of what would be done in each of the new hooks would be
> good (and maybe describing that in the cover letter).

We may need another call back for "deliver mastership" because the way 
how controllers do request/deliver may differ.

> Thanks,
> Boris

Apart of all this it necessary to think how request/deliver will take 
place in a functionally system.
  - main master just deliver the ownership to secondary master and expect 
it take care of the bus.
  - secondary master request the ownership and automatically send back 
the ownership to the main master.
  - give a time window in which each master can own the bus.

All this are topics that I'm going discussing with people that are 
working with i3c.

Best regards,
Vitor Soares

linux-i3c mailing list

  reply index

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  9:33 Przemyslaw Gaj
2019-11-10 10:30 ` Boris Brezillon
2019-11-11 12:30   ` Vitor Soares [this message]
2019-11-12  7:41     ` Boris Brezillon
2019-11-14  6:10       ` Przemyslaw Gaj
2019-11-14 11:56         ` Vitor Soares
2019-11-14 12:32           ` Boris Brezillon
2019-11-14 12:59             ` Przemyslaw Gaj
2019-11-14 14:17             ` Vitor Soares
2019-11-14 14:50               ` Boris Brezillon
2019-11-14 20:15                 ` Przemyslaw Gaj
2019-11-25  8:02               ` Przemyslaw Gaj
2019-11-25 11:19                 ` Vitor Soares
2019-11-25 11:34                   ` Boris Brezillon
2019-11-25 11:42                     ` Vitor Soares
2019-11-25 11:55                       ` Przemyslaw Gaj
2019-11-25 12:03                         ` Vitor Soares
2019-11-25 12:22                           ` Boris Brezillon
2019-11-25 13:00                             ` Vitor Soares
2019-11-25 13:09                               ` Boris Brezillon
2019-11-25 14:27                                 ` Vitor Soares
2019-11-25 14:50                                   ` Boris Brezillon
2019-11-25 14:59                                   ` Przemyslaw Gaj
2019-11-25 15:22                                     ` Vitor Soares
2019-11-25 12:25                           ` Przemyslaw Gaj
2019-11-25 12:56                             ` Vitor Soares
2019-11-25 11:50                     ` Przemyslaw Gaj

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-i3c Archive on

Archives are clonable:
	git clone --mirror linux-i3c/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-i3c linux-i3c/ \
	public-inbox-index linux-i3c

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone