From: Bartlomiej Sieka <tur@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] CFI: synchronize command offsets with Linux CFI driver
Date: Tue, 11 Dec 2007 15:25:25 +0100 [thread overview]
Message-ID: <475E9DD5.3040108@semihalf.com> (raw)
In-Reply-To: <200712111511.49605.sr@denx.de>
Stefan Roese wrote:
[...]
>> diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
>> index 66754cd..b748a9f 100644
>> --- a/drivers/mtd/cfi_flash.c
>> +++ b/drivers/mtd/cfi_flash.c
>> @@ -1231,9 +1231,26 @@ static int flash_detect_cfi (flash_info_t * info)
>> debug ("port %d bits chip %d bits\n",
>> info->portwidth << CFI_FLASH_SHIFT_WIDTH,
>> info->chipwidth << CFI_FLASH_SHIFT_WIDTH);
>> - /* this probably only works if info->interface == FLASH_CFI_X8X16 */
>> - info->addr_unlock1 = (info->portwidth == FLASH_CFI_8BIT) ? 0xAAA :
>> 0x555; - info->addr_unlock2 = (info->portwidth == FLASH_CFI_8BIT) ?
>> 0x555 : 0x2AA; +
>> + /* calculate command offsets as in the Linux driver */
>> + info->addr_unlock1 = 0x555;
>> + info->addr_unlock2 = 0x2aa;
>> +
>> + /*
>> + * modify the unlock address if we are
>> + * in compatibility mode
>> + */
>> + if ( /* x8/x16 in x8 mode */
>> + ((info->chipwidth == FLASH_CFI_BY8) &&
>> + (info->interface == FLASH_CFI_X8X16)) ||
>> + /* x16/x32 in x16 mode */
>> + ((info->chipwidth == FLASH_CFI_BY16) &&
>> + (info->interface == FLASH_CFI_X16X32)))
>> + {
>> + info->addr_unlock1 = 0xaaa;
>> + info->addr_unlock2 = 0x555;
>> + }
>> +
>
> Why not like this:
>
> if (((info->chipwidth == FLASH_CFI_BY8) &&
> (info->interface == FLASH_CFI_X8X16)) ||
> ((info->chipwidth == FLASH_CFI_BY16) &&
> (info->interface == FLASH_CFI_X16X32))) {
> /*
> * Compatibility mode:
> * x8/x16 in x8 mode or
> * x16/x32 in x16 mode
> */
> info->addr_unlock1 = 0xaaa;
> info->addr_unlock2 = 0x555;
> } else {
> /* default */
> info->addr_unlock1 = 0x555;
> info->addr_unlock2 = 0x2aa;
> }
I copied the code from Linux CFI driver and kept it as is (modulo
#define names). I'm fine with either of the two forms, although I think
that there is some benefit in keeping borrowed code as intact as possible.
Regards,
Bartlomiej
next prev parent reply other threads:[~2007-12-11 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 12:59 [U-Boot-Users] [PATCH] CFI: synchronize command offsets with Linux CFI driver Bartlomiej Sieka
2007-12-11 14:11 ` Stefan Roese
2007-12-11 14:25 ` Bartlomiej Sieka [this message]
2007-12-11 14:37 ` Stefan Roese
2007-12-21 7:58 ` Hoi-Ho Chan
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=475E9DD5.3040108@semihalf.com \
--to=tur@semihalf.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