USB controller status

[Praveen kumar]

Hi Greg,

What type of diagnostics are you trying to do?
           I am trying to is to make communication to all the chips present
on board (from kernel) and make sure all the input/output lines are working
on that chip and the status of the configuration.
As I am doing with the other chips like video controller ,audio controller
etc ,I want to make sure the working condition of the USB controller and
some tests to prove input and output lines are working and if possible loop
back data test.

How can it not be configured correctly?

I am not sure in which condition the configuration of controller may fail
but just I want to make sure the controller is configured properly.

You have looked at the debugfs files for the usb controllers for this
type of thing already, right?

I have seen debugfs where I can dump all the configuration reg values ,but
not sure to see which reg values to confirm  controller is configured
properly.

Also I was trying to get the linux-usb project (
http://sourceforge.net/apps/trac/sourceforge/wiki/Git) through git to make
use of some code in there for some of the tests but I am not able to get it.
Is there any alternative link from where I can get the code (like lsusb.c
etc )..

Thanks ,
Praveen




On Mon, Jan 16, 2012 at 11:07 PM, Greg KH <greg at kroah.com> wrote:

> On Mon, Jan 16, 2012 at 04:15:09PM +0530, Praveen kumar wrote:
> > Hi All,
> >         As part of diagnostics  I have to make sure the USB controller is
> > configured correctly.
>
> How can it not be configured correctly?
>
> > Can I get this information from any entry in /sys or /proc ?? If yes
> where ??
> > If no I plan to add a exclusive entry in the driver to do my diagnostics.
>
> What type of diagnostics are you trying to do?
>
> > Is that feasible by reading some of the registers in
> > the controller ??
>
> You have looked at the debugfs files for the usb controllers for this
> type of thing already, right?
>
> greg k-h
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120117/990ed4a0/attachment.html