On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
> The OTG core instantiates the OTG Finite State Machine
> per OTG controller and manages starting/stopping the
> host and gadget controllers based on the bus state.
>
> It provides APIs for the following tasks
>
> - Registering an
On Mon, Aug 24, 2015 at 04:21:24PM +0300, Roger Quadros wrote:
> DRD mode is a reduced functionality OTG mode. In this mode
> we don't support SRP, HNP and dynamic role-swap.
>
> In DRD operation, the controller mode (Host or Peripheral)
> is decided based on the ID pin status. Once a cable plug
Peter,
On 06/09/15 05:02, Peter Chen wrote:
> On Wed, Sep 02, 2015 at 05:24:16PM +0300, Roger Quadros wrote:
>> Register with the USB OTG core. Since we don't support
>> OTG yet we just work as a dual-role device even
>> if device tree says "otg".
>>
>> +
>> +static int dwc3_drd_init(struct dwc3
Hi,
On Tue, Sep 01, 2015 at 06:37:54PM +0300, Ville Syrjälä wrote:
> On Tue, Sep 01, 2015 at 10:17:59AM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Sep 01, 2015 at 05:39:28PM +0300, Ville Syrjälä wrote:
> > > On Tue, Sep 01, 2015 at 08:59:02AM -0500, Felipe Balbi wrote:
> > > > Hi,
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/09/15 12:06, Roger Quadros wrote:
> Felipe,
>
> On 03/09/15 18:44, Felipe Balbi wrote:
>> Hi,
>
>> On Thu, Sep 03, 2015 at 03:21:48PM +0300, Roger Quadros wrote:
> + dwc->fsm->id = id;
> + dwc->fsm->b_sess_vld = vbus;
> +
The bulk queue tests are used to show 'best performance' for bulk
transfer, we are often asked this question by users. The implementation
is the same with iso test, that is queue request at interrupt completion,
so we reuse the iso structures, and rename them as common one.
It's result should be
Right now even if driver failed to probe extcon framework will
still deliver its VBUS and ID events, which will lead to random
exception codes.
Fix this by removing VBUS and ID events notifiers when probe fail.
Fixes: 591fc116f330 ("usb: phy: msm: Use extcon framework for VBUS and ID
On Mon, 2015-08-24 at 10:11 -0700, Tim Bird wrote:
> On 08/18/2015 12:56 AM, Ivan T. Ivanov wrote:
> > Right now even if driver failed to probe extcon framework will
> > still deliver its VBUS and ID events, which will lead to random
> > exception codes.
> >
> > Fix this by removing driver
On 07/09/15 10:53, Li Jun wrote:
> On Mon, Aug 24, 2015 at 04:21:24PM +0300, Roger Quadros wrote:
>> DRD mode is a reduced functionality OTG mode. In this mode
>> we don't support SRP, HNP and dynamic role-swap.
>>
>> In DRD operation, the controller mode (Host or Peripheral)
>> is decided based
Hello,
I have a problem with the panel on my Tegra Chromebook taking longer
than expected to be ready during boot (Stéphane Marchesin reported what
is basically the same issue in [0]), and have looked into ordered
probing as a better way of solving this than moving nodes around in the
DT or
On 07/09/15 10:40, Li Jun wrote:
> On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
>> The OTG core instantiates the OTG Finite State Machine
>> per OTG controller and manages starting/stopping the
>> host and gadget controllers based on the bus state.
>>
>> It provides APIs for the
On 06/09/15 10:06, Peter Chen wrote:
> On Mon, Aug 24, 2015 at 04:21:11PM +0300, Roger Quadros wrote:
>> Hi,
>>
>> This series centralizes OTG/Dual-role functionality in the kernel.
>> As of now I've got Dual-role functionality working pretty reliably on
>> dra7-evm and am437x-gp-evm.
>>
>> DWC3
On 07/09/15 04:24, Peter Chen wrote:
> On Mon, Aug 24, 2015 at 04:21:15PM +0300, Roger Quadros wrote:
>> This is to prevent missing symbol build error if OTG is
>> enabled (built-in) and HCD core (CONFIG_USB) is module.
>>
>> Signed-off-by: Roger Quadros
>> Acked-by: Peter Chen
On 07/09/15 04:23, Peter Chen wrote:
> On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
>> + * This is used by the USB Host stack to register the Host controller
>> + * to the OTG core. Host controller must not be started by the
>> + * caller as it is left upto the OTG state machine
Use kmalloc_array instead of kmalloc to allocate memory for an array.
Also, remove the dev_warn for a memory leak, making the if check more
sleek.
Signed-off-by: Muhammad Falak R Wani
---
On suggestion by Joe Perches
Changes since v0
-remove
urb completion callback is executed in host controllers interrupt
context. To keep preempt disable time short, add urbs to a list on
completion and schedule work to process the list.
Moreover, save timestamp and sof number in the urb completion callback
to avoid any delays.
Signed-off-by: Mian
I executed a clone detection tool* on drivers source code and I found
that the files
drivers/usb/host/fusbh200-hcd.c
and
drivers/usb/host/fotg210-hcd.c
are very similar. The main difference between the two files are
replacing the string 'USBH20' by 'OTG21' and some white space fixes.
Some
Hi Alan,
> No output at all? Even when you use a VT console and you do "echo 8
> >proc/sys/kernel/printk"?
When using "lsusb -v", I get the line that tells me which device is to
be listed first, then nothing anymore. When disabling the ehci-pci module,
I get nothing at all. I've taken a photo
Hi Alan,
just a quick heads-up before I go to sleep,
more detailed info to follow later this week.
The freeze is triggered from hcd.c, function usb_remove_hcd:
/* Prevent any more root-hub status calls from the timer.
* The HCD might still restart the timer (if a port status change
* interrupt
On Mon, 7 Sep 2015, Roland Weber wrote:
> > It would be nice to find out exactly where the unbind freezes. Here
> > are some routines to check; try sprinkling printk or dev_info
> > statements at various places within them:
>
> Thanks. I'll send some results later this week.
The fact that
On Mon, Sep 7, 2015 at 7:23 AM, Tomeu Vizoso wrote:
> Hello,
>
> I have a problem with the panel on my Tegra Chromebook taking longer
> than expected to be ready during boot (Stéphane Marchesin reported what
> is basically the same issue in [0]), and have looked into
[un]register_interest and reading cable state by
name have been deprecated. Switch to new API.
Signed-off-by: Ivan T. Ivanov
---
drivers/usb/phy/phy-qcom-8x16-usb.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git
On Fri, 2015-06-05 at 17:26 +0800, Peter Chen wrote:
> On Fri, Jun 05, 2015 at 10:37:07AM +0300, Ivan T. Ivanov wrote:
>
> > > > +
> > > > +static int ci_id_notifier(struct notifier_block *nb, unsigned long
> > > > event,
> > > > + void *ptr)
> > > > +{
On recent Qualcomm platforms VBUS and ID lines are not routed to
USB PHY LINK controller. Use extcon framework to receive connect
and disconnect ID and VBUS notification.
Signed-off-by: Ivan T. Ivanov
---
Changes sice v3 [1]:
* Migrate to new extcon framework API
*
24 matches
Mail list logo