From: Vitor Soares <Vitor.Soares@synopsys.com>
To: Przemyslaw Gaj <pgaj@cadence.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: "linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"bbrezillon@kernel.org" <bbrezillon@kernel.org>,
Vitor Soares <Vitor.Soares@synopsys.com>
Subject: RE: I3C Mastership RFC
Date: Thu, 14 Nov 2019 11:56:00 +0000 [thread overview]
Message-ID: <CH2PR12MB42168DCBB3495AD92E8231D1AE710@CH2PR12MB4216.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20191114061011.GA25288@global.cadence.com>
Hi,
From: Przemyslaw Gaj <pgaj@cadence.com>
Date: Thu, Nov 14, 2019 at 06:10:12
> Hi Vitor,
>
> The 11/12/2019 08:41, Boris Brezillon wrote:
> >
> > Hi Vitor,
> >
> > On Mon, 11 Nov 2019 12:30:45 +0000
> > Vitor Soares <Vitor.Soares@synopsys.com> wrote:
> >
> > > 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.
> >
> > Okay. Would you mind sharing a branch with this material so Przemek and
> > I can have a look at it?
>
> So, Vitor, can you share your changes? Can you tell me what you had to
> change to make it work? Also, which patch version is this based on?
I'm closing a task and after that I will prepare the RFC.
I based in all version and tried to pass everything to master.c file.
Right now my challenge it to trigger mastership request when a device
driver want to access to the bus but I believe we can discuss that after.
Best regards,
Vitor Soares
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2019-11-14 11:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:33 I3C Mastership RFC Przemyslaw Gaj
2019-11-10 10:30 ` Boris Brezillon
2019-11-11 12:30 ` Vitor Soares
2019-11-12 7:41 ` Boris Brezillon
2019-11-14 6:10 ` Przemyslaw Gaj
2019-11-14 11:56 ` Vitor Soares [this message]
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:
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=CH2PR12MB42168DCBB3495AD92E8231D1AE710@CH2PR12MB4216.namprd12.prod.outlook.com \
--to=vitor.soares@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=linux-i3c@lists.infradead.org \
--cc=pgaj@cadence.com \
/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;
as well as URLs for NNTP newsgroup(s).