From: Vignesh Raghavendra <vigneshr@ti.com>
To: John Garry <john.garry@huawei.com>,
Schrempf Frieder <frieder.schrempf@kontron.de>,
"corbet@lwn.net" <corbet@lwn.net>,
"mchehab+samsung@kernel.org" <mchehab+samsung@kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: "tudor.ambarus@microchip.com" <tudor.ambarus@microchip.com>,
"richard@nod.at" <richard@nod.at>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
wanghuiqiang <wanghuiqiang@huawei.com>
Subject: Re: [PATCH] docs: mtd: Update spi nor reference driver
Date: Mon, 19 Aug 2019 10:09:54 +0530 [thread overview]
Message-ID: <b2a475eb-58e6-e7c7-7b8f-b1be04cf27c0@ti.com> (raw)
In-Reply-To: <ab2d3c29-982f-cb13-e2a2-e6d8da8f1438@huawei.com>
Hi,
On 16/08/19 3:50 PM, John Garry wrote:
> On 06/08/2019 17:40, Schrempf Frieder wrote:
[...]
>
> Hi,
>
> Could someone kindly advise on the following:
>
> I am looking at ACPI support only for an mtd spi nor driver we're
> targeting for mainline support.
>
If its a new driver, please add it under drivers/spi implementing SPI
MEM framework.
There are few drivers under drivers/spi that can be used as example.
(Search for "spi_mem_ops")
> So for the host, I could use a proprietary HID in the DSDT for matching
> in the kernel driver.
>
> About the child spi flash devices, is the recommendation to just use
> PRP0001 HID and "jedec,spi-nor" compatible?
>
I am not quite familiar with ACPI systems, but child flash device should
use "jedec,spi-nor" as compatible.
Regards
Vignesh
> thanks,
> John
>
>
>>
>> @Maintainers:
>> Maybe the docs under Documentation/driver-api/mtd should be officially
>> maintained by the MTD subsystem (and added to MAINTAINERS). And if there
>> will be some driver API docs for SPI MEM it should probably live in
>> Documentation/driver-api/spi instead of Documentation/driver-api/mtd, as
>> spi-mem.c itself is in drivers/spi.
>>
>> Regards,
>> Frieder
>>
>>>
>>> Thanks,
>>> John
>>>
>>>> @@ -59,7 +59,7 @@ Part III - How can drivers use the framework?
>>>>
>>>> The main API is spi_nor_scan(). Before you call the hook, a driver
>>>> should
>>>> initialize the necessary fields for spi_nor{}. Please see
>>>> -drivers/mtd/spi-nor/spi-nor.c for detail. Please also refer to
>>>> fsl-quadspi.c
>>>> +drivers/mtd/spi-nor/spi-nor.c for detail. Please also refer to
>>>> spi-fsl-qspi.c
>>>> when you want to write a new driver for a SPI NOR controller.
>>>> Another API is spi_nor_restore(), this is used to restore the status
>>>> of SPI
>>>> flash chip such as addressing mode. Call it whenever detach the
>>>> driver from
>>>>
>>>
>>>
>>>
>>> ______________________________________________________
>>> Linux MTD discussion mailing list
>>> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
--
Regards
Vignesh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-08-19 4:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 16:06 [PATCH] docs: mtd: Update spi nor reference driver John Garry
2019-08-06 16:35 ` John Garry
2019-08-06 16:40 ` Schrempf Frieder
2019-08-16 10:20 ` John Garry
2019-08-19 4:39 ` Vignesh Raghavendra [this message]
2019-08-20 14:09 ` John Garry
2019-08-20 16:58 ` Mark Brown
2019-08-21 13:39 ` John Garry
2019-09-06 14:52 ` Jonathan Corbet
2019-09-06 14:58 ` John Garry
2019-09-06 15:03 ` Jonathan Corbet
2019-09-06 15:10 ` Tudor.Ambarus
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=b2a475eb-58e6-e7c7-7b8f-b1be04cf27c0@ti.com \
--to=vigneshr@ti.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=frieder.schrempf@kontron.de \
--cc=john.garry@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mchehab+samsung@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=wanghuiqiang@huawei.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;
as well as URLs for NNTP newsgroup(s).