Re: [RFC 11/17] usb/ehci: make au1xxx use generic add code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 29, 2011 at 03:31:42PM +0530, ABRAHAM, KISHON VIJAY wrote:
> > Is there a way that I can know this upfront? Like a flag somewhere or an
> > assigned callback which isn't there otherwise?
> 
> maybe we can add a .irqflag member in hc_driver?

not int hc_driver. I want to have one struct which can be shared along all
ehci drivers so extra fields which are unique to the platform / board in
there are a no-no.
If I get get many config arguments like this I may introduce a config struct
which covers all of them.

What I see right now is
- tt, big endian register and such
- clocks
- phy setup
- register offset (sometimes at 0x0 sometimes + 0x100). This however could be
  solved by moving the chip address +0x100. I haven't seen this registers beeing
  used. One driver claimed that this are "debug" registers so someone might
  want to use them, dunno.

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux