From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Igor Plyatov <plyatov@gmail.com>
Cc: sshtylyov@mvista.com, jgarzik@pobox.com,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
geomatsi@gmail.com, nicolas.ferre@atmel.com, linux@maxim.org.za,
linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk,
christian.glindkamp@taskit.de, ryan@bluewatersys.com,
pgsellmann@portner-elektronik.at
Subject: Re: [PATCH v2] ide: at91_ide.c bugfix for high master clock
Date: Mon, 13 Dec 2010 22:35:49 +0100 [thread overview]
Message-ID: <20101213213549.GA2077@r2bh72.net.upc.cz> (raw)
In-Reply-To: <1292100326-637-1-git-send-email-plyatov@gmail.com>
On Sat, Dec 11, 2010 at 11:45:26PM +0300, Igor Plyatov wrote:
> The AT91SAM9 microcontrollers with master clock higher then 105 MHz
> and PIO0, have overflow of the NCS_RD_PULSE value in the MSB. This
> lead to "NCS_RD_PULSE" pulse longer then "NRD_CYCLE" pulse and driver
> does not detect IDE device.
The overflow happens because MSB (bit 6) is multiplied by 256.
NCS pulse length = 256*NCS_RD_PULSE[6] + NCS_RD_PULSE[5:0] clock
cycles. So NCS_RD_PULSE 0x41 gives 257 clock cycles not 65 as we
expected before. Static memory controller behaviour is undefined
when pulse length is bigger than cycle length, so things not work.
> + u16 ncs_rd_pulse;
> unsigned long mode = AT91_SMC_READMODE | AT91_SMC_WRITEMODE |
> AT91_SMC_BAT_SELECT;
>
> @@ -81,19 +84,29 @@ static void set_smc_timings(const u8 chipselect, const u16 cycle,
> if (data_float)
> mode |= AT91_SMC_TDF_(data_float);
>
> + ncs_rd_pulse = cycle;
> + if (ncs_rd_pulse > NCS_RD_PULSE_LIMIT) {
> + ncs_rd_pulse = NCS_RD_PULSE_LIMIT;
> + pr_warn(DRV_NAME ": ncs_rd_pulse limited to maximal value %d\n",
> + ncs_rd_pulse);
> + }
I'm fine with that fix. We can possibly still have problems with higher
frequencies, but I'm not sure if someone will use that hardware with
faster clocks.
Thanks
Stanislaw
next prev parent reply other threads:[~2010-12-13 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 20:45 Igor Plyatov
2010-12-13 21:35 ` Stanislaw Gruszka [this message]
2010-12-16 23:51 ` Stanislaw Gruszka
2011-04-20 11:54 ` Igor Plyatov
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=20101213213549.GA2077@r2bh72.net.upc.cz \
--to=stf_xl@wp.pl \
--cc=christian.glindkamp@taskit.de \
--cc=geomatsi@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=pgsellmann@portner-elektronik.at \
--cc=plyatov@gmail.com \
--cc=ryan@bluewatersys.com \
--cc=sshtylyov@mvista.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
all inboxes | Powered by JetHome®