[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fw: Why cannot Target change its mind
----- Original Message -----
From: "Gérard Roudier" <groudier@club-internet.fr>
To: "Weng" <wtx@umem.com>
Cc: <pci-sig@znyx.com>
Sent: Friday, April 13, 2001 1:42 PM
Subject: Re: Why cannot Target change its mind
>
>
> On Fri, 13 Apr 2001, Weng wrote:
>
> > Hi,
> > PCI 2.2 p.53: Once a target has asserted TRDY# or STOP#, it cannot
change DEVSEL#, TRDY#, or STOP# until the current data phase completes.
> >
> > I have two questions about the above definition.
> >
> > The reason that DEVSEL# and STOP# cannot be changed is clear, I don't
see any merit why TRDY# cannot be changed if Target found Master is
asserting wait cycles and it wants to change mind too.
> >
> > 1. On what senerio the changing TRDY# signal will have permanent damage
to any transactions?
>
> I imagine that this allows the other part (the master) to anticipate the
> data phase, if such anticipation can optimize the data transfer, and avoid
> side effects without too much complexity.
> Anyway, such behaviour by the target might lead to bus cycles wastage or,
> for example, let the master (some kind of bridge for example) prefetch
> data and throw them away...
>
> > When I have been designing Master module, I don't see any difference in
design whether or not PCI-Target is changing its mind. The only logic that
go into my design is IRDY# = '0' and (TRDY# = '0' or STOP# = '0'), that
means only when both Master and Target agree with a transaction, the deal is
made, otherwise wait until the above conditions happen.
> >
> > 2. While not allowing Target to change its mind, why there is no
symmetrical limit on Master side, that is, on IRDY#?
>
> In my opinion you misread the specs here. The assertion of IRDY# must also
> be considered as a commitment for a data phase by the master as seen by
> the target. In this situation, catastroph may happen if the master wants
> to read to non-prefetchable and then changes its mind, since the target
> may have read the data (with side effect) and then will not be able to
> deliver it to the master.
>
> > My opinion is: (a relaxed condition that is good enough to match
original definition)
> > Once a target has asserted DEVSEL# or STOP#, it must be asserted until a
transaction is finished. Data is transfered only on conditions that IRDY# =
'0' and TRDY# = '0'. Target can change TRDY# state if no data is transfered.
>
> You should forget about such suggestion, in my opinion.
>
> > Weng Tianxiang
> >
> > wtx@umem.com
> > wengtianxiang@yahoo.com
> >
> > Micro Memory Inc.
> > 9540 Vassar Avenue
> > Chartsworth, CA 91311
> > Tel: 818-998-0070
> > Fax: 818-998-4459
>
> Gérard.
>
>