public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Conor Culhane <conor.culhane@silvaco.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Clark Wang <xiaoning.wang@nxp.com>,
	"moderated list:SILVACO I3C DUAL-ROLE MASTER"
	<linux-i3c@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	imx@lists.linux.dev
Subject: Re: [PATCH 1/1] i3c: master: svc: Modify enabled_events bit 7:0 to act as IBI enable counter
Date: Fri, 25 Oct 2024 16:10:20 +0200	[thread overview]
Message-ID: <20241025161020.11765f79@xps-13> (raw)
In-Reply-To: <ZxukksXwyWN2HQ3I@lizhi-Precision-Tower-5810>

Hi Frank,

Frank.li@nxp.com wrote on Fri, 25 Oct 2024 10:00:50 -0400:

> On Fri, Oct 25, 2024 at 09:53:18AM +0200, Miquel Raynal wrote:
> > Hi Frank,
> >
> > Frank.Li@nxp.com wrote on Thu, 24 Oct 2024 16:38:55 -0400:
> >  
> > > Fix issue where disabling IBI on one device disables the entire IBI
> > > interrupt. Modify bit 7:0 of enabled_events to serve as an IBI enable  
> >
> > Is this bitfield arbitrary?
> >
> > Is there a rationale behind it?  
> 
> Max devices number under a I3C bus is 128 because dynamic address is 7 bit.
> So 8 bits for it should be enough.
> 
> Bit31 as hotjoin, Bit30 reserved as control switch request.

Makes sense.

Thanks,
Miquèl

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2024-10-25 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 20:38 [PATCH 1/1] i3c: master: svc: Modify enabled_events bit 7:0 to act as IBI enable counter Frank Li
2024-10-25  7:53 ` Miquel Raynal
2024-10-25 14:00   ` Frank Li
2024-10-25 14:10     ` Miquel Raynal [this message]
2024-10-31 23:05 ` Alexandre Belloni

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=20241025161020.11765f79@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=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiaoning.wang@nxp.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