Hi, >-----Original Message----- >From: Balbi, Felipe >Sent: Thursday, October 07, 2010 4:56 PM >To: Kalliguddi, Hema >Cc: Balbi, Felipe; David Brownell; >dbrownell@xxxxxxxxxxxxxxxxxxxxx; Arnaud Mandy; >felipe.balbi@xxxxxx; linux-usb@xxxxxxxxxxxxxxx >Subject: Re: [PATCH 2/2] usb: otg: introduce otg_notify_event >and otg_get_last_event > >Hi, > >On Thu, Oct 07, 2010 at 06:21:15AM -0500, Kalliguddi, Hema wrote: >>I am talking about USB PRESENCE IRQ itself can be turned on >only whn required. > >and which information you have to turn that on ? That's not part of the >USB block on twl* either. > >>I am talking about TWL4030 VBUS and ID_GND IRQs. > >That's not part of the USB block, right ? It's the USB PRESENCE IRQ, to >differentiate between VBUS and ID, we read the link status and >decide if >it's IRQ due id ground or VBUS. > Correct, so let's enable this VBUS PRESENCE IRQ in otg_init function which will be called during gadget driver load. And call the VBUS PRESENCE irq handler to capture the status and send the notifications. >Let's say we disable that logic. What will we use to detect a USB cable >attach ? > The status will be logged when the cable is connected. But the IRQ is masked so, there will not be any IRQ. When link driver calls the otg_init enable the logic for VBUS PRESENCE interrupt and call the VBUS PRESENCE IRQ handler. If the status bit set anyway the handler will send the notifications. >-- >balbi >-- 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
