From: Przemyslaw Gaj <pgaj@cadence.com>
To: <bbrezillon@kernel.org>
Cc: linux-i3c@lists.infradead.org, agolec@cadence.com,
Przemyslaw Gaj <pgaj@cadence.com>,
rafalc@cadence.com, vitor.soares@synopsys.com
Subject: [PATCH v6 0/2] Drop support for I2C 10 bit devices from I3C subsystem
Date: Tue, 16 Apr 2019 09:36:13 +0100 [thread overview]
Message-ID: <20190416083615.6894-1-pgaj@cadence.com> (raw)
I3C MIPI spec does not clearly say that I2C 10bit devices are supported.
Additionally, it isn't possible to pass 10 bit device properly through DEFSLVS
command and reserve address for such device on secondary master side.
Main changes between v5 and v6:
- Fix typo in commit message
Main changes between v4 and v5:
- Merge HC driver patches and I3C subsystem into one.
Main changes between v3 and v4:
- Fix changelogs
- Fix patch versioning
- Change order of the patches to make it bisectable.
Przemyslaw Gaj (2):
i3c: Drop support for I2C 10 bit addresing
dt-bindings: i3c: Document dropped support for I2C 10 bit devices
Documentation/devicetree/bindings/i3c/i3c.txt | 4 +++-
drivers/i3c/master.c | 21 ++++++++++++++-------
drivers/i3c/master/dw-i3c-master.c | 6 ------
drivers/i3c/master/i3c-master-cdns.c | 10 +---------
include/linux/i3c/master.h | 5 +----
5 files changed, 19 insertions(+), 27 deletions(-)
--
2.8.3
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2019-04-16 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 8:36 Przemyslaw Gaj [this message]
2019-04-16 8:36 ` [PATCH v6 1/2] i3c: Drop support for I2C 10 bit addresing Przemyslaw Gaj
2019-04-16 8:36 ` [PATCH v6 2/2] dt-bindings: i3c: Document dropped support for I2C 10 bit devices 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=20190416083615.6894-1-pgaj@cadence.com \
--to=pgaj@cadence.com \
--cc=agolec@cadence.com \
--cc=bbrezillon@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=rafalc@cadence.com \
--cc=vitor.soares@synopsys.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).