sf: spansion: Update the name for S25FL256S flash
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH v2 1/8 sf: spansion: Update the name for S25FL256S flash
As the per the ID tabl the flash is under Uniform 64-kB sector architecture, hence updated with proper name.
---
Changes for v2:
- none
drivers/mtd/spi/spansion.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mtd/spi/spansion.c +1 -1
@@ -108,7 +108,7 @@ static const struct spansion_spi_flash_params spansion_spi_flash_table[] = { .idcode2 = 0x4d01, .pages_per_sector = 256, .nr_sectors = 512, - .name = "S25FL256S", + .name = "S25FL256S_64K", }, };
Signature · 1 line
1.8.3
PATCH v2 1/8 sf: spansion: Update the name for S25FL256S flash
Quoted 17 lines · Jagannadha Sutradharudu Teki
As the per the ID tabl the flash is under Uniform 64-kB sector architecture, hence updated with proper name.
Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/spansion.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/mtd/spi/spansion.c +0
-0
drivers/mtd/spi/spansion.c static const struct spansion_spi_flash_params spansion_spi_flash_table[] = { · line 114
Quoted 8 lines
drivers/mtd/spi/spansion.c +1
-1@@ -108,7 +108,7 @@ static const struct spansion_spi_flash_params spansion_spi_flash_table[] = { .idcode2 = 0x4d01, .pages_per_sector = 256, .nr_sectors = 512, - .name = "S25FL256S", + .name = "S25FL256S_64K", }, };
Applied to u-boot-spi/master
--
Thanks,
Jagan.
PATCH v2 2/8 sf: spansion: Add support for S25FL128S_64K
In reply to a message not in the archiveThis commit is based on the patch from Xie Xiaobo <[email protected]> with commit head title as "sf: spansion: Add support for S25FL128S". pulled the same code changes into current u-boot tree with little update on the name field.
http://patchwork.ozlabs.org/patch/218145/
SPANSION recommend S25FL128S supersedes S25FL129P, and the two flash memory have the same device ID and Memory architecture. So they can use the same config parameters.
---
Changes for v2:
- none
drivers/mtd/spi/spansion.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mtd/spi/spansion.c +1 -1
@@ -101,7 +101,7 @@ static const struct spansion_spi_flash_params spansion_spi_flash_table[] = { .idcode2 = 0x4d01, .pages_per_sector = 256, .nr_sectors = 256, - .name = "S25FL129P_64K", + .name = "S25FL129P_64K/S25FL128S_64K", }, { .idcode1 = 0x0219,
Signature · 1 line
1.8.3
PATCH v2 2/8 sf: spansion: Add support for S25FL128S_64K
Quoted 25 lines · Jagannadha Sutradharudu Teki
This commit is based on the patch from Xie Xiaobo <[email protected]> with commit head title as "sf: spansion: Add support for S25FL128S". pulled the same code changes into current u-boot tree with little update on the name field.
http://patchwork.ozlabs.org/patch/218145/
SPANSION recommend S25FL128S supersedes S25FL129P, and the two flash memory have the same device ID and Memory architecture. So they can use the same config parameters.
Signed-off-by Xie Xiaobo <[email protected]>Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/spansion.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/mtd/spi/spansion.c +0
-0
drivers/mtd/spi/spansion.c static const struct spansion_spi_flash_params spansion_spi_flash_table[] = { · line 104
Quoted 5 lines
drivers/mtd/spi/spansion.c +1
-1@@ -101,7 +101,7 @@ static const struct spansion_spi_flash_params spansion_spi_flash_table[] = { .idcode2 = 0x4d01, .pages_per_sector = 256, .nr_sectors = 256, - .name = "S25FL129P_64K", + .name = "S25FL129P_64K/S25FL128S_64K",
Any comments on this notation, as the ID's are same for these parts upto 5bytes. if you need to differ then we should read the 6th byte.
If i.e the case increase the byte count on probe function for this, due to extra over head only for this, i just noted like this. does it make sense?
Request comments.
--
Thanks,
Jagan.
PATCH v2 3/8 sf: winbond: Add support for W25Q80BW
In reply to a message not in the archiveAdd support for Winbond W25Q80BW SPI flash.
This patch corrected the flash name, nr_blocks and also commit message header from below patch. "sf: winbond: add W25Q32"
(sha1: c969abc47033d6f810d3c9dbdb994ea9d691d038)
---
Changes for v2:
- none
drivers/mtd/spi/winbond.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/mtd/spi/winbond.c +2 -2
@@ -84,8 +84,8 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { }, { .id = 0x5014, - .nr_blocks = 128, - .name = "W25Q80", + .nr_blocks = 16, + .name = "W25Q80BW", }, { .id = 0x6016,
Signature · 1 line
1.8.3
PATCH v2 3/8 sf: winbond: Add support for W25Q80BW
Quoted 21 lines · Jagannadha Sutradharudu Teki
Add support for Winbond W25Q80BW SPI flash.
This patch corrected the flash name,
nr_blocksand also commit message header from below patch. "sf: winbond: add W25Q32"
(sha1:c969abc47033d6f810d3c9dbdb994ea9d691d038)Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/winbond.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)drivers/mtd/spi/winbond.c +0
-0
drivers/mtd/spi/winbond.c static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { · line 91
Quoted 10 lines
drivers/mtd/spi/winbond.c +2
-2@@ -84,8 +84,8 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { }, { .id = 0x5014, - .nr_blocks = 128, - .name = "W25Q80", + .nr_blocks = 16, + .name = "W25Q80BW", }, { .id = 0x6016,
Applied to u-boot-spi/master
--
Thanks,
Jagan.
PATCH v2 4/8 sf: winbond: Correct the nr_blocks used for W25Q32DW
In reply to a message not in the archiveThis patch corrected the nr_blocks used for W25Q32DW SPI flash.
nr_blcoks are incorrectly assigned on below patch
"sf: winbond: add W25Q32DW"
(sha1: 772ba15474f73adc942e817cc072b6e9750836cc)
---
Changes for v2:
- none
drivers/mtd/spi/winbond.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mtd/spi/winbond.c +1 -1
@@ -89,7 +89,7 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { }, { .id = 0x6016, - .nr_blocks = 512, + .nr_blocks = 64, .name = "W25Q32DW", }, {
Signature · 1 line
1.8.3
PATCH v2 4/8 sf: winbond: Correct the nr_blocks used for W25Q32DW
Quoted 20 lines · Jagannadha Sutradharudu Teki
This patch corrected the
nr_blocksused for W25Q32DW SPI flash.
nr_blcoksare incorrectly assigned on below patch
"sf: winbond: add W25Q32DW"
(sha1:772ba15474f73adc942e817cc072b6e9750836cc)Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/winbond.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/mtd/spi/winbond.c +0
-0
drivers/mtd/spi/winbond.c static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { · line 95
Quoted 8 lines
drivers/mtd/spi/winbond.c +1
-1@@ -89,7 +89,7 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { }, { .id = 0x6016, - .nr_blocks = 512, + .nr_blocks = 64, .name = "W25Q32DW", }, {
Applied to u-boot-spi/master
--
Thanks,
Jagan.
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
In reply to a message not in the archiveUse the exact names for W25Q 0x40XX ID's flash parts, as the same sizes of flashes comes with different ID's. so-that the distinguishes becomes easy with this change.
---
Changes for v2:
- none
drivers/mtd/spi/winbond.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/mtd/spi/winbond.c +5 -5
@@ -55,27 +55,27 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { { .id = 0x4014, .nr_blocks = 16, - .name = "W25Q80BL", + .name = "W25Q80BL/W25Q80BV", }, { .id = 0x4015, .nr_blocks = 32, - .name = "W25Q16", + .name = "W25Q16CL/W25Q16DV", }, { .id = 0x4016, .nr_blocks = 64, - .name = "W25Q32", + .name = "W25Q32BV", }, { .id = 0x4017, .nr_blocks = 128, - .name = "W25Q64", + .name = "W25Q64CV", }, { .id = 0x4018, .nr_blocks = 256, - .name = "W25Q128", + .name = "W25Q128BV", }, { .id = 0x4019,
Signature · 1 line
1.8.3
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Hi,
Quoted 18 lines · Jagannadha Sutradharudu Teki
Use the exact names for W25Q 0x40XX ID's flash parts, as the same sizes of flashes comes with different ID's. so-that the distinguishes becomes easy with this change.
Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/winbond.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)drivers/mtd/spi/winbond.c +0
-0@@ -55,27 +55,27 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { {
drivers/mtd/spi/winbond.c static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { · line 63
Quoted 10 lines
drivers/mtd/spi/winbond.c +2
-2.id = 0x4014, .nr_blocks = 16, - .name = "W25Q80BL", + .name = "W25Q80BL/W25Q80BV", }, { .id = 0x4015, .nr_blocks = 32, - .name = "W25Q16", + .name = "W25Q16CL/W25Q16DV",
The id codes were same for these two parts, I think there is no way to detect the separately.
Any idea?
Thanks,
Jagan.
Quoted 25 lines
drivers/mtd/spi/winbond.c +3
-4}, { .id = 0x4016, .nr_blocks = 64, - .name = "W25Q32", + .name = "W25Q32BV", }, { .id = 0x4017, .nr_blocks = 128, - .name = "W25Q64", + .name = "W25Q64CV", }, { .id = 0x4018, .nr_blocks = 256, - .name = "W25Q128", + .name = "W25Q128BV", }, { .id = 0x4019, --1.8.3
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Hi Syed,
Quoted 28 lines · Jagan Teki
Hi,
Quoted 24 lines · Jagannadha Sutradharudu Teki
Use the exact names for W25Q 0x40XX ID's flash parts, as the same sizes of flashes comes with different ID's. so-that the distinguishes becomes easy with this change.
Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/winbond.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)drivers/mtd/spi/winbond.c +1
-1@@ -55,27 +55,27 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { { .id = 0x4014, .nr_blocks = 16, - .name = "W25Q80BL", + .name = "W25Q80BL/W25Q80BV", }, {
Quoted 8 lines
drivers/mtd/spi/winbond.c static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { · line 63
Quoted 4 lines
drivers/mtd/spi/winbond.c +1
-1.id = 0x4015, .nr_blocks = 32, - .name = "W25Q16", + .name = "W25Q16CL/W25Q16DV",The id codes were same for these two parts, I think there is no way to detect the separately.
Any idea?
Any comments on this.
--
Thanks,
Jagan.
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Copying Mike, Technical Marketing Director
-----Original Message-----
From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
Sent: Monday, June 03, 2013 11:03 PM
To: US30 Syed Hussain
Cc: u-boot at lists.denx.de; Michal Simek; Tom Rini; Simon Glass; Jagannadha Sutradharudu Teki
Subject: Re: [PATCH v2 5/8] sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Hi Syed,
Quoted 28 lines · Jagan Teki
Hi,
Quoted 24 lines · Jagannadha Sutradharudu Teki
Use the exact names for W25Q 0x40XX ID's flash parts, as the same sizes of flashes comes with different ID's. so-that the distinguishes becomes easy with this change.
Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/winbond.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)drivers/mtd/spi/winbond.c +1
-1@@ -55,27 +55,27 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { { .id = 0x4014, .nr_blocks = 16, - .name = "W25Q80BL", + .name = "W25Q80BL/W25Q80BV", }, {
Quoted 8 lines
drivers/mtd/spi/winbond.c static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { · line 63
Quoted 4 lines
drivers/mtd/spi/winbond.c +1
-1.id = 0x4015, .nr_blocks = 32, - .name = "W25Q16", + .name = "W25Q16CL/W25Q16DV",The id codes were same for these two parts, I think there is no way to detect the separately.
Any idea?
Any comments on this.
--
Thanks,
Jagan.
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Jagan,
So far, our major customer request is to have the same ID for backward compatibility. Therefore the IDs are the same for W25Q16C and W25Q16D. As for the 2.5V parts (W25Q80BL/W25Q16CL), they are the same die as the 3V (W25Q80BV/W25Q16CV), so the IDs are the same as well.
The differences between the pairs are not that significant. We consider them as drop-in compatible.
Best Regards,
Mike Chen
Technical Marketing
Winbond Electronics Corp. America
(408)544-2667
-----Original Message-----
From: US30 Syed Hussain
Sent: Tuesday, June 04, 2013 10:12 AM
To: Jagan Teki; US20 Hui (Mike) Chen
Cc: u-boot at lists.denx.de; Michal Simek; Tom Rini; Simon Glass; Jagannadha Sutradharudu Teki
Subject: RE: [PATCH v2 5/8] sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Copying Mike, Technical Marketing Director
-----Original Message-----
From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
Sent: Monday, June 03, 2013 11:03 PM
To: US30 Syed Hussain
Cc: u-boot at lists.denx.de; Michal Simek; Tom Rini; Simon Glass; Jagannadha Sutradharudu Teki
Subject: Re: [PATCH v2 5/8] sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Hi Syed,
Quoted 28 lines · Jagan Teki
Hi,
Quoted 24 lines · Jagannadha Sutradharudu Teki
Use the exact names for W25Q 0x40XX ID's flash parts, as the same sizes of flashes comes with different ID's. so-that the distinguishes becomes easy with this change.
Signed-off-by Jagannadha Sutradharudu Teki <[email protected]>---
Changes for v2:
- nonedrivers/mtd/spi/winbond.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)drivers/mtd/spi/winbond.c +1
-1@@ -55,27 +55,27 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { { .id = 0x4014, .nr_blocks = 16, - .name = "W25Q80BL", + .name = "W25Q80BL/W25Q80BV", }, {
Quoted 8 lines
drivers/mtd/spi/winbond.c static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { · line 63
Quoted 4 lines
drivers/mtd/spi/winbond.c +1
-1.id = 0x4015, .nr_blocks = 32, - .name = "W25Q16", + .name = "W25Q16CL/W25Q16DV",The id codes were same for these two parts, I think there is no way to detect the separately.
Any idea?
Any comments on this.
--
Thanks,
Jagan.
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Quoted 5 lines · On Tue, Jun 4, 2013 at 10:49 PM, MCHEN4 at winbond.com <[email protected]>…
Jagan,
So far, our major customer request is to have the same ID for backward compatibility. Therefore the IDs are the same for W25Q16C and W25Q16D. As for the 2.5V parts (W25Q80BL/W25Q16CL), they are the same die as the 3V (W25Q80BV/W25Q16CV), so the IDs are the same as well.
The differences between the pairs are not that significant. We consider them as drop-in compatible.
Ok, thanks for your response.
And are your ok with below representation for common id's parts ?
+ .name = "W25Q80BL/W25Q80BV", + .name = "W25Q16CL/W25Q16DV", + .name = "W25Q32BV/W25Q32FV_SPI", + .name = "W25Q64CV/W25Q64FV_SPI", + .name = "W25Q128BV/W25Q128FV_SPI", + .name = "W25Q32DW/W25Q32FV_QPI", + .name = "W25Q64DW/W25Q64FV_QPI", + .name = "W25Q128FW/W25Q128FV_QPI",
--
Thanks,
Jagan.
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Jagan,
Yes, it is OK. Of course, the 3V QPI IDs of W25Q32FV/64FV/128FV are identical to that of the 1.8V devices (W25Q32DW/64DW/128FW). It may not be a good idea but it's too late for us to change.
Best Regards,
Mike Chen
Technical Marketing
Winbond Electronics Corp. America
(408)544-2667
-----Original Message-----
From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
Sent: Tuesday, June 04, 2013 10:26 AM
To: US20 Hui (Mike) Chen
Cc: US30 Syed Hussain; u-boot at lists.denx.de; Michal Simek; Tom Rini; Simon Glass; Jagannadha Sutradharudu Teki
Subject: Re: [PATCH v2 5/8] sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Quoted 5 lines · On Tue, Jun 4, 2013 at 10:49 PM, MCHEN4 at winbond.com <[email protected]>…
Jagan,
So far, our major customer request is to have the same ID for backward compatibility. Therefore the IDs are the same for W25Q16C and W25Q16D. As for the 2.5V parts (W25Q80BL/W25Q16CL), they are the same die as the 3V (W25Q80BV/W25Q16CV), so the IDs are the same as well.
The differences between the pairs are not that significant. We consider them as drop-in compatible.
Ok, thanks for your response.
And are your ok with below representation for common id's parts ?
+ .name = "W25Q80BL/W25Q80BV", + .name = "W25Q16CL/W25Q16DV", + .name = "W25Q32BV/W25Q32FV_SPI", + .name = "W25Q64CV/W25Q64FV_SPI", + .name = "W25Q128BV/W25Q128FV_SPI", + .name = "W25Q32DW/W25Q32FV_QPI", + .name = "W25Q64DW/W25Q64FV_QPI", + .name = "W25Q128FW/W25Q128FV_QPI",
--
Thanks,
Jagan.
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
A message that is not in the archive (sent off-list or not yet received): CAD6G_RQ6efJce77bvSUrVsb9aBoJorE+czunUoVZ3Ad7wLeoJQ@mail.gmail.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): CAD6G_RSbR9PVB5HMHoQiV86MqZ87JeDjpDoRrC9pZQVNg-jjGw@mail.gmail.com
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
move this discussion back to mailing list.
Quoted 16 lines · Jagan Teki
Quoted 16 lines
Quoted 15 lines
Review
Quoted 9 lines
And are your ok with below representation for common id's parts ?
(quoted diff) +8
-0+ .name = "W25Q80BL/W25Q80BV", + .name = "W25Q16CL/W25Q16DV", + .name = "W25Q32BV/W25Q32FV_SPI", + .name = "W25Q64CV/W25Q64FV_SPI", + .name = "W25Q128BV/W25Q128FV_SPI", + .name = "W25Q32DW/W25Q32FV_QPI", + .name = "W25Q64DW/W25Q64FV_QPI", + .name = "W25Q128FW/W25Q128FV_QPI",Any comments on above representation of part names, as the id's to these pairs are common.
This will enhance u-boot sf to support all parts from winbond, but seems like different view of names.
Quoted 4 lines
Quoted 1 line
what's the difference between that parts?
parts were diff in terms of voltages and sone SPI and QPI configurations. but from the manufacture defeat, pair of parts were same ID's
ok.
Quoted 6 lines
Quoted 3 lines
Does software care if it is W25G80BL or BV?
Or software behaviour is the same and there is only difference in voltage or so.SW is same even if it 1.8 or 3.3 v.
The only reason for giving the pair of names to support all different parts
You are supporting them but you are just not list them.
Quoted 4 lines
Quoted 1 line
I don't care about it so much but it is increase u-boot size.
Why does u-boot size increase, is it because of below representation on name filed
= "W25Q80BL/W25Q80BV"
Just because of longer names which go probably to rodata section.
It is not a problem for me at all.
Thanks,
Michal
Signature · 14 lines
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/ Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 263 bytes Desc: OpenPGP digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130606/18ddcec5/attachment.pgp>
PATCH v2 5/8 sf: winbond: Update the names for W25Q 0x40XX ID's flash parts
Quoted 35 lines · Michal Simek
move this discussion back to mailing list.
Quoted 16 lines · Jagan Teki
Quoted 16 lines
Quoted 15 lines
Review
Quoted 9 lines
And are your ok with below representation for common id's parts ?
(quoted diff) +8
-0+ .name = "W25Q80BL/W25Q80BV", + .name = "W25Q16CL/W25Q16DV", + .name = "W25Q32BV/W25Q32FV_SPI", + .name = "W25Q64CV/W25Q64FV_SPI", + .name = "W25Q128BV/W25Q128FV_SPI", + .name = "W25Q32DW/W25Q32FV_QPI", + .name = "W25Q64DW/W25Q64FV_QPI", + .name = "W25Q128FW/W25Q128FV_QPI",Any comments on above representation of part names, as the id's to these pairs are common.
This will enhance u-boot sf to support all parts from winbond, but seems like different view of names.Quoted 4 lines
Quoted 1 line
what's the difference between that parts?
parts were diff in terms of voltages and sone SPI and QPI configurations. but from the manufacture defeat, pair of parts were same ID's
ok.
Quoted 6 lines
Quoted 3 lines
Does software care if it is W25G80BL or BV?
Or software behaviour is the same and there is only difference in voltage or so.SW is same even if it 1.8 or 3.3 v.
The only reason for giving the pair of names to support all different partsYou are supporting them but you are just not list them.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
I don't care about it so much but it is increase u-boot size.
Why does u-boot size increase, is it because of below representation on name filed
= "W25Q80BL/W25Q80BV"Just because of longer names which go probably to rodata section.
It is not a problem for me at all.
OK, I can go ahead to applied these.
Let me know for any more concerns.
--
Thanks,
Jagan.
PATCH v2 6/8 sf: winbond: Add support for W25Q128FW
In reply to a message not in the archiveAdd support for Winbond W25Q128FW SPI flash.
---
Changes for v2:
- none
drivers/mtd/spi/winbond.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/mtd/spi/winbond.c +5 -0
@@ -97,6 +97,11 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { .nr_blocks = 128, .name = "W25Q64DW", }, + { + .id = 0x6018, + .nr_blocks = 256, + .name = "W25Q128FW", + }, };struct spi_flash *spi_flash_probe_winbond (struct spi_slave *spi,u8 *idcode)
Signature · 1 line
1.8.3
PATCH v2 7/8 sf: winbond: Add support for W25Q16DW
In reply to a message not in the archiveAdd support for Winbond W25Q16DW SPI flash.
---
Changes for v2:
- none
drivers/mtd/spi/winbond.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/mtd/spi/winbond.c +5 -0
@@ -88,6 +88,11 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { .name = "W25Q80BW", }, { + .id = 0x6015, + .nr_blocks = 32, + .name = "W25Q16DW", + }, + { .id = 0x6016, .nr_blocks = 64, .name = "W25Q32DW",
Signature · 1 line
1.8.3
PATCH v2 8/8 sf: winbond: Add support for W25QXXXFV
In reply to a message not in the archiveAdd support for Winbond W25QXXXFV SPI flash.
---
Changes for v2:
- none
drivers/mtd/spi/winbond.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/mtd/spi/winbond.c +6 -6
@@ -65,17 +65,17 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { { .id = 0x4016, .nr_blocks = 64, - .name = "W25Q32BV", + .name = "W25Q32BV/W25Q32FV_SPI", }, { .id = 0x4017, .nr_blocks = 128, - .name = "W25Q64CV", + .name = "W25Q64CV/W25Q64FV_SPI", }, { .id = 0x4018, .nr_blocks = 256, - .name = "W25Q128BV", + .name = "W25Q128BV/W25Q128FV_SPI", }, { .id = 0x4019,
@@ -95,17 +95,17 @@ static const struct winbond_spi_flash_params winbond_spi_flash_table[] = { { .id = 0x6016, .nr_blocks = 64, - .name = "W25Q32DW", + .name = "W25Q32DW/W25Q32FV_QPI", }, { .id = 0x6017, .nr_blocks = 128, - .name = "W25Q64DW", + .name = "W25Q64DW/W25Q64FV_QPI", }, { .id = 0x6018, .nr_blocks = 256, - .name = "W25Q128FW", + .name = "W25Q128FW/W25Q128FV_QPI", }, };
Signature · 1 line
1.8.3