Re: What breaks aic7xxx in post 2.6.12-rc2 ?

K.R. Foley
2005-05-20T01:32:28Z

James Bottomley wrote:
> On Thu, 2005-05-19 at 20:05 -0500, K.R. Foley wrote:
>
>>It does work with the exception that my u160 drive is still identified
>>as 80MB/s.
>
>
> Well, that's some good news, at least.
>
>
>>May 19 19:36:46 porky kernel: scsi0:A:0:0: Tagged Queuing enabled. Depth 32
>>May 19 19:36:46 porky kernel: target0:0:0: Beginning Domain Validation
>>May 19 19:36:46 porky kernel: WIDTH IS 1
>>May 19 19:36:46 porky kernel: (scsi0:A:0): 6.600MB/s transfers (16bit)
>>May 19 19:36:46 porky kernel: (scsi0:A:0): 80.000MB/s transfers
>>(40.000MHz, offset 127, 16bit)
>
>
> OK, it looks like the period is limited to 25ns. Could you confirm
> this?
>
> cat /sys/class/spi_transport/target0:0:0/period

this is 25

> cat /sys/class/spi_transport/target0:0:0/max_period

this doesn't exist, but i bet you knew that

>
> Now, if the max_period is 25, try doing
>
> echo 12.5 > /sys/class/spi_transport/target0:0:0/max_period

actually put this into period but it didn't take :-( period is still 25
and before you ask min_period is 12.5

>
> and then
>
> echo 1 > /sys/class/spi_transport/target0:0:0/revalidate

did this anyway and this is what i got

May 19 20:21:45 porky kernel: target0:0:0: Beginning Domain Validation
May 19 20:21:45 porky kernel: (scsi0:A:0): 3.300MB/s transfers
May 19 20:21:45 porky kernel: WIDTH IS 1
May 19 20:21:46 porky kernel: (scsi0:A:0): 6.600MB/s transfers (16bit)
May 19 20:21:46 porky kernel: (scsi0:A:0): 80.000MB/s transfers
(40.000MHz, offset 127, 16bit)
May 19 20:21:46 porky kernel: target0:0:0: Ending Domain Validation

Any idea why I can't set the period to 12.5? I am going to see if
anything jumps out at me.

>
> to trigger a revalidation of the domain and see if it comes up to 160.
>
> Thanks,
>
> James
>
>
>

--
kr