From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: alexandre.belloni@bootlin.com, conor.culhane@silvaco.com,
imx@lists.linux.dev, joe@perches.com,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
zbigniew.lukwinski@linux.intel.com
Subject: Re: [PATCH v4 2/6] i3c: master: svc: add hot join support
Date: Thu, 30 Nov 2023 11:16:36 +0100 [thread overview]
Message-ID: <20231130111636.34432d30@xps-13> (raw)
In-Reply-To: <20231129221225.387952-3-Frank.Li@nxp.com>
Hi Frank,
Frank.Li@nxp.com wrote on Wed, 29 Nov 2023 17:12:21 -0500:
> Add hot join support for svc master controller. Enable hot join defaultly.
by default
> User can use sys entry to disable hot join.
Should we do the opposite? Disable hot-join by default and allow
enabling it?
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> drivers/i3c/master/svc-i3c-master.c | 58 +++++++++++++++++++++++++++--
> 1 file changed, 54 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i3c/master/svc-i3c-master.c b/drivers/i3c/master/svc-i3c-master.c
> index 6b6bdd163af4f..880c6ae76c013 100644
> --- a/drivers/i3c/master/svc-i3c-master.c
> +++ b/drivers/i3c/master/svc-i3c-master.c
> @@ -128,6 +128,9 @@
> /* This parameter depends on the implementation and may be tuned */
> #define SVC_I3C_FIFO_SIZE 16
>
> +#define SVC_I3C_EVENT_IBI BIT(0)
> +#define SVC_I3C_EVENT_HOTJOIN BIT(1)
> +
> struct svc_i3c_cmd {
> u8 addr;
> bool rnw;
> @@ -176,6 +179,7 @@ struct svc_i3c_regs_save {
> * @ibi.tbq_slot: To be queued IBI slot
> * @ibi.lock: IBI lock
> * @lock: Transfer lock, protect between IBI work thread and callbacks from master
> + * @enabled_events: Bit masks for enable events (IBI, HotJoin).
> */
> struct svc_i3c_master {
> struct i3c_master_controller base;
> @@ -205,6 +209,7 @@ struct svc_i3c_master {
> spinlock_t lock;
> } ibi;
> struct mutex lock;
> + int enabled_events;
> };
>
> /**
> @@ -428,13 +433,16 @@ static void svc_i3c_master_ibi_work(struct work_struct *work)
> switch (ibitype) {
> case SVC_I3C_MSTATUS_IBITYPE_IBI:
> dev = svc_i3c_master_dev_from_addr(master, ibiaddr);
> - if (!dev)
> + if (!dev || !(master->enabled_events & SVC_I3C_EVENT_IBI))
If we are going to add new events like that maybe we should have a
helper. So we can then extend the helper with the list of enabled
events?
> svc_i3c_master_nack_ibi(master);
> else
> svc_i3c_master_handle_ibi(master, dev);
> break;
> case SVC_I3C_MSTATUS_IBITYPE_HOT_JOIN:
> - svc_i3c_master_ack_ibi(master, false);
> + if (master->enabled_events & SVC_I3C_EVENT_HOTJOIN)
And you could reuse the helper here
> + svc_i3c_master_ack_ibi(master, false);
> + else
> + svc_i3c_master_nack_ibi(master);
> break;
> case SVC_I3C_MSTATUS_IBITYPE_MASTER_REQUEST:
> svc_i3c_master_nack_ibi(master);
> @@ -471,7 +479,9 @@ static void svc_i3c_master_ibi_work(struct work_struct *work)
> svc_i3c_master_emit_stop(master);
> break;
> case SVC_I3C_MSTATUS_IBITYPE_HOT_JOIN:
> - queue_work(master->base.wq, &master->hj_work);
> + svc_i3c_master_emit_stop(master);
> + if (master->enabled_events & SVC_I3C_EVENT_HOTJOIN)
and here
> + queue_work(master->base.wq, &master->hj_work);
> break;
Thanks,
Miquèl
next prev parent reply other threads:[~2023-11-30 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 22:12 [PATCH v4 0/6] i3c: master: some improvment for i3c master Frank Li
2023-11-29 22:12 ` [PATCH v4 1/6] i3c: master: add enable(disable) hot join in sys entry Frank Li
2023-11-30 10:13 ` Miquel Raynal
2023-11-29 22:12 ` [PATCH v4 2/6] i3c: master: svc: add hot join support Frank Li
2023-11-30 10:16 ` Miquel Raynal [this message]
2023-11-29 22:12 ` [PATCH v4 3/6] i3c: add actual_len in i3c_priv_xfer Frank Li
2023-11-30 10:17 ` Miquel Raynal
2023-11-29 22:12 ` [PATCH v4 4/6] i3c: svc: rename read_len as actual_len Frank Li
2023-11-29 22:12 ` [PATCH v4 5/6] i3c: master: svc return actual transfer data len Frank Li
2023-11-30 10:09 ` Miquel Raynal
2023-11-29 22:12 ` [PATCH v4 6/6] i3c: add API i3c_dev_gettstatus_format1() to get target device status Frank Li
2023-11-30 10:19 ` Miquel Raynal
2023-11-30 17:49 ` Frank Li
2023-11-30 19:16 ` Miquel Raynal
2023-11-30 22:00 ` [PATCH v4 6/6] i3c: add API i3c_dev_gettstatus_format1() to get target device statusy Frank Li
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=20231130111636.34432d30@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=imx@lists.linux.dev \
--cc=joe@perches.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zbigniew.lukwinski@linux.intel.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