From: Przemyslaw Gaj <pgaj@cadence.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: "linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"bbrezillon@kernel.org" <bbrezillon@kernel.org>,
rafalc@cadence.com, Vitor Soares <Vitor.Soares@synopsys.com>
Subject: Re: I3C Mastership RFC
Date: Thu, 14 Nov 2019 13:59:51 +0100 [thread overview]
Message-ID: <20191114125950.GB13588@global.cadence.com> (raw)
In-Reply-To: <20191114133214.0b6ecc0a@collabora.com>
Hi,
+Rafal
The 11/14/2019 13:32, Boris Brezillon wrote:
>
> Hi Vitor,
>
> On Thu, 14 Nov 2019 11:56:00 +0000
> Vitor Soares <Vitor.Soares@synopsys.com> wrote:
>
> > 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.
>
> Okay, can we have an estimate? Are we talking about days or weeks?
>
> >
> > I based in all version and tried to pass everything to master.c file.
>
> I'm not sure what that means, but okay.
>
> > 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.
>
> That's kind of a basic feature when talking about mastership handover,
> but sure, we can discuss it after your RFC has been posted.
>
> Note that I'm not super happy to have to go back to square 1 and throw
> away all of the work done by Przemek, especially since Przemek was the
> first one to post a patchset and he never really said he didn't
> want or didn't have time to continue working on this task (not even
> mentioning the time I spent reviewing those patches...).
>
> If Przemek is fine with this situation I'm okay making an exception,
> but be aware that it's not how we usually do: the person that posts a
> patchset first leads the thing (of course, it's even better if there's
> some kind of coordination before the patch is posted).
It depends when you are able to post it. If it's this or next week,
I'm ok. But otherwise, I have to start working on that now. I'm trying
to address your comments from my latest patch, having in mind HCI
implementation. As I said before, our customer is pushing. They have
boards with our hardware and they started using that. Please let me
know.
>
> BTW, you mentioned working on a lot of different topics, but most of
> them were left unfinished (userspace i3cdev interface, I3C slave
> framework/API, ...). Any plans to post RFCs on those aspects anytime
> soon? I mean, there's plenty of topics to work on, and I'd really prefer
> that each developer work on a different topic instead of duplicating the
> effort...
>
> Regards,
>
> Boris
--
--
Przemyslaw Gaj
_______________________________________________
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 13:00 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
2019-11-14 12:32 ` Boris Brezillon
2019-11-14 12:59 ` Przemyslaw Gaj [this message]
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=20191114125950.GB13588@global.cadence.com \
--to=pgaj@cadence.com \
--cc=Vitor.Soares@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=linux-i3c@lists.infradead.org \
--cc=rafalc@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).