From: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>,
"p.yadav@ti.com" <p.yadav@ti.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"git@xilinx.com" <git@xilinx.com>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"michael@walle.cc" <michael@walle.cc>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"git (AMD-Xilinx)" <git@amd.com>
Subject: RE: [RFC PATCH 1/2] spi: Add multiple CS support for a single SPI device
Date: Wed, 27 Jul 2022 13:02:31 +0000 [thread overview]
Message-ID: <BN7PR12MB2802E2A9079E505932832270DC979@BN7PR12MB2802.namprd12.prod.outlook.com> (raw)
In-Reply-To: <YtbvlYZoRDz6i+pS@sirena.org.uk>
Hello Mark,
> -----Original Message-----
> From: Mark Brown <broonie@kernel.org>
> Sent: Tuesday, July 19, 2022 11:23 PM
> To: Mahapatra, Amit Kumar <amit.kumar-mahapatra@amd.com>
> Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>;
> p.yadav@ti.com; miquel.raynal@bootlin.com; richard@nod.at;
> vigneshr@ti.com; git@xilinx.com; michal.simek@xilinx.com; linux-
> spi@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org; michael@walle.cc; linux-mtd@lists.infradead.org;
> git (AMD-Xilinx) <git@amd.com>
> Subject: Re: [RFC PATCH 1/2] spi: Add multiple CS support for a single SPI
> device
>
> On Tue, Jul 19, 2022 at 01:21:41PM +0000, Mahapatra, Amit Kumar wrote:
>
> > I agree, so for checking the controller multiple chip select
> > capability(using more than one chip select at once) we can define a
> > new spi controller DT property like "multi-cs-cap"(please suggest a better
> name).
> > The controller that can support multiple chip selects should have this
> > property in the spi controller DT node. The spi core will check
> > ctlr->multi-cs-cap to operate multiple chip select in parallel.
>
> I'm not sure this needs to be a DT property, it's more just something we infer
> from the compatible. The name seems fine, as does the flag in the controller
> data.
I agree that we can infer this from the compatible and set the flag in the controller data.
>
> > > the chip selects are available and that the controller can do
> > > something useful with them (and probably have an implementation in
> > > the core for doing so via GPIO).
>
> > Here are you referring to the usecase in which a controller
> > implementing multi CS support using GPIO?
>
> Yes, we probably ought to.
In my next version I will add the implementation in the spi core for multi CS support using GPIO, but I will not be able test it as I don't have the necessary hardware setup .
Regards,
Amit
WARNING: multiple messages have this Message-ID (diff)
From: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>,
"p.yadav@ti.com" <p.yadav@ti.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"git@xilinx.com" <git@xilinx.com>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"michael@walle.cc" <michael@walle.cc>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"git (AMD-Xilinx)" <git@amd.com>
Subject: RE: [RFC PATCH 1/2] spi: Add multiple CS support for a single SPI device
Date: Wed, 27 Jul 2022 13:02:31 +0000 [thread overview]
Message-ID: <BN7PR12MB2802E2A9079E505932832270DC979@BN7PR12MB2802.namprd12.prod.outlook.com> (raw)
In-Reply-To: <YtbvlYZoRDz6i+pS@sirena.org.uk>
Hello Mark,
> -----Original Message-----
> From: Mark Brown <broonie@kernel.org>
> Sent: Tuesday, July 19, 2022 11:23 PM
> To: Mahapatra, Amit Kumar <amit.kumar-mahapatra@amd.com>
> Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>;
> p.yadav@ti.com; miquel.raynal@bootlin.com; richard@nod.at;
> vigneshr@ti.com; git@xilinx.com; michal.simek@xilinx.com; linux-
> spi@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org; michael@walle.cc; linux-mtd@lists.infradead.org;
> git (AMD-Xilinx) <git@amd.com>
> Subject: Re: [RFC PATCH 1/2] spi: Add multiple CS support for a single SPI
> device
>
> On Tue, Jul 19, 2022 at 01:21:41PM +0000, Mahapatra, Amit Kumar wrote:
>
> > I agree, so for checking the controller multiple chip select
> > capability(using more than one chip select at once) we can define a
> > new spi controller DT property like "multi-cs-cap"(please suggest a better
> name).
> > The controller that can support multiple chip selects should have this
> > property in the spi controller DT node. The spi core will check
> > ctlr->multi-cs-cap to operate multiple chip select in parallel.
>
> I'm not sure this needs to be a DT property, it's more just something we infer
> from the compatible. The name seems fine, as does the flag in the controller
> data.
I agree that we can infer this from the compatible and set the flag in the controller data.
>
> > > the chip selects are available and that the controller can do
> > > something useful with them (and probably have an implementation in
> > > the core for doing so via GPIO).
>
> > Here are you referring to the usecase in which a controller
> > implementing multi CS support using GPIO?
>
> Yes, we probably ought to.
In my next version I will add the implementation in the spi core for multi CS support using GPIO, but I will not be able test it as I don't have the necessary hardware setup .
Regards,
Amit
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>,
"p.yadav@ti.com" <p.yadav@ti.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"git@xilinx.com" <git@xilinx.com>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"michael@walle.cc" <michael@walle.cc>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"git (AMD-Xilinx)" <git@amd.com>
Subject: RE: [RFC PATCH 1/2] spi: Add multiple CS support for a single SPI device
Date: Wed, 27 Jul 2022 13:02:31 +0000 [thread overview]
Message-ID: <BN7PR12MB2802E2A9079E505932832270DC979@BN7PR12MB2802.namprd12.prod.outlook.com> (raw)
In-Reply-To: <YtbvlYZoRDz6i+pS@sirena.org.uk>
Hello Mark,
> -----Original Message-----
> From: Mark Brown <broonie@kernel.org>
> Sent: Tuesday, July 19, 2022 11:23 PM
> To: Mahapatra, Amit Kumar <amit.kumar-mahapatra@amd.com>
> Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>;
> p.yadav@ti.com; miquel.raynal@bootlin.com; richard@nod.at;
> vigneshr@ti.com; git@xilinx.com; michal.simek@xilinx.com; linux-
> spi@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org; michael@walle.cc; linux-mtd@lists.infradead.org;
> git (AMD-Xilinx) <git@amd.com>
> Subject: Re: [RFC PATCH 1/2] spi: Add multiple CS support for a single SPI
> device
>
> On Tue, Jul 19, 2022 at 01:21:41PM +0000, Mahapatra, Amit Kumar wrote:
>
> > I agree, so for checking the controller multiple chip select
> > capability(using more than one chip select at once) we can define a
> > new spi controller DT property like "multi-cs-cap"(please suggest a better
> name).
> > The controller that can support multiple chip selects should have this
> > property in the spi controller DT node. The spi core will check
> > ctlr->multi-cs-cap to operate multiple chip select in parallel.
>
> I'm not sure this needs to be a DT property, it's more just something we infer
> from the compatible. The name seems fine, as does the flag in the controller
> data.
I agree that we can infer this from the compatible and set the flag in the controller data.
>
> > > the chip selects are available and that the controller can do
> > > something useful with them (and probably have an implementation in
> > > the core for doing so via GPIO).
>
> > Here are you referring to the usecase in which a controller
> > implementing multi CS support using GPIO?
>
> Yes, we probably ought to.
In my next version I will add the implementation in the spi core for multi CS support using GPIO, but I will not be able test it as I don't have the necessary hardware setup .
Regards,
Amit
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-27 13:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 11:26 [RFC PATCH 0/2] spi: Add support for stacked/parallel memories Amit Kumar Mahapatra
2022-06-06 11:26 ` Amit Kumar Mahapatra
2022-06-06 11:26 ` Amit Kumar Mahapatra
2022-06-06 11:26 ` [RFC PATCH 1/2] spi: Add multiple CS support for a single SPI device Amit Kumar Mahapatra
2022-06-06 11:26 ` Amit Kumar Mahapatra
2022-06-06 11:26 ` Amit Kumar Mahapatra
2022-06-09 11:54 ` Mark Brown
2022-06-09 11:54 ` Mark Brown
2022-06-09 11:54 ` Mark Brown
2022-06-23 11:39 ` Mahapatra, Amit Kumar
2022-06-23 11:39 ` Mahapatra, Amit Kumar
2022-06-23 11:39 ` Mahapatra, Amit Kumar
2022-06-23 12:06 ` Mark Brown
2022-06-23 12:06 ` Mark Brown
2022-06-23 12:06 ` Mark Brown
2022-07-15 15:35 ` Mahapatra, Amit Kumar
2022-07-15 15:35 ` Mahapatra, Amit Kumar
2022-07-15 15:35 ` Mahapatra, Amit Kumar
2022-07-15 15:54 ` Mark Brown
2022-07-15 15:54 ` Mark Brown
2022-07-15 15:54 ` Mark Brown
2022-07-19 13:21 ` Mahapatra, Amit Kumar
2022-07-19 13:21 ` Mahapatra, Amit Kumar
2022-07-19 13:21 ` Mahapatra, Amit Kumar
2022-07-19 17:53 ` Mark Brown
2022-07-19 17:53 ` Mark Brown
2022-07-19 17:53 ` Mark Brown
2022-07-27 13:02 ` Mahapatra, Amit Kumar [this message]
2022-07-27 13:02 ` Mahapatra, Amit Kumar
2022-07-27 13:02 ` Mahapatra, Amit Kumar
2022-07-11 12:47 ` Michal Simek
2022-07-11 12:47 ` Michal Simek
2022-07-11 12:47 ` Michal Simek
2022-07-11 14:52 ` Mark Brown
2022-07-11 14:52 ` Mark Brown
2022-07-11 14:52 ` Mark Brown
2022-07-15 15:36 ` Mahapatra, Amit Kumar
2022-07-15 15:36 ` Mahapatra, Amit Kumar
2022-07-15 15:36 ` Mahapatra, Amit Kumar
2022-07-15 16:03 ` Mark Brown
2022-07-15 16:03 ` Mark Brown
2022-07-15 16:03 ` Mark Brown
2022-06-06 11:26 ` [RFC PATCH 2/2] mtd: spi-nor: Add support for stacked/parallel memories Amit Kumar Mahapatra
2022-06-06 11:26 ` Amit Kumar Mahapatra
2022-06-06 11:26 ` Amit Kumar Mahapatra
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=BN7PR12MB2802E2A9079E505932832270DC979@BN7PR12MB2802.namprd12.prod.outlook.com \
--to=amit.kumar-mahapatra@amd.com \
--cc=amit.kumar-mahapatra@xilinx.com \
--cc=broonie@kernel.org \
--cc=git@amd.com \
--cc=git@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@walle.cc \
--cc=michal.simek@xilinx.com \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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.