From: Clark Wang <xiaoning.wang@nxp.com>
To: miquel.raynal@bootlin.com, conor.culhane@silvaco.com,
alexandre.belloni@bootlin.com
Cc: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: [PATCH V4 0/8] i3c: master: svc: some bug fixes and add runtime pm support
Date: Mon, 9 Aug 2021 14:36:37 +0800 [thread overview]
Message-ID: <20210809063645.2289988-1-xiaoning.wang@nxp.com> (raw)
Hi,
V4 changes:
- New patches:
- i3c: master: svc: separate err, fifo and disable interrupt of reset function
- i3c: master: svc: add the missing module device table
- i3c: master: svc: enable the interrupt in the enable ibi function
- i3c: master: svc: add support for slave to stop returning data
- Only use COMPLETE flag in the read function.
- Add a reset before each transfer.
- i3c: master: svc: add runtime pm support
- error path emit_stop only used in svc_i3c_master_do_daa() for one time, so
remove it. Or it needs another goto command at the end of the function to
skip it and to go to rpm_out.
V3 changes:
- i3c: master: svc: add runtime pm support:
- restore the error path of probe function
- enable runtime pm just before i3c module reset
V2 changes:
- align the parameters of the function in the second patch
- add a new patch to support runtime PM.
Clark Wang (8):
i3c: master: svc: move module reset behind clk enable
i3c: master: svc: fix atomic issue
i3c: master: svc: separate err, fifo and disable interrupt of reset
function
i3c: master: svc: add support for slave to stop returning data
i3c: master: svc: set ODSTOP to let I2C device see the STOP signal
i3c: master: svc: add runtime pm support
i3c: master: svc: add the missing module device table
i3c: master: svc: enable the interrupt in the enable ibi function
drivers/i3c/master/svc-i3c-master.c | 307 +++++++++++++++++++++-------
1 file changed, 231 insertions(+), 76 deletions(-)
--
2.25.1
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2021-08-09 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 6:36 Clark Wang [this message]
2021-08-09 6:36 ` [PATCH V4 1/8] i3c: master: svc: move module reset behind clk enable Clark Wang
2021-08-09 6:36 ` [PATCH V4 2/8] i3c: master: svc: fix atomic issue Clark Wang
2021-08-09 6:36 ` [PATCH V4 3/8] i3c: master: svc: separate err, fifo and disable interrupt of reset function Clark Wang
2021-08-16 6:52 ` Miquel Raynal
2021-08-09 6:36 ` [PATCH V4 4/8] i3c: master: svc: add support for slave to stop returning data Clark Wang
2021-08-16 7:15 ` Miquel Raynal
2021-08-09 6:36 ` [PATCH V4 5/8] i3c: master: svc: set ODSTOP to let I2C device see the STOP signal Clark Wang
2021-08-09 6:36 ` [PATCH V4 6/8] i3c: master: svc: add runtime pm support Clark Wang
2021-08-16 6:59 ` Miquel Raynal
2021-08-09 6:36 ` [PATCH V4 7/8] i3c: master: svc: add the missing module device table Clark Wang
2021-08-16 7:00 ` Miquel Raynal
2021-08-09 6:36 ` [PATCH V4 8/8] i3c: master: svc: enable the interrupt in the enable ibi function Clark Wang
2021-08-16 7:02 ` Miquel Raynal
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=20210809063645.2289988-1-xiaoning.wang@nxp.com \
--to=xiaoning.wang@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.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 read-only IMAP folder(s) and NNTP newsgroup(s).