Hi Tim,<br>Thank you for your reply.<br><br>Yes our driver is taking care. Driver supports two ERV values: <br>1. nibble (0x00) and 2. device ID with nibble mode (0x04).<br><br>Actually, the negotiation is passed for the nibble mode (0x00) and is performing rev.<br>
data transfer successfully.<br><br>But, for device ID request, it is not the case, though the code execution path is same<br>for both of them.<br><br>I could get the printk of ERV value - 0x04. and doing the following events:<br>
<br>1. set event 5 (Set XFlag, nDataAvail, PError low)<br>2. set event 6 (Set nAck high)<br>3. Wait for event 7 (HostBusy go low)<br>4. Data transfer phase<br><br>Above is the same sequence of execution even for the nibble mode data transfer.<br>
Nibble mode data transfer is working fine.<br><br>regards,<br>-Nagesh A<br><br><div class="gmail_quote">On Thu, Jul 28, 2011 at 3:36 PM, Tim Waugh <span dir="ltr"><<a href="mailto:twaugh@redhat.com">twaugh@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Thu, 2011-07-28 at 14:41 +0530, Nagesh A wrote:<br>
> Currently my driver at device side, supports compatibility mode and<br>
> nibble mode, and<br>
> working fine with data transfers in both directions.<br>
<br>
</div>To fetch the Device ID, the host sets bit 2 of the extensibility request<br>
value byte during negotiation (i.e. the byte placed on the data bits<br>
when nSelectIn/nAutoFd are toggled).<br>
<br>
Is your device watching for that?<br>
<br>
Tim.<br>
*/<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br><i style="font-family:garamond,serif;color:rgb(51, 51, 51)">regards,</i><div style="font-family:garamond,serif;color:rgb(51, 51, 51)"><i>-Nagesh A</i></div><br>