From: shijie8@gmail.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] spi-nor: Remove spi_nor::read_id operation
Date: Mon, 15 Sep 2014 22:55:24 +0800 [thread overview]
Message-ID: <20140915145523.GA1963@localhost.localdomain> (raw)
In-Reply-To: <1410714676.3040.40.camel@decadent.org.uk>
On Sun, Sep 14, 2014 at 06:11:16PM +0100, Ben Hutchings wrote:
> There is currently no useful way to override the default
> implementation of this operation. The returned struct spi_device_id
> must have a pointer to struct flash_info in its private data, but this
> structure is defined inside spi-nor.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> drivers/mtd/spi-nor/spi-nor.c | 4 +---
> include/linux/mtd/spi-nor.h | 3 ---
> 2 files changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 6b1bda2..6f699c5 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -902,8 +902,6 @@ static int spi_nor_check(struct spi_nor *nor)
> return -EINVAL;
> }
>
> - if (!nor->read_id)
> - nor->read_id = spi_nor_read_id;
> if (!nor->wait_till_ready)
> nor->wait_till_ready = spi_nor_wait_till_ready;
>
> @@ -952,7 +950,7 @@ int spi_nor_scan(struct spi_nor *nor, const struct spi_device_id *id,
> if (info->jedec_id) {
> const struct spi_device_id *jid;
>
> - jid = nor->read_id(nor);
> + jid = spi_nor_read_id(nor);
> if (IS_ERR(jid)) {
> return PTR_ERR(jid);
> } else if (jid != id) {
> diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h
> index 5ec84cc..66af67a 100644
> --- a/include/linux/mtd/spi-nor.h
> +++ b/include/linux/mtd/spi-nor.h
> @@ -139,8 +139,6 @@ enum spi_nor_ops {
> * @write_xfer: [OPTIONAL] the writefundamental primitive
> * @read_reg: [DRIVER-SPECIFIC] read out the register
> * @write_reg: [DRIVER-SPECIFIC] write data to the register
> - * @read_id: [REPLACEABLE] read out the ID data, and find
> - * the proper spi_device_id
If we remove this hook, i guess we will add it back in the later.
Other new drivers will use this hook.
so i suggest to keep it as it is.
thanks
Huang Shijie
next prev parent reply other threads:[~2014-09-15 14:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 17:10 [PATCH 0/5] m25p80,spi-nor: Fix module aliases for m25p80; clean up chip identification Ben Hutchings
2014-09-14 17:11 ` [PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80 Ben Hutchings
2014-09-28 22:21 ` Brian Norris
2014-09-29 6:36 ` Rafał Miłecki
2014-09-29 9:53 ` Rafał Miłecki
2014-09-29 10:25 ` Rafał Miłecki
2014-09-30 2:07 ` Ben Hutchings
2014-09-30 3:55 ` Brian Norris
2014-09-30 5:09 ` Rafał Miłecki
2014-09-29 8:37 ` Rafał Miłecki
2014-09-14 17:11 ` [PATCH 2/5] spi-nor: Remove spi_nor::read_id operation Ben Hutchings
2014-09-15 14:55 ` Huang Shijie [this message]
2014-09-15 15:08 ` Ben Hutchings
2014-09-14 17:11 ` [PATCH 3/5] spi-nor: Make spi_nor_scan() take a chip type name, not an spi_device_id Ben Hutchings
2014-09-14 17:11 ` [PATCH 4/5] spi-nor: Replace struct spi_device_id with struct flash_info Ben Hutchings
2014-09-14 17:11 ` [PATCH 5/5] m25p80,spi-nor: Share the list of supported chip type names again Ben Hutchings
2014-09-15 7:55 ` [PATCH 5/5] m25p80, spi-nor: " Geert Uytterhoeven
2014-09-15 15:07 ` [PATCH 5/5] m25p80,spi-nor: " Ben Hutchings
2014-09-17 8:23 ` [PATCH 5/5] m25p80, spi-nor: " Geert Uytterhoeven
2014-09-30 1:50 ` [PATCH 5/5] m25p80,spi-nor: " Ben Hutchings
2014-09-14 17:13 ` [PATCH 0/5] m25p80,spi-nor: Fix module aliases for m25p80; clean up chip identification Ben Hutchings
2014-09-28 22:03 ` Brian Norris
2014-09-30 1:47 ` Ben Hutchings
2014-10-10 4:52 ` Brian Norris
2014-09-28 11:35 ` 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=20140915145523.GA1963@localhost.localdomain \
--to=shijie8@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).