All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Rajeev Huralikoppi <rajeev.huralikoppi@silvaco.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
	Conor Culhane <conor.culhane@silvaco.com>
Subject: Re: [PATCH 3/4] i3c: master: svc: Add Silvaco I3C master driver
Date: Wed, 5 Aug 2020 17:22:17 +0200	[thread overview]
Message-ID: <20200805172217.27a00af5@xps13> (raw)
In-Reply-To: <nycvar.YSQ.7.77.849.2008051105550.1112668@knanqh.ubzr>

Hi Nicolas,

Nicolas Pitre <nico@fluxnic.net> wrote on Wed, 5 Aug 2020 11:13:41
-0400 (EDT):

> On Tue, 4 Aug 2020, Conor Culhane wrote:
> 
> > Miquel is passing 0 as the delay_us argument.  
> 
> Good point.
> 
> > Is this still a concern?  
> 
> Not in that case.

I will check again if looping over this register read actually
makes sense or not. If yes, I will add a comment here.

Thanks,
Miquèl

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

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Conor Culhane <conor.culhane@silvaco.com>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Rob Herring <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rajeev Huralikoppi <rajeev.huralikoppi@silvaco.com>
Subject: Re: [PATCH 3/4] i3c: master: svc: Add Silvaco I3C master driver
Date: Wed, 5 Aug 2020 17:22:17 +0200	[thread overview]
Message-ID: <20200805172217.27a00af5@xps13> (raw)
In-Reply-To: <nycvar.YSQ.7.77.849.2008051105550.1112668@knanqh.ubzr>

Hi Nicolas,

Nicolas Pitre <nico@fluxnic.net> wrote on Wed, 5 Aug 2020 11:13:41
-0400 (EDT):

> On Tue, 4 Aug 2020, Conor Culhane wrote:
> 
> > Miquel is passing 0 as the delay_us argument.  
> 
> Good point.
> 
> > Is this still a concern?  
> 
> Not in that case.

I will check again if looping over this register read actually
makes sense or not. If yes, I will add a comment here.

Thanks,
Miquèl

  reply	other threads:[~2020-08-05 15:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  8:01 [PATCH 1/4] dt-bindings: Add vendor prefix for Silvaco Miquel Raynal
2020-07-09  8:01 ` Miquel Raynal
2020-07-09  8:01 ` [PATCH 2/4] dt-bindings: i3c: Describe Silvaco master binding Miquel Raynal
2020-07-09  8:01   ` Miquel Raynal
2020-07-09 17:04   ` Rob Herring
2020-07-09 17:04     ` Rob Herring
2020-07-09  8:01 ` [PATCH 3/4] i3c: master: svc: Add Silvaco I3C master driver Miquel Raynal
2020-07-09  8:01   ` Miquel Raynal
2020-07-09 10:02   ` kernel test robot
2020-07-09 10:02     ` kernel test robot
2020-07-09 10:02     ` kernel test robot
2020-07-09 12:58   ` kernel test robot
2020-07-09 12:58     ` kernel test robot
2020-07-09 12:58     ` kernel test robot
2020-08-03 20:20   ` Nicolas Pitre
2020-08-03 20:20     ` Nicolas Pitre
     [not found]     ` <BN6PR16MB1762D6CE430AB08B7A2BE5FCF14A0@BN6PR16MB1762.namprd16.prod.outlook.com>
2020-08-05 15:13       ` Nicolas Pitre
2020-08-05 15:13         ` Nicolas Pitre
2020-08-05 15:22         ` Miquel Raynal [this message]
2020-08-05 15:22           ` Miquel Raynal
2020-07-09  8:01 ` [PATCH 4/4] MAINTAINERS: Add Silvaco I3C master Miquel Raynal
2020-07-09  8:01   ` Miquel Raynal
2020-07-20 22:23 ` [PATCH 1/4] dt-bindings: Add vendor prefix for Silvaco Rob Herring
2020-07-20 22:23   ` Rob Herring

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=20200805172217.27a00af5@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=boris.brezillon@collabora.com \
    --cc=conor.culhane@silvaco.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=rajeev.huralikoppi@silvaco.com \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@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 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.