All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stanisław Gruszka" <stf_xl@wp.pl>
To: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: Igor Plyatov <plyatov@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ATA: pata_at91.c bugfixes
Date: Fri, 29 Apr 2011 09:56:54 +0200	[thread overview]
Message-ID: <4dba6f46587df2.89235609@wp.pl> (raw)
In-Reply-To: <1303299877-12088-1-git-send-email-plyatov@gmail.com> <20110423093623.GA3410@localhost.localdomain> <4DB6684C.7050505@gmail.com> <20110427183819.GA2285@localhost.localdomain>

> > * The NCS_RD_CYCLE is equal to the NRD_CYCLE for AT91SAM9, because they
> >   start/finish simultaneously (HW related).
> No, NCS and NRD are different signals, waveforms are different (if 
> configured differently in SMC controller).
Your sentence is true. NRD and NCS cycle time must be the same (otherwise
SMC behaviour is undefined), hence both signals start/finish simultaneously.
Anyway waveforms (setup, and pulse time) can be different. All of thise
are kinda obvious, no? :-)

Stanislaw



  reply	other threads:[~2011-04-29  7:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 11:44 [PATCH] ATA: pata_at91.c bugfixes Igor Plyatov
2011-04-23  9:36 ` Stanislaw Gruszka
2011-04-26  6:38   ` Igor Plyatov
2011-04-27 18:38     ` Stanislaw Gruszka
2011-04-29  7:56       ` Stanisław Gruszka [this message]
     [not found]       ` <4DBA9E2F.3070100@gmail.com>
2011-05-01 21:17         ` Stanislaw Gruszka
2011-05-12 12:03           ` Igor Plyatov
2011-04-24 15:35 ` Jeff Garzik
2011-05-12 12:05   ` 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=4dba6f46587df2.89235609@wp.pl \
    --to=stf_xl@wp.pl \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plyatov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.