[PATCH 2/2] USB: isp1760: Support board-specific hardware configurations

Nathaniel Case ncase at xes-inc.com
Fri May 23 13:28:37 EST 2008

On Thu, 2008-05-22 at 17:35 +0200, Sebastian Siewior wrote:
> If you don't mind, I would prefer having ISP1760_FLAG_BUS_WIDTH_32 and
> or conditionally HW_DATA_BUS_32BIT.

It doesn't matter much to me -- I just reasoned that a 32-bit bus width
was the norm since it's the hardware default and so having a flags=0
would be desirable for that case.  Did you have something else in mind?

> Why do you have to read the chip id here? Is this a dummy read to ensure
> something?

The idea is to force the data bus lines to change states to protect
against a false success.  E.g., you read back 0xdeadbabe but it was due
to the line states from the previous write rather than coming from the
chip itself (I've seen this when you get the bus chip select or timing
configuration wrong). 

> I'm sorry, you can't solve this way. My ISP1760 claims to be an ISP1761
> this way :) So I end up with one functional port... The only way to
> distinguish between 1760 & 1761 would be at the probing level.

Yikes -- you're right.  I would have never guessed that the 1760 would
have returned 0x1761, but sure enough that's what the datasheet says.

Thanks for the feedback.

Nate Case <ncase at xes-inc.com>

More information about the Linuxppc-dev mailing list