From: Vitor Soares <Vitor.Soares@synopsys.com>
To: linux-i3c@lists.infradead.org
Cc: pgaj@cadence.com, Joao.Pinto@synopsys.com,
Vitor Soares <Vitor.Soares@synopsys.com>,
bbrezillon@kernel.org
Subject: [RFC 0/2] Add secondary master
Date: Thu, 28 Nov 2019 02:15:10 +0100 [thread overview]
Message-ID: <cover.1574897246.git.vitor.soares@synopsys.com> (raw)
As agreed I'm sharing with you my secondary master approach based on
[1] and [2]. It is not my goal to use this as alternative solution to
[1] and [2] but to provide you feedback about my challenges. Futher the
following patch should be considered as final work.
During proposal of [1] and [2] I was't able to compile the code directly and
dad need to adjust them to be able to compile dw-i3c-master and found that
they didn'd address my use case.
Apart of what already was done IMO:
- We may have a secondary master struct to embbed master and slave rules.
- Algorithm to define the way masters share bus ownership
- Delay a tranfers when secondary master doesn't bus ownership.
[1] https://patchwork.kernel.org/patch/11011447/
[2] https://patchwork.kernel.org/patch/10846309/
Vitor Soares (2):
i3c: Add prliminary support for secondary master
i3c: dw: add preliminary support for sec master
drivers/i3c/master.c | 365 +++++++++++++++++++++-
drivers/i3c/master/dw-i3c-master.c | 619 +++++++++++++++++++++++++++++++++----
include/linux/i3c/master.h | 39 +++
3 files changed, 959 insertions(+), 64 deletions(-)
--
2.7.4
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2019-11-28 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 1:15 Vitor Soares [this message]
2019-11-28 1:15 ` [RFC 1/2] i3c: Add preliminary support for secondary master Vitor Soares
2019-11-28 5:50 ` Przemyslaw Gaj
2019-11-28 12:20 ` Vitor Soares
2019-11-28 12:58 ` Przemyslaw Gaj
2019-11-28 15:50 ` Vitor Soares
2019-11-28 17:01 ` Przemyslaw Gaj
2019-12-06 8:25 ` Przemyslaw Gaj
2019-11-28 1:15 ` [RFC 2/2] i3c: dw: add preliminary support for sec master Vitor Soares
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=cover.1574897246.git.vitor.soares@synopsys.com \
--to=vitor.soares@synopsys.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bbrezillon@kernel.org \
--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).