From: Jagan Teki <jteki@openedev.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8 14/14] sf: Rename sf_ops.c to spi-flash.c
Date: Fri, 11 Dec 2015 12:32:20 +0530 [thread overview]
Message-ID: <566A74FC.6090105@openedev.com> (raw)
In-Reply-To: <CAEUhbmVqpQnXXpjM6=pDDiQhjnsaV2X_oN=6crZNG5iEUYButw@mail.gmail.com>
On Friday 11 December 2015 12:21 PM, Bin Meng wrote:
> Hi Jagan,
>
> On Fri, Dec 11, 2015 at 2:28 PM, Jagan Teki <jteki@openedev.com> wrote:
>>
>>
>> On Friday 11 December 2015 11:53 AM, Bin Meng wrote:
>>>
>>> Hi Jagan,
>>>
>>> On Thu, Dec 10, 2015 at 11:13 PM, Jagan Teki <jteki@openedev.com> wrote:
>>>>
>>>> On 10 December 2015 at 07:01, Bin Meng <bmeng.cn@gmail.com> wrote:
>>>>>
>>>>> On Wed, Dec 9, 2015 at 12:54 PM, Simon Glass <sjg@chromium.org> wrote:
>>>>>>
>>>>>> On 6 December 2015 at 11:34, Jagan Teki <jteki@openedev.com> wrote:
>>>>>>>
>>>>>>> Since all spi-flash core operations are moved into
>>>>>>> sf_ops.c then it's better to renamed as spi-flash.c
>>>>>>>
>>>>>>> Signed-off-by: Jagan Teki <jteki@openedev.com>
>>>>>>> ---
>>>>>>> drivers/mtd/spi/Makefile | 2 +-
>>>>>>> drivers/mtd/spi/{sf_ops.c => spi-flash.c} | 7 ++++---
>>>>>>> 2 files changed, 5 insertions(+), 4 deletions(-)
>>>>>>> rename drivers/mtd/spi/{sf_ops.c => spi-flash.c} (99%)
>>>>>>
>>>>>>
>>>>>> Reviewed-by: Simon Glass <sjg@chromium.org>
>>>>>>
>>>>>> (but I suggest spi_flash.c is better as it fits with the other files)
>>>>>
>>>>>
>>>>> Agreed. spi_flash.c makes more sense. So far it looks that only driver
>>>>> model uclass driver is using - in the file name, others are using _.
>>>>
>>>>
>>>> Clear, but this file will handle common spi-flash core functionalities
>>>> it shouldn't be dm even now or later and more over underlying sf_probe
>>>> which is calling this through spi_flash_scan has a driver model on it.
>>>
>>>
>>> Sorry, I don't quite understand what you mean. But my comment is to
>>> rename sf_ops.c to sf_flash.c, not sf-flash.c.
>>
>>
>>
>> spi-flash.c (the function spi_flash_scan from sf_probe, so this never be a
>> dm driver and it handles all core functionalities
>> ======================================================================
>> sf_probe.c (this has dm support)
>> =================================
>>
>> Since you're saying dm has - and ie the reason I'm saying spi-flash.c should
>> technically a dm supported core.
>>
>
> I was saying it looks to me that only dm uclass driver is allowed to
> have -, like sf-uclass.c or pci-uclass.c. Other files we should use _.
sf_probe.c is a dm driver - agree?
If ie the case probably this is the first file has a code moved from dm
driver into different file which is spi-flash in this case.
thanks!
--
Jagan
next prev parent reply other threads:[~2015-12-11 7:02 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
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 [this message]
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=566A74FC.6090105@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