RE: usb: typec: driver for TI HD3SS3220 USB Type-C DRP port controller question

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

 



Hi Biju,

On 21 June 2022 09:40 Biju Das wrote:
> > On 21 June 2022 08:23 Heikki Krogerus wrote:
> > > On Mon, Jun 20, 2022 at 09:04:10AM +0000, Phil Edworthy wrote:
> > > > Hi Heikki,
> > > >
> > > > I have a board that uses the TI HD3SS3220 USB Type-C DRP port
> > > > controller [1], however it doesn't have the interrupt line
> > > > connected. How would you recommend I handle this? Should I get the
> > > > driver to poll the i2c registers?
> > > >
> > > > [1]
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/t
> > > > ree/drivers/usb/typec/hd3ss3220.c?h=v5.19-rc3
> > >
> > > If you have some other way of detecting connections on your system,
> > > then we probable could consider some kind of notifier, but as a
> > > general solution for the lack of interrupt, I think polling is the
> > > only way.
> > Thanks for your comments.
> >
> > I wonder if this is a problem that affects quite a few drivers, where a
> > generic polling solution can be used instead of interrupts. This would
> > require a driver-specific function that can detect when an interrupt
> > would have occurred, e.g. by reading a register via i2c.
> > This is already done like that for ethernet PHY interrupts.
> 
> You mean like PHY at subsystem level, check IRQ is present in dt or not?,
> if present use IRQ otherwise
> Use polling.
Indeed, but something that could be used for _all_ i2c devices.
 
Thanks
Phil




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

  Powered by Linux