From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
arm-linux <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] GPMC: add ECC control definitions
Date: Thu, 08 Mar 2012 12:10:31 +0100 [thread overview]
Message-ID: <4F5893A7.2070909@visionsystems.de> (raw)
In-Reply-To: <20120305230334.GM12083@atomide.com>
Am 06.03.2012 00:03, schrieb Tony Lindgren:
> * Yegor Yefremov <yegor_sub1@visionsystems.de> [120123 03:33]:
>> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
>> ---
>> arch/arm/mach-omap2/gpmc.c | 30 +++++++++++++++++++++++++-----
>> 1 file changed, 25 insertions(+), 5 deletions(-)
>>
>> Index: b/arch/arm/mach-omap2/gpmc.c
>> ===================================================================
>> --- a/arch/arm/mach-omap2/gpmc.c
>> +++ b/arch/arm/mach-omap2/gpmc.c
>> @@ -50,6 +50,19 @@
>> #define GPMC_ECC_SIZE_CONFIG 0x1fc
>> #define GPMC_ECC1_RESULT 0x200
>>
>> +/* GPMC ECC control settings */
>> +#define GPMC_ECC_CTRL_ECCCLEAR 0x100
>> +#define GPMC_ECC_CTRL_ECCDISABLE 0x000
>> +#define GPMC_ECC_CTRL_ECCREG1 0x001
>> +#define GPMC_ECC_CTRL_ECCREG2 0x002
>> +#define GPMC_ECC_CTRL_ECCREG3 0x003
>> +#define GPMC_ECC_CTRL_ECCREG4 0x004
>> +#define GPMC_ECC_CTRL_ECCREG5 0x005
>> +#define GPMC_ECC_CTRL_ECCREG6 0x006
>> +#define GPMC_ECC_CTRL_ECCREG7 0x007
>> +#define GPMC_ECC_CTRL_ECCREG8 0x008
>> +#define GPMC_ECC_CTRL_ECCREG9 0x009
>> +
>> #define GPMC_CS0_OFFSET 0x60
>> #define GPMC_CS_SIZE 0x30
>>
>> @@ -855,8 +868,9 @@
>> gpmc_ecc_used = cs;
>>
>> /* clear ecc and enable bits */
>> - val = ((0x00000001<<8) | 0x00000001);
>> - gpmc_write_reg(GPMC_ECC_CONTROL, val);
>> + gpmc_write_reg(GPMC_ECC_CONTROL,
>> + GPMC_ECC_CTRL_ECCCLEAR |
>> + GPMC_ECC_CTRL_ECCREG1);
>>
>> /* program ecc and result sizes */
>> val = ((((ecc_size >> 1) - 1) << 22) | (0x0000000F));
>> @@ -864,13 +878,19 @@
>>
>> switch (mode) {
>> case GPMC_ECC_READ:
>> - gpmc_write_reg(GPMC_ECC_CONTROL, 0x101);
>> + gpmc_write_reg(GPMC_ECC_CONTROL,
>> + GPMC_ECC_CTRL_ECCCLEAR |
>> + GPMC_ECC_CTRL_ECCREG1);
>> break;
>> case GPMC_ECC_READSYN:
>> - gpmc_write_reg(GPMC_ECC_CONTROL, 0x100);
>> + gpmc_write_reg(GPMC_ECC_CONTROL,
>> + GPMC_ECC_CTRL_ECCCLEAR |
>> + GPMC_ECC_CTRL_ECCDISABLE);
>> break;
>> case GPMC_ECC_WRITE:
>> - gpmc_write_reg(GPMC_ECC_CONTROL, 0x101);
>> + gpmc_write_reg(GPMC_ECC_CONTROL,
>> + GPMC_ECC_CTRL_ECCCLEAR |
>> + GPMC_ECC_CTRL_ECCREG1);
>> break;
>> default:
>> printk(KERN_INFO "Error: Unrecognized Mode[%d]!\n", mode);
>>
> No functional changes here, right?
>
> Can GPMC_ECC_READ and GPMC_ECC_WRITE case be combined:
>
> switch (mode) {
> case GPMC_ECC_READ:
> case GPMC_ECC_WRITE:
> gpmc_write_reg(GPMC_ECC_CONTROL,
> GPMC_ECC_CTRL_ECCCLEAR |
> GPMC_ECC_CTRL_ECCREG1);
> break;
> ...
You are right. path v2 already sent.
Thanks for review.
Best regards,
Yegor
prev parent reply other threads:[~2012-03-08 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 12:04 [PATCH] GPMC: add ECC control definitions Yegor Yefremov
2012-03-05 23:03 ` Tony Lindgren
2012-03-08 11:10 ` Yegor Yefremov [this message]
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=4F5893A7.2070909@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).