[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00394d38-20d9-60a5-0068-5f9f023520c2@ti.com>
Date: Mon, 24 Aug 2020 17:14:56 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Jan Kiszka <jan.kiszka@...mens.com>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Mark Brown <broonie@...nel.org>
CC: Boris Brezillon <bbrezillon@...nel.org>,
Ramuthevar Vadivel Murugan
<vadivel.muruganx.ramuthevar@...ux.intel.com>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-spi@...r.kernel.org>, <simon.k.r.goldschmidt@...il.com>,
<dinguyen@...nel.org>, <marex@...x.de>
Subject: Re: [RESEND PATCH v3 7/8] mtd: spi-nor: Convert cadence-quadspi to
use spi-mem framework
Hi Jan,
On 8/24/20 11:25 AM, Jan Kiszka wrote:
[...]
>> +MODULE_AUTHOR("Vignesh Raghavendra <vigneshr@...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;
};
Regards
Vignesh
Powered by blists - more mailing lists