From: "Cédric Le Goater" <clg@kaod.org>
To: Cyrille Pitchen <cyrille.pitchen@microchip.com>,
Rob Lippert <roblip@gmail.com>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v2 1/2] mtd: spi-nor: aspeed: add support for SPI dual IO read mode
Date: Fri, 23 Jun 2017 13:47:57 +0200 [thread overview]
Message-ID: <f830d7d3-2f34-c2b5-8ef7-cf9432c415d1@kaod.org> (raw)
In-Reply-To: <69129be7-1216-7069-bcff-764ed5e31351@microchip.com>
On 06/23/2017 11:08 AM, Cyrille Pitchen wrote:
> Hi Cédric,
>
> Le 23/06/2017 à 09:02, Cédric Le Goater a écrit :
>> On 06/23/2017 08:35 AM, Cédric Le Goater wrote:
>>> On 06/22/2017 07:17 PM, Rob Lippert wrote:
>>>> On Thu, Jun 22, 2017 at 12:18 AM, Cédric Le Goater <clg@kaod.org> wrote:
>>>>> Implements support for the dual IO read mode on aspeed SMC/FMC
>>>>> controllers which uses both MISO and MOSI lines for data during a read
>>>>> to double the read bandwidth.
>>>>>
>>>>> Based on work from Robert Lippert <roblip@gmail.com>
>>>>>
>>>>> Signed-off-by: Cédric Le Goater <clg@kaod.org>
>>>>> Cc: Robert Lippert <roblip@gmail.com>
>>>>> ---
>>>>>
>>>>> Changes since v1:
>>>>>
>>>>> - reworked the patch to fit the new spi-nor hwcaps
>>>>> - added dual address and data IO
>>>>> - took ownership due to the amount of rewritten code.
>>>>>
>>>>> drivers/mtd/spi-nor/aspeed-smc.c | 52 +++++++++++++++++++++++++++++++---------
>>>>> 1 file changed, 41 insertions(+), 11 deletions(-)
>>>>>
>>>>> diff --git a/drivers/mtd/spi-nor/aspeed-smc.c b/drivers/mtd/spi-nor/aspeed-smc.c
>>>>> index 0106357421bd..93ca2ee65f51 100644
>>>>> --- a/drivers/mtd/spi-nor/aspeed-smc.c
>>>>> +++ b/drivers/mtd/spi-nor/aspeed-smc.c
>>>>> @@ -373,6 +373,33 @@ static void aspeed_smc_send_cmd_addr(struct spi_nor *nor, u8 cmd, u32 addr)
>>>>> }
>>>>> }
>>>>>
>>>>> +static int aspeed_smc_get_io_mode(struct aspeed_smc_chip *chip)
>>>>> +{
>>>>> + switch (chip->nor.read_proto) {
>>>>> + case SNOR_PROTO_1_1_1:
>>>>> + return 0;
>>>>> + case SNOR_PROTO_1_1_2:
>>>>> + return CONTROL_IO_DUAL_DATA;
>>>>> + case SNOR_PROTO_1_2_2:
>>>>> + return CONTROL_IO_DUAL_ADDR_DATA;
>>>>> + default:
>>>>> + dev_err(chip->nor.dev, "unsupported SPI read mode\n");
>>>>> + return -EINVAL;
>>>>> + }
>>>>> +}
>>>>> +
>>>>> +static void aspeed_smc_set_io_mode(struct aspeed_smc_chip *chip)
>>>>> +{
>>>>> + u32 io_mode = aspeed_smc_get_io_mode(chip);
>>>>> + u32 ctl;
>>>>> +
>>>>> + if (io_mode > 0) {
>>>>> + ctl = readl(chip->ctl) & ~CONTROL_IO_MODE_MASK;
>>>>> + ctl |= io_mode;
>>>>> + writel(ctl, chip->ctl);
>>>>> + }
>>>>> +}
>>>>> +
>>>>> static ssize_t aspeed_smc_read_user(struct spi_nor *nor, loff_t from,
>>>>> size_t len, u_char *read_buf)
>>>>> {
>>>>> @@ -385,6 +412,7 @@ static ssize_t aspeed_smc_read_user(struct spi_nor *nor, loff_t from,
>>>>> for (i = 0; i < chip->nor.read_dummy / 8; i++)
>>>>> aspeed_smc_write_to_ahb(chip->ahb_base, &dummy, sizeof(dummy));
>>>>>
>>>>> + aspeed_smc_set_io_mode(chip);
>>>>
>>>> Does this actually work for 1_2_2 mode? I figured you would need to
>>>> set it to dual mode before sending the address (but after the command)
>>>> a few lines up from here.
>>>
>>> yes. This needs a fix for CONTROL_IO_DUAL_ADDR_DATA.
>>
>> I was wondering why I didn't see the BB command being used.
>> The spi-nor layer only provides the SNOR_PROTO_1_2_2 definition
>> but only the SNOR_PROTO_1_1_2 is handled for the moment.
>> Any how, this patch needs some more work.
>
> If you want to test your controller with SPI 1-2-2, you will need this
> patch:
> http://patchwork.ozlabs.org/patch/778995/
>
> As you noticed, currently SPI 1-2-2 and 1-4-4 protocols has been
> introduced in the spi-nor subsystem so the SPI controller drivers can
> declare their hardware capabilities but you will need the SFDP patch to
> take advantage of these capabilities.
>
> If you succeed in using SPI 1-2-2 with the Aspeed controller, don't
> hesitate to add your Tested-by tag on the SFDP patch ;)
So, I gave it a quick try on a AST2400 booting from a n25q256a chip
and I had to double the read_dummies to make it work. I need to study
a little more the question before adding a Tested-by :)
Cheers,
C.
> Best regards,
>
> Cyrille
>
>
>>
>> Thanks,
>>
>> C.
>>
>>
>> ______________________________________________________
>> Linux MTD discussion mailing list
>> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>>
>
next prev parent reply other threads:[~2017-06-23 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 7:18 [PATCH v2 0/2] mtd: spi-nor: aspeed: add dual read and command mode support Cédric Le Goater
2017-06-22 7:18 ` [PATCH v2 1/2] mtd: spi-nor: aspeed: add support for SPI dual IO read mode Cédric Le Goater
2017-06-22 17:17 ` Rob Lippert
2017-06-23 6:35 ` Cédric Le Goater
2017-06-23 7:02 ` Cédric Le Goater
2017-06-23 9:08 ` Cyrille Pitchen
2017-06-23 11:47 ` Cédric Le Goater [this message]
2017-06-23 12:04 ` Cyrille Pitchen
2017-06-22 7:18 ` [PATCH v2 2/2] mtd: spi-nor: aspeed: use command mode for reads Cédric Le Goater
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=f830d7d3-2f34-c2b5-8ef7-cf9432c415d1@kaod.org \
--to=clg@kaod.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@microchip.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=roblip@gmail.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