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 0/3] Add data hold delay support
Date: Thu, 14 Nov 2019 06:51:52 +0100 [thread overview]
Message-ID: <20191114055155.20446-1-pgaj@cadence.com> (raw)
Add THD_DEL (Data Hold Delay) support. After testing different scenarios,
on various systems, sometimes there is a need to delay SDA_OUT propagation.
Adding support which allows to configure that delay using the device
tree parameter.
Przemyslaw Gaj (3):
i3c: master: add data hold delay support
dt-bindings: i3c: Document data hold delay feature
MAINTAINERS: add myself as maintainer of Cadence I3C master controller
driver
Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt | 6 ++++++
MAINTAINERS | 6 ++++++
drivers/i3c/master/i3c-master-cdns.c | 5 ++++-
3 files changed, 16 insertions(+), 1 deletion(-)
--
2.14.0
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2019-11-14 5:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 5:51 Przemyslaw Gaj [this message]
2019-11-14 5:51 ` [PATCH 1/3] i3c: master: add data hold delay support Przemyslaw Gaj
2019-11-14 13:38 ` Vitor Soares
2019-11-14 5:51 ` [PATCH 2/3] dt-bindings: i3c: Document data hold delay feature Przemyslaw Gaj
2019-11-14 9:15 ` Boris Brezillon
2019-11-14 9:26 ` Boris Brezillon
2019-11-14 10:54 ` Przemyslaw Gaj
2019-11-14 11:09 ` Boris Brezillon
2019-11-14 11:35 ` Przemyslaw Gaj
2019-11-14 5:51 ` [PATCH 3/3] MAINTAINERS: add myself as maintainer of Cadence I3C master controller driver Przemyslaw Gaj
2019-11-15 5:09 ` Boris Brezillon
2019-11-14 11:58 ` [PATCH 0/3] Add data hold delay support Vitor Soares
2019-11-14 12:48 ` Przemyslaw Gaj
2019-11-14 13:31 ` Vitor Soares
2019-11-14 13:46 ` Boris Brezillon
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=20191114055155.20446-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.