From: Mugunthan V N <mugunthanvnm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 10/16] drivers: mtd: spi: sf_probe: add compatible for spansion spi flash
Date: Sun, 6 Dec 2015 12:27:19 +0530 [thread overview]
Message-ID: <5663DC4F.4070508@ti.com> (raw)
In-Reply-To: <CAD6G_RScK=ajwgmYbDJ+68UnooEzMPVE_maSDrRd-V1WRO2k+g@mail.gmail.com>
On Thursday 03 December 2015 09:32 PM, Jagan Teki wrote:
> Hi Mugunthan,
>
> On 23 November 2015 at 18:42, Jagan Teki <jteki@openedev.com> wrote:
>> On 23 November 2015 at 16:59, Mugunthan V N <mugunthanvnm@ti.com> wrote:
>>> On Friday 20 November 2015 05:57 PM, Jagan Teki wrote:
>>>> On 20 November 2015 at 11:31, Mugunthan V N <mugunthanvnm@ti.com> wrote:
>>>>> Jagan
>>>>>
>>>>> On Thursday 19 November 2015 03:40 PM, Jagan Teki wrote:
>>>>>> On 19 November 2015 at 12:35, Mugunthan V N <mugunthanvnm@ti.com> wrote:
>>>>>>> Add compatible for spansion 32MiB spi flash s25fl256s1.
>>>>>>>
>>>>>>> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
>>>>>>> ---
>>>>>>> drivers/mtd/spi/sf_probe.c | 1 +
>>>>>>> 1 file changed, 1 insertion(+)
>>>>>>>
>>>>>>> diff --git a/drivers/mtd/spi/sf_probe.c b/drivers/mtd/spi/sf_probe.c
>>>>>>> index bc05d30..ffbce59 100644
>>>>>>> --- a/drivers/mtd/spi/sf_probe.c
>>>>>>> +++ b/drivers/mtd/spi/sf_probe.c
>>>>>>> @@ -515,6 +515,7 @@ static const struct dm_spi_flash_ops spi_flash_std_ops = {
>>>>>>>
>>>>>>> static const struct udevice_id spi_flash_std_ids[] = {
>>>>>>> { .compatible = "spi-flash" },
>>>>>>> + { .compatible = "s25fl256s1" },
>>>>>>> { }
>>>>>>
>>>>>> Never compare with spi-flash vs s25fl256s1 here former is driver
>>>>>> compatible string and later one is probed flash string name. we don't
>>>>>> need to add them in compatible list, better to add it on dts node
>>>>>> otherwise no issue the connected flash will detect while 'sf probe'
>>>>>>
>>>>>
>>>>> I agree that spi flash will be probed even without addition of compatibles.
>>>>>
>>>>> If there is no matching compatible between the dtb and driver, the dt
>>>>> properties like spi-max-frequency, spi clock phase/polarity and spi
>>>>> bus-width are not parsed from DT as the of_offset of the spi device will
>>>>> be '-1'. This check and dt parse is done in spi_child_post_bind() in
>>>>> spi-uclass driver.
>>>>>
>>>>> Since spi bus-width is not read from DT, by default spi transfers are
>>>>> done in one wire mode and read throughput drops to 5.3Mbps. With Quad
>>>>> mode read throughput is 16.6Mbps in DRA74x EVM.
>>>>>
>>>>
>>>> Why can't we try something like this [1] [2] I do agree with
>>>> documentation missing, may be we add add that well.
>>>>
>>>> [1] arch/arm/dts/socfpga_cyclone5_sockit.dts
>>>
>>> This dts file is not in sync with kernel dts. There is no qspi support
>>> in kernel. It is going to be really tough time to sync this dts between
>>> kernel and u-boot ;)
>>
>> Since we are in starting point of adding dts files (unlike Linux)
>> these dts files may not sync with Linux, we started adding these to
>> make dm or related drivers need to work. Yes I agreed with your point
>> and we really need to work on that as well.
>>
>>>
>>>> [2] arch/arm/dts/zynqmp-ep108.dts
>>>
>>> I don't see compatible string "spi-flash" in zynqmp-ep108.dts
>>
>> Yes, cant you add "s25fl256s1" like n25q512a11 added in this dts.
>>
>>>
>>> Adding spi-flash compatible will be tough as spi-flash works with the
>>> existing compatibles and convincing spi maintainer (Mark Brown) for
>>> adding a generic compatible will be difficult.
>>
>> This is what you pointed out - id_table.
>>
>> static struct spi_driver m25p80_driver = {
>> .driver = {
>> .name = "m25p80",
>> .of_match_table = m25p_of_table,
>> },
>> .id_table = m25p_ids,
>>
>
> Comments?
Yes, I was pointing to this compatible only.
>
>>
>>>
>>> If you still insist to add spi-flash compatible to the dts file and *Tom
>>> Rini* is also fine, I will re-spin the series with compatible changes to
>>> the dts files.
>>
>> I'm saying like s25fl256s1 few of compatible strings were added
>> already on existing dts files, probably we may proceed with the same
>> for now. will trimming up later.
>
> Any comments? proceed with above suggestion.
I agree, we can add compatibles, if needed we can work on trimming it later.
Regards
Mugunthan V N
next prev parent reply other threads:[~2015-12-06 6:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 7:05 [U-Boot] [PATCH v3 00/16] device model bring-up of ti-qspi on dra72, dra74 and am437x-sk evm Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 01/16] drivers: spi: ti_qspi: do not hard code chip select for memory map configuration Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 02/16] drivers: spi:ti_qspi: change ti_qspi_slave to ti_qspi_priv for driver model conversion Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 03/16] drivers: spi: ti_qspi: prepare driver for DM conversion Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 04/16] dm: core: Add a new api to get indexed device address Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 05/16] spi: Add support for dual and quad mode Mugunthan V N
2015-12-03 16:07 ` Jagan Teki
2015-12-06 6:03 ` Mugunthan V N
2015-12-06 14:43 ` Jagan Teki
2015-12-08 15:05 ` Mugunthan V N
2015-12-08 15:48 ` Jagan Teki
2015-12-15 7:52 ` [U-Boot] [PATCH v4 " Mugunthan V N
2015-12-15 8:13 ` Jagan Teki
2015-12-17 6:30 ` Mugunthan V N
2015-12-17 6:49 ` Jagan Teki
2015-12-17 16:40 ` Jagan Teki
2015-12-20 3:24 ` Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 06/16] dra7xx_evm: qspi: do not define DM_SPI and DM_SPI_FLASH for spl Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 07/16] dts: dra7: add spi alias for qspi Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 08/16] drivers: spi: ti_qspi: convert driver to adopt device driver model Mugunthan V N
2015-12-15 7:52 ` [U-Boot] [PATCH v4 " Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 09/16] arm: dts: dra7: add qspi register maps for memory map and control module Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 10/16] drivers: mtd: spi: sf_probe: add compatible for spansion spi flash Mugunthan V N
2015-11-19 10:10 ` Jagan Teki
2015-11-20 6:01 ` Mugunthan V N
2015-11-20 12:27 ` Jagan Teki
2015-11-23 11:29 ` Mugunthan V N
2015-11-23 13:12 ` Jagan Teki
2015-12-03 16:02 ` Jagan Teki
2015-12-06 6:57 ` Mugunthan V N [this message]
2015-11-23 15:24 ` Tom Rini
2015-11-19 7:05 ` [U-Boot] [PATCH v3 11/16] drivers: mtd: spi: sf_probe: add compatible for Macronix " Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 12/16] defconfig: dra72_evm: enable spi driver model Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 13/16] defconfig: dra74_evm: " Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 14/16] am43xx_evm: qspi: do not define DM_SPI and DM_SPI_FLASH for spl Mugunthan V N
2015-11-21 1:20 ` Tom Rini
2015-11-19 7:05 ` [U-Boot] [PATCH v3 15/16] arm: dts: am4372: add qspi register maps for memory map Mugunthan V N
2015-11-19 7:05 ` [U-Boot] [PATCH v3 16/16] defconfig: am437x_sk_evm: enable spi driver model Mugunthan V N
2015-12-01 6:31 ` [U-Boot] [PATCH v3 00/16] device model bring-up of ti-qspi on dra72, dra74 and am437x-sk evm Mugunthan V N
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=5663DC4F.4070508@ti.com \
--to=mugunthanvnm@ti.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