From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Mark Brown <broonie@kernel.org>
Cc: Boris Brezillon <bbrezillon@kernel.org>,
Ramuthevar Vadivel Murugan
<vadivel.muruganx.ramuthevar@linux.intel.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, simon.k.r.goldschmidt@gmail.com,
dinguyen@kernel.org, marex@denx.de
Subject: Re: [RESEND PATCH v3 7/8] mtd: spi-nor: Convert cadence-quadspi to use spi-mem framework
Date: Mon, 24 Aug 2020 14:06:41 +0200 [thread overview]
Message-ID: <26caa2e5-6c6e-09a3-902e-843cfee40158@siemens.com> (raw)
In-Reply-To: <00394d38-20d9-60a5-0068-5f9f023520c2@ti.com>
On 24.08.20 13:44, Vignesh Raghavendra wrote:
> Hi Jan,
>
> On 8/24/20 11:25 AM, Jan Kiszka wrote:
> [...]
>
>>> +MODULE_AUTHOR("Vignesh Raghavendra <vigneshr@ti.com>");
>>>
>> On the AM65x, this changes mtd->name (thus mtd-id for
>> parser/cmdlinepart) from 47040000.spi.0 to spi7.0. The besides having to
>> deal with both names now, "spi7" sounds like it could easily change
>> again if someone plugs or unplugs some other SPI device. Is this intended?
>>
>
> You could use DT aliases to make sure OSPI0 is always at given bus num
> (say spi7):
>
> aliases {
> spi7 = &ospi0;
> };
Ah, looks like this is a common pattern... Thanks, will try that.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Mark Brown <broonie@kernel.org>
Cc: marex@denx.de, Boris Brezillon <bbrezillon@kernel.org>,
dinguyen@kernel.org, simon.k.r.goldschmidt@gmail.com,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Ramuthevar Vadivel Murugan
<vadivel.muruganx.ramuthevar@linux.intel.com>,
linux-mtd@lists.infradead.org
Subject: Re: [RESEND PATCH v3 7/8] mtd: spi-nor: Convert cadence-quadspi to use spi-mem framework
Date: Mon, 24 Aug 2020 14:06:41 +0200 [thread overview]
Message-ID: <26caa2e5-6c6e-09a3-902e-843cfee40158@siemens.com> (raw)
In-Reply-To: <00394d38-20d9-60a5-0068-5f9f023520c2@ti.com>
On 24.08.20 13:44, Vignesh Raghavendra wrote:
> Hi Jan,
>
> On 8/24/20 11:25 AM, Jan Kiszka wrote:
> [...]
>
>>> +MODULE_AUTHOR("Vignesh Raghavendra <vigneshr@ti.com>");
>>>
>> On the AM65x, this changes mtd->name (thus mtd-id for
>> parser/cmdlinepart) from 47040000.spi.0 to spi7.0. The besides having to
>> deal with both names now, "spi7" sounds like it could easily change
>> again if someone plugs or unplugs some other SPI device. Is this intended?
>>
>
> You could use DT aliases to make sure OSPI0 is always at given bus num
> (say spi7):
>
> aliases {
> spi7 = &ospi0;
> };
Ah, looks like this is a common pattern... Thanks, will try that.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-08-24 12:07 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 7:04 [RESEND PATCH v3 0/8] mtd: spi-nor: Move cadence-qaudspi to spi-mem framework Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-06-01 7:04 ` [RESEND PATCH v3 1/8] mtd: spi-nor: cadence-quadspi: Make driver independent of flash geometry Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-06-01 7:04 ` [RESEND PATCH v3 2/8] mtd: spi-nor: cadence-quadspi: Provide a way to disable DAC mode Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-06-01 7:04 ` [RESEND PATCH v3 3/8] mtd: spi-nor: cadence-quadspi: Don't initialize rx_dma_complete on failure Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-06-01 7:04 ` [RESEND PATCH v3 4/8] mtd: spi-nor: cadence-quadspi: Fix error path on failure to acquire reset lines Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-06-01 7:04 ` [RESEND PATCH v3 5/8] mtd: spi-nor: cadence-quadspi: Handle probe deferral while requesting DMA channel Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-08-22 18:05 ` Jan Kiszka
2020-08-22 18:05 ` Jan Kiszka
2020-08-24 11:45 ` Vignesh Raghavendra
2020-08-24 11:45 ` Vignesh Raghavendra
2020-08-24 12:49 ` Jan Kiszka
2020-08-24 12:49 ` Jan Kiszka
2020-08-24 17:20 ` Jan Kiszka
2020-08-24 17:20 ` Jan Kiszka
2020-08-26 10:12 ` Jan Kiszka
2020-08-26 10:12 ` Jan Kiszka
2020-08-26 12:18 ` Vignesh Raghavendra
2020-08-26 12:18 ` Vignesh Raghavendra
2020-08-26 13:31 ` Jan Kiszka
2020-08-26 13:31 ` Jan Kiszka
2020-08-27 7:04 ` Vignesh Raghavendra
2020-08-27 7:04 ` Vignesh Raghavendra
2020-08-25 3:12 ` Jin, Le
2020-08-25 3:12 ` Jin, Le
2020-06-01 7:04 ` [RESEND PATCH v3 6/8] mtd: spi-nor: cadence-quadspi: Drop redundant WREN in erase path Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-06-01 7:04 ` [RESEND PATCH v3 7/8] mtd: spi-nor: Convert cadence-quadspi to use spi-mem framework Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-08-24 5:55 ` Jan Kiszka
2020-08-24 5:55 ` Jan Kiszka
2020-08-24 11:44 ` Vignesh Raghavendra
2020-08-24 11:44 ` Vignesh Raghavendra
2020-08-24 12:04 ` Boris Brezillon
2020-08-24 12:04 ` Boris Brezillon
2020-08-24 13:52 ` Jan Kiszka
2020-08-24 13:52 ` Jan Kiszka
2020-08-24 12:06 ` Jan Kiszka [this message]
2020-08-24 12:06 ` Jan Kiszka
2020-06-01 7:04 ` [RESEND PATCH v3 8/8] spi: Move cadence-quadspi driver to drivers/spi/ Vignesh Raghavendra
2020-06-01 7:04 ` Vignesh Raghavendra
2020-06-19 10:57 ` [RESEND PATCH v3 0/8] mtd: spi-nor: Move cadence-qaudspi to spi-mem framework Mark Brown
2020-06-19 10:57 ` Mark Brown
2020-06-19 11:47 ` Tudor.Ambarus
2020-06-19 11:47 ` Tudor.Ambarus
2020-06-19 15:17 ` Mark Brown
2020-06-19 15:17 ` Mark Brown
2020-06-26 9:25 ` Tudor.Ambarus
2020-06-26 9:25 ` Tudor.Ambarus
2020-06-19 13:28 ` Mark Brown
2020-06-19 13:28 ` Mark Brown
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=26caa2e5-6c6e-09a3-902e-843cfee40158@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=tudor.ambarus@microchip.com \
--cc=vadivel.muruganx.ramuthevar@linux.intel.com \
--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.