From: Jagan Teki <jteki@openedev.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8 01/14] sf: spi_flash_validate_params => spi_flash_scan
Date: Fri, 11 Dec 2015 12:01:04 +0530 [thread overview]
Message-ID: <566A6DA8.6080602@openedev.com> (raw)
In-Reply-To: <CAEUhbmWFBeYK6c0AH1e6KnmqQjpZ8-CositgTU23y0wjs1rNNA@mail.gmail.com>
On Friday 11 December 2015 11:51 AM, Bin Meng wrote:
> Hi Jagan,
>
> On Thu, Dec 10, 2015 at 11:16 PM, Jagan Teki <jteki@openedev.com> wrote:
>> On 10 December 2015 at 07:00, Bin Meng <bmeng.cn@gmail.com> wrote:
>>> On Mon, Dec 7, 2015 at 2:34 AM, Jagan Teki <jteki@openedev.com> wrote:
>>>> Rename spi_flash_validate_params to spi_flash_scan
>>>> as this code not only deals with params setup but
>>>> also configure all spi_flash attributes.
>>>>
>>>> And also moved all flash related code into
>>>> spi_flash_scan for future functionality addition.
>>>>
>>>> Reviewed-by: Simon Glass <sjg@chromium.org>
>>>> Signed-off-by: Jagan Teki <jteki@openedev.com>
>>>> ---
>>>> drivers/mtd/spi/sf_probe.c | 145 +++++++++++++++++++++++----------------------
>>>> 1 file changed, 75 insertions(+), 70 deletions(-)
>>>>
>>>> diff --git a/drivers/mtd/spi/sf_probe.c b/drivers/mtd/spi/sf_probe.c
>>>> index a619182..0e20088 100644
>>>> --- a/drivers/mtd/spi/sf_probe.c
>>>> +++ b/drivers/mtd/spi/sf_probe.c
>>>> @@ -130,13 +130,42 @@ bank_end:
>>>> }
>>>> #endif
>>>>
>>>> -static int spi_flash_validate_params(struct spi_slave *spi, u8 *idcode,
>>>> +#if CONFIG_IS_ENABLED(OF_CONTROL)
>>>> +int spi_flash_decode_fdt(const void *blob, struct spi_flash *flash)
>>>> +{
>>>> + fdt_addr_t addr;
>>>> + fdt_size_t size;
>>>> + int node;
>>>> +
>>>> + /* If there is no node, do nothing */
>>>> + node = fdtdec_next_compatible(blob, 0, COMPAT_GENERIC_SPI_FLASH);
>>>> + if (node < 0)
>>>> + return 0;
>>>> +
>>>> + addr = fdtdec_get_addr_size(blob, node, "memory-map", &size);
>>>> + if (addr == FDT_ADDR_T_NONE) {
>>>> + debug("%s: Cannot decode address\n", __func__);
>>>> + return 0;
>>>> + }
>>>> +
>>>> + if (flash->size != size) {
>>>> + debug("%s: Memory map must cover entire device\n", __func__);
>>>> + return -1;
>>>> + }
>>>> + flash->memory_map = map_sysmem(addr, size);
>>>> +
>>>> + return 0;
>>>> +}
>>>> +#endif /* CONFIG_IS_ENABLED(OF_CONTROL) */
>>>> +
>>>> +static int spi_flash_scan(struct spi_slave *spi, u8 *idcode,
>>>> struct spi_flash *flash)
>>>
>>> nits: please align above line to the left (
>>
>> What is the reason, will it be an alignment issue.
>
> checkpatch.pl will report such warnings.
>
> [snip]
>
$> ./scripts/checkpatch.pl
0001-sf-spi_flash_validate_params-spi_flash_scan.patch
total: 0 errors, 0 warnings, 0 checks, 195 lines checked
NOTE: Ignored message types: COMPLEX_MACRO CONSIDER_KSTRTO MINMAX
MULTISTATEMENT_MACRO_USE_DO_WHILE NETWORKING_BLOCK_COMMENT_STYLE
USLEEP_RANGE
0001-sf-spi_flash_validate_params-spi_flash_scan.patch has no obvious
style problems and is ready for submission.
--
Jagan
next prev parent reply other threads:[~2015-12-11 6:31 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 18:34 [U-Boot] [PATCH v8 00/14] sf: Tuning spi-flash layer Jagan Teki
2015-12-06 18:34 ` [U-Boot] [PATCH v8 01/14] sf: spi_flash_validate_params => spi_flash_scan Jagan Teki
2015-12-10 1:30 ` Bin Meng
2015-12-10 15:16 ` Jagan Teki
2015-12-11 6:21 ` Bin Meng
2015-12-11 6:31 ` Jagan Teki [this message]
2015-12-11 6:44 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 02/14] sf: Move spi_flash_scan code to sf_ops Jagan Teki
2015-12-10 1:30 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 03/14] sf: Move read_id " Jagan Teki
2015-12-10 1:30 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 04/14] sf: probe: Code cleanup Jagan Teki
2015-12-10 1:30 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 05/14] sf: Use static for file-scope functions Jagan Teki
2015-12-10 1:31 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 06/14] sf: Fix Makefile Jagan Teki
2015-12-06 18:34 ` [U-Boot] [PATCH v8 07/14] sf: Use simple name for register access functions Jagan Teki
2015-12-10 1:31 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 08/14] sf: Flash power up read-only based on idcode0 Jagan Teki
2015-12-10 1:31 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 09/14] sf: Remove unneeded header includes Jagan Teki
2015-12-10 1:31 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 10/14] sf: Remove unneeded SST_BP and SST_WP Jagan Teki
2015-12-10 1:31 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 11/14] sf: ops: Fix missing break on spansion read_bar Jagan Teki
2015-12-09 4:53 ` Simon Glass
2015-12-06 18:34 ` [U-Boot] [PATCH v8 12/14] sf: sf_probe: Remove spi_slave pointer argument Jagan Teki
2015-12-09 4:53 ` Simon Glass
2015-12-10 1:31 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 13/14] sf: Use static for file-scope functions Jagan Teki
2015-12-09 4:53 ` Simon Glass
2015-12-10 1:31 ` Bin Meng
2015-12-06 18:34 ` [U-Boot] [PATCH v8 14/14] sf: Rename sf_ops.c to spi-flash.c Jagan Teki
2015-12-09 4:54 ` Simon Glass
2015-12-09 13:48 ` Jagan Teki
2015-12-10 1:31 ` Bin Meng
2015-12-10 15:13 ` Jagan Teki
2015-12-11 6:23 ` Bin Meng
2015-12-11 6:28 ` Jagan Teki
2015-12-11 6:51 ` Bin Meng
2015-12-11 7:02 ` Jagan Teki
2015-12-11 14:34 ` Simon Glass
2015-12-07 13:14 ` [U-Boot] [PATCH v8 00/14] sf: Tuning spi-flash layer Jagan Teki
2015-12-08 11:54 ` Bin Meng
2015-12-08 10:30 ` Jagan Teki
2015-12-10 15:18 ` Jagan Teki
2015-12-10 15:22 ` Jagan Teki
2015-12-11 16:45 ` Jagan Teki
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=566A6DA8.6080602@openedev.com \
--to=jteki@openedev.com \
--cc=u-boot@lists.denx.de \
/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