Hi,
"Zengtao (B)" writes:
>>-Original Message-
>>From: Felipe Balbi [mailto:ba...@kernel.org]
>>Sent: Friday, December 14, 2018 4:52 PM
>>To: Zengtao (B)
>>Cc: liangshengjun ; Zengtao (B)
>>; Greg Kroah-Hartman
>>; linux-...@vger.kern
Hi,
Sekhar Nori writes:
All this should be part of comments in code along with information about
controller versions which suffer from the errata.
Is there a version of controller available which does not have the
defect? Is there a future plan to fix this?
Zeng Tao writes:
> If it's a busy system, some times when we start an isoc transfer, the
> framenumber get from the event buffer may be already elasped, in this
> case, we will get all the packets dropped due to miss isoc. And we turn
> into transfer nothing, to fix this issue, we need to fix
Peter Chen writes:
>> >> >> +irqreturn_t ret = IRQ_NONE;
>> >> >> +unsigned long flags;
>> >> >> +u32 reg;
>> >> >> +
>> >> >> +priv_dev = cdns->gadget_dev;
>> >> >> +spin_lock_irqsave(_dev->lock, flags);
>> >> >
>> >> >you're already running in hardirq context. Why do you
Peter Chen writes:
>> >> +tmode = le16_to_cpu(ctrl->wIndex);
>> >> +
>> >> +if (!set || (tmode & 0xff) != 0)
>> >> +return -EINVAL;
>> >> +
>> >> +switch (tmode >> 8) {
>> >> +case TEST_J:
>> >> +case TEST_K:
>> >> +
Hi
Pawel Laszczak writes:
>>> + cdns->phy = devm_phy_get(dev, "cdns3,usbphy");
>>> + if (IS_ERR(cdns->phy)) {
>>> + ret = PTR_ERR(cdns->phy);
>>> + if (ret == -ENOSYS || ret == -ENODEV) {
>>
>>Are you sure you can get ENOSYS here? Have you checked output of
>>checkpatch
Hi,
Pawel Laszczak writes:
>>I think what Felipe meant was to only combine the gadget driver code into one
>>patch.
>>
>>The series could be split into 6 patches like so.
>>-dt binding
>>-pci glue
>>-core driver
>>-host driver
>>-gadget driver
>>-drd driver
>
> Felipe wrote:
> "
> Frankly, I
Hi,
Pawel Laszczak writes:
> +static int cdns3_probe(struct platform_device *pdev)
> +{
> + struct device *dev = >dev;
> + struct resource *res;
> + struct cdns3 *cdns;
> + void __iomem *regs;
> + int ret;
> +
> + cdns = devm_kzalloc(dev, sizeof(*cdns), GFP_KERNEL);
> +
Hi,
Roger Quadros writes:
>> This patch introduce new Cadence USBSS DRD driver
>> to linux kernel.
>>
>> The Cadence USBSS DRD Driver is a highly
>> configurable IP Core which can be
>> instantiated as Dual-Role Device (DRD),
>> Peripheral Only and Host Only (XHCI)
>> configurations.
>>
>>
Hi,
Anurag Kumar Vulisha writes:
> Thanks for reviewing this patch. Lets consider an example where a
> request has num_sgs > 0 and each sg is mapped to a TRB and the last
> TRB has the IOC bit set. Once the controller is done with the
> transfer, it generates XferInProgress for
Hi,
Anurag Kumar Vulisha writes:
> HI Felipe,
>
>>-Original Message-----
>>From: Felipe Balbi [mailto:ba...@kernel.org]
>>Sent: Friday, December 07, 2018 11:42 AM
>>To: Anurag Kumar Vulisha ; Greg Kroah-Hartman
>>; Shuah Khan ; Alan Stern
>>
Hi,
Minas Harutyunyan writes:
> Hi Filipe,
>
> My patch dccf1bad4be7eaa096c1f3697bd37883f9a08ecb "usb: dwc2: Disable
> all EP's on disconnect" applied to 4.20-rc1.
>
> I need to update this patch. What I should do. There are 2 options:
>
> 1. Ack Marek Szyprowski [PATCH] usb: dwc2:
>
Hi,
Minas Harutyunyan writes:
> Hi Marek,
>
> On 12/6/2018 7:04 PM, Marek Szyprowski wrote:
>> Dear Minas,
>>
>> On 2018-12-04 13:34, Minas Harutyunyan wrote:
>>> On 11/23/2018 6:43 PM, Dan Carpenter wrote:
Ugh... We also had a long thread about the v2 patch but it turns out
the
Hi,
Anurag Kumar Vulisha writes:
>>> @@ -2286,7 +2286,12 @@ static int
>>dwc3_gadget_ep_reclaim_completed_trb(struct dwc3_ep *dep,
>>> if (event->status & DEPEVT_STATUS_SHORT && !chain)
>>> return 1;
>>>
>>> - if (event->status & (DEPEVT_STATUS_IOC | DEPEVT_STATUS_LST))
>>> +
hi,
Anurag Kumar Vulisha writes:
>>Does the data book suggest a value for the timeout?
>>
>
> No, the databook doesn't mention about the timeout value
>
>>> >At this point, it seems that the generic approach will be messier than
>>> >having every
>>> >controller driver implement its own fix.
Hi,
On Tue, Oct 16, 2018 at 1:27 PM Roger Quadros wrote:
>
> Felipe,
>
> On 16/10/2018 12:29, H. Nikolaus Schaller wrote:
> > Hi,
> >
> >> Am 17.09.2018 um 10:24 schrieb H. Nikolaus Schaller :
> >>
> >> Hi Felipe,
> >> I have made otg mode work on the omap5-uevm with help from Roger
> >> and now
Hi,
On Tue, Oct 16, 2018 at 1:27 PM Roger Quadros wrote:
>
> Felipe,
>
> On 16/10/2018 12:29, H. Nikolaus Schaller wrote:
> > Hi,
> >
> >> Am 17.09.2018 um 10:24 schrieb H. Nikolaus Schaller :
> >>
> >> Hi Felipe,
> >> I have made otg mode work on the omap5-uevm with help from Roger
> >> and now
Krzysztof Kozlowski writes:
> On Tue, May 15, 2018 at 2:12 PM, Andrzej Hajda wrote:
>> OF graph describes USB data lanes between USB-PHY and respective MUIC.
>> Since graph is present and DWC driver can use it to get extcon, obsolete
>> extcon property can
Krzysztof Kozlowski writes:
> On Tue, May 15, 2018 at 2:12 PM, Andrzej Hajda wrote:
>> OF graph describes USB data lanes between USB-PHY and respective MUIC.
>> Since graph is present and DWC driver can use it to get extcon, obsolete
>> extcon property can be removed.
>>
>> Signed-off-by:
onvert the percpu_ida users to the sbitmap API.
>
> Signed-off-by: Matthew Wilcox <mawil...@microsoft.com>
> ---
[...]
> drivers/usb/gadget/function/f_tcm.c | 8 +++---
for drivers/usb/gadget/function/f_tcm.c
Acked-by: Felipe Balbi <felipe.ba...@linux.intel.com>
--
balbi
signature.asc
Description: PGP signature
ff-by: Matthew Wilcox
> ---
[...]
> drivers/usb/gadget/function/f_tcm.c | 8 +++---
for drivers/usb/gadget/function/f_tcm.c
Acked-by: Felipe Balbi
--
balbi
signature.asc
Description: PGP signature
Andrzej Hajda writes:
> extcon device is used to detect host/device connection. Since extcon
> OF property is deprecated, alternative method should be added.
> This method uses OF graph bindings to locate extcon.
>
> Signed-off-by: Andrzej Hajda
> ---
>
Andrzej Hajda writes:
> extcon device is used to detect host/device connection. Since extcon
> OF property is deprecated, alternative method should be added.
> This method uses OF graph bindings to locate extcon.
>
> Signed-off-by: Andrzej Hajda
> ---
> Hi all,
>
> This patch implements
Hi,
Chunfeng Yun <chunfeng@mediatek.com> writes:
> On Wed, 2018-05-09 at 14:33 +0300, Felipe Balbi wrote:
>> Hi,
>>
>> Chunfeng Yun <chunfeng@mediatek.com> writes:
>> > The USB3CV version 2.1.80 (March 26, 2018) requires all devices
>> &
Hi,
Chunfeng Yun writes:
> On Wed, 2018-05-09 at 14:33 +0300, Felipe Balbi wrote:
>> Hi,
>>
>> Chunfeng Yun writes:
>> > The USB3CV version 2.1.80 (March 26, 2018) requires all devices
>> > ( gen1, gen2, single lane, dual lane) to return the v
Hi,
Chunfeng Yun writes:
> The USB3CV version 2.1.80 (March 26, 2018) requires all devices
> ( gen1, gen2, single lane, dual lane) to return the value of 0x0320
> in the bcdUSB field
this sounds really odd. What happens when I get a USB 3.1 compliant
device
Hi,
Chunfeng Yun writes:
> The USB3CV version 2.1.80 (March 26, 2018) requires all devices
> ( gen1, gen2, single lane, dual lane) to return the value of 0x0320
> in the bcdUSB field
this sounds really odd. What happens when I get a USB 3.1 compliant
device off-the-shelf and run it through
Romain Izard writes:
> When converting to GPIO descriptors, gpiod_get_value automatically
> handles the line inversion flags from the device tree.
>
> Do not invert the line twice.
>
> Fixes: 3df034081021fa4b6967ce3364bc7d867ec1c870
your fixes line is incorrect.
Romain Izard writes:
> When converting to GPIO descriptors, gpiod_get_value automatically
> handles the line inversion flags from the device tree.
>
> Do not invert the line twice.
>
> Fixes: 3df034081021fa4b6967ce3364bc7d867ec1c870
your fixes line is incorrect. Please fix and resend. While at
Hi,
Minas Harutyunyan writes:
>>> Actually to fix this issue I updated condition of wait function
>>> from:
>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING)
>>> to:
>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING & DWC3_EP_ENABLED)
>>
Hi,
Minas Harutyunyan writes:
>>> Actually to fix this issue I updated condition of wait function
>>> from:
>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING)
>>> to:
>>> !(dep->flags & DWC3_EP_END_TRANSFER_PENDING & DWC3_EP_ENABLED)
>>
>> you're not fixing anything.
Hi,
Masahiro Yamada writes:
>>> Each DWC3 instance is connected with
>>> multiple HS PHYs and multiple SS PHYs,
>>> depending on the number of ports.
>>
>> in that case, you shouldn't need dwc3 at all. A Host-only dwc3 is xHCI
>> compliant. If you really don't
Hi,
Masahiro Yamada writes:
>>> Each DWC3 instance is connected with
>>> multiple HS PHYs and multiple SS PHYs,
>>> depending on the number of ports.
>>
>> in that case, you shouldn't need dwc3 at all. A Host-only dwc3 is xHCI
>> compliant. If you really don't have the gadget block, there's no
Hi,
Masahiro Yamada <yamada.masah...@socionext.com> writes:
> 2018-04-04 14:36 GMT+09:00 Felipe Balbi <felipe.ba...@linux.intel.com>:
>>
>> Hi,
>>
>> Masahiro Yamada <yamada.masah...@socionext.com> writes:
>>> Currently, DWC3 core IP (driv
Hi,
Masahiro Yamada writes:
> 2018-04-04 14:36 GMT+09:00 Felipe Balbi :
>>
>> Hi,
>>
>> Masahiro Yamada writes:
>>> Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
>>> can take only one PHY phandle for each of SS, HS.
>>> (phy-names DT pr
Hi,
Masahiro Yamada writes:
> Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
> can take only one PHY phandle for each of SS, HS.
> (phy-names DT property is "usb2-phy" and "usb3-phy" for each)
We never had any other requirements :-)
> The DWC3 core IP is
Hi,
Masahiro Yamada writes:
> Currently, DWC3 core IP (drivers/usb/dwc3/core.c)
> can take only one PHY phandle for each of SS, HS.
> (phy-names DT property is "usb2-phy" and "usb3-phy" for each)
We never had any other requirements :-)
> The DWC3 core IP is provided by Synopsys,
> but some
(please configure your email client to break lines at 80 columns ;-)
Hi,
Anurag Kumar Vulisha writes:
> Hi Felipe,
>
> Thanks for reviewing the patch , please find my comments inline
no issues :-)
>>Anurag Kumar Vulisha writes:
>>> This
(please configure your email client to break lines at 80 columns ;-)
Hi,
Anurag Kumar Vulisha writes:
> Hi Felipe,
>
> Thanks for reviewing the patch , please find my comments inline
no issues :-)
>>Anurag Kumar Vulisha writes:
>>> This patch fixes two issues
>>>
>>> 1. The code logic in
Hi,
Randy Dunlap writes:
> On 03/21/2018 01:25 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20180320:
>>
>
>
> on i386:
>
> ERROR: "__tracepoint_dwc3_gadget_generic_cmd" [drivers/usb/dwc3/dwc3.ko]
> undefined!
> ERROR: "__tracepoint_dwc3_ep_queue"
Hi,
Randy Dunlap writes:
> On 03/21/2018 01:25 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20180320:
>>
>
>
> on i386:
>
> ERROR: "__tracepoint_dwc3_gadget_generic_cmd" [drivers/usb/dwc3/dwc3.ko]
> undefined!
> ERROR: "__tracepoint_dwc3_ep_queue" [drivers/usb/dwc3/dwc3.ko]
Hi,
Minas Harutyunyan writes:
>> Thanks for picking this for -next.
>> Is it better to have this in v4.16-rc fixes?
>> and also stable? v4.12+
>
> Well, there was no "Fixes: foobar" or "Cc: stable" lines in the commit
> log ;-)
>
>
Hi,
Minas Harutyunyan writes:
>> Thanks for picking this for -next.
>> Is it better to have this in v4.16-rc fixes?
>> and also stable? v4.12+
>
> Well, there was no "Fixes: foobar" or "Cc: stable" lines in the commit
> log ;-)
>
> The best we can do now, is wait
Hi,
Anurag Kumar Vulisha writes:
> This patch fixes two issues
>
> 1. The code logic in dwc3_prepare_one_trb() incorrectly uses the address
> and length given in req packet even for scattergather lists. This patch
> correct's the code to use sg->address and
Hi,
Anurag Kumar Vulisha writes:
> This patch fixes two issues
>
> 1. The code logic in dwc3_prepare_one_trb() incorrectly uses the address
> and length given in req packet even for scattergather lists. This patch
> correct's the code to use sg->address and sg->length when scattergather
> lists
Hi,
Minas Harutyunyan writes:
On 09/03/18 14:47, Roger Quadros wrote:
> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
> after which dual-role switching doesn't work.
>
> On dra7-evm's dual-role port,
> - Load
Hi,
Minas Harutyunyan writes:
On 09/03/18 14:47, Roger Quadros wrote:
> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
> after which dual-role switching doesn't work.
>
> On dra7-evm's dual-role port,
> - Load g_zero gadget driver and
Hi,
Roger Quadros writes:
> Hi Felipe,
>
> On 09/03/18 14:47, Roger Quadros wrote:
>> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
>> after which dual-role switching doesn't work.
>>
>> On dra7-evm's dual-role port,
>> - Load g_zero gadget driver
Hi,
Roger Quadros writes:
> Hi Felipe,
>
> On 09/03/18 14:47, Roger Quadros wrote:
>> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
>> after which dual-role switching doesn't work.
>>
>> On dra7-evm's dual-role port,
>> - Load g_zero gadget driver and enumerate to
Hi,
Colin King writes:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_warn warning message text.
>
> Signed-off-by: Colin Ian King
seems like we need a patch to fix your subject ;-) I'll fix it
Hi,
Colin King writes:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_warn warning message text.
>
> Signed-off-by: Colin Ian King
seems like we need a patch to fix your subject ;-) I'll fix it when applying
--
balbi
signature.asc
Description: PGP signature
Hi,
Manu Gautam <mgau...@codeaurora.org> writes:
> Hi,
>
>
> On 3/13/2018 4:38 PM, Felipe Balbi wrote:
>> Hi,
>>
>> +Andy
>>
>> Manu Gautam <mgau...@codeaurora.org> writes:
>>> DWC3 controller on Qualcomm SOCs has a Qscratch wrap
Hi,
Manu Gautam writes:
> Hi,
>
>
> On 3/13/2018 4:38 PM, Felipe Balbi wrote:
>> Hi,
>>
>> +Andy
>>
>> Manu Gautam writes:
>>> DWC3 controller on Qualcomm SOCs has a Qscratch wrapper.
>>> Some of its uses are described below resulting
Hi,
+Andy
Manu Gautam writes:
> DWC3 controller on Qualcomm SOCs has a Qscratch wrapper.
> Some of its uses are described below resulting in need to
> have a separate glue driver instead of using dwc3-of-simple:
> - It exposes register interface to override
Hi,
+Andy
Manu Gautam writes:
> DWC3 controller on Qualcomm SOCs has a Qscratch wrapper.
> Some of its uses are described below resulting in need to
> have a separate glue driver instead of using dwc3-of-simple:
> - It exposes register interface to override vbus-override
>and
Hi,
Roger Quadros writes:
>> When we set up the DWC3_DEPCMD_ENDTRANSFER command in
>> dwc3_stop_active_transfer(), we can do not set DWC3_DEPCMD_CMDIOC,
>> then there will no endpoint command complete interrupts I think.
>>
>> cmd |= DWC3_DEPCMD_CMDIOC;
>
Hi,
Roger Quadros writes:
>> When we set up the DWC3_DEPCMD_ENDTRANSFER command in
>> dwc3_stop_active_transfer(), we can do not set DWC3_DEPCMD_CMDIOC,
>> then there will no endpoint command complete interrupts I think.
>>
>> cmd |= DWC3_DEPCMD_CMDIOC;
>
> I
Hi,
Roger Quadros writes:
>>> This is what the v3.10 databook says
>>>
>>> "When issuing an End Transfer command, software must set the CmdIOC
>>> bit (field 8) so that an Endpoint Command Complete event is generated
>>> after the transfer ends. This is necessary to synchronize
Hi,
Roger Quadros writes:
>>> This is what the v3.10 databook says
>>>
>>> "When issuing an End Transfer command, software must set the CmdIOC
>>> bit (field 8) so that an Endpoint Command Complete event is generated
>>> after the transfer ends. This is necessary to synchronize the
>>>
Hi,
Roger Quadros writes:
>>> When we set up the DWC3_DEPCMD_ENDTRANSFER command in
>>> dwc3_stop_active_transfer(), we can do not set DWC3_DEPCMD_CMDIOC,
>>> then there will no endpoint command complete interrupts I think.
>>>
>>> cmd |= DWC3_DEPCMD_CMDIOC;
>>
>> I remember
Hi,
Roger Quadros writes:
>>> When we set up the DWC3_DEPCMD_ENDTRANSFER command in
>>> dwc3_stop_active_transfer(), we can do not set DWC3_DEPCMD_CMDIOC,
>>> then there will no endpoint command complete interrupts I think.
>>>
>>> cmd |= DWC3_DEPCMD_CMDIOC;
>>
>> I remember some part of
Stefan Wahren writes:
>> Stefan Wahren hat am 12. Februar 2018 um 21:20
>> geschrieben:
>>
>>
>> We better print an error in case probing of dwc2 fails on
>> setting the DMA coherent mask.
>>
>> Signed-off-by: Stefan Wahren
Stefan Wahren writes:
>> Stefan Wahren hat am 12. Februar 2018 um 21:20
>> geschrieben:
>>
>>
>> We better print an error in case probing of dwc2 fails on
>> setting the DMA coherent mask.
>>
>> Signed-off-by: Stefan Wahren
>> ---
>> drivers/usb/dwc2/platform.c | 4 +++-
>> 1 file
Hi,
Masahiro Yamada writes:
> +static void dwc3u_reset_init(struct dwc3u_priv *priv)
> +{
> + dwc3u_maskwrite(priv, RESET_CTL, LINK_RESET, 0);
> + usleep_range(1000, 2000);
> + dwc3u_maskwrite(priv, RESET_CTL, LINK_RESET, LINK_RESET);
Hi,
Masahiro Yamada writes:
> +static void dwc3u_reset_init(struct dwc3u_priv *priv)
> +{
> + dwc3u_maskwrite(priv, RESET_CTL, LINK_RESET, 0);
> + usleep_range(1000, 2000);
> + dwc3u_maskwrite(priv, RESET_CTL, LINK_RESET, LINK_RESET);
> +}
> +
>
Hi,
Roger Quadros <rog...@ti.com> writes:
> Hi,
>
> On 08/03/18 18:49, Brian Norris wrote:
>> Hi,
>>
>> On Thu, Mar 08, 2018 at 12:43:40PM +0200, Felipe Balbi wrote:
>>> William Wu <william...@rock-chips.com> writes:
>>>>
Hi,
Roger Quadros writes:
> Hi,
>
> On 08/03/18 18:49, Brian Norris wrote:
>> Hi,
>>
>> On Thu, Mar 08, 2018 at 12:43:40PM +0200, Felipe Balbi wrote:
>>> William Wu writes:
>>>> The dwc3_core_init() gets the PHYs and initializes the PHYs with
Hi,
Roger Quadros <rog...@ti.com> writes:
> Felipe,
>
> On 08/03/18 12:39, Felipe Balbi wrote:
>> Roger Quadros <rog...@ti.com> writes:
>>
>>> This is useful on platforms (e.g. TI AM437x) that don't
>>> have ID available on a GPIO but do hav
Hi,
Roger Quadros writes:
> Felipe,
>
> On 08/03/18 12:39, Felipe Balbi wrote:
>> Roger Quadros writes:
>>
>>> This is useful on platforms (e.g. TI AM437x) that don't
>>> have ID available on a GPIO but do have the OTG block.
>>>
>>
Hi Roger,
William Wu writes:
> The dwc3_core_init() gets the PHYs and initializes the PHYs with
> the usb_phy_init() and phy_init() functions before initializing
> core, and power on the PHYs after core initialization is done.
>
> However, some platforms (e.g.
Hi Roger,
William Wu writes:
> The dwc3_core_init() gets the PHYs and initializes the PHYs with
> the usb_phy_init() and phy_init() functions before initializing
> core, and power on the PHYs after core initialization is done.
>
> However, some platforms (e.g. Rockchip RK3399 DWC3 with Type-C
>
Roger Quadros writes:
> This is useful on platforms (e.g. TI AM437x) that don't
> have ID available on a GPIO but do have the OTG block.
>
> We can obtain the ID state via the OTG block and use it
> for dual-role switching.
>
> Signed-off-by: Roger Quadros
patch
Roger Quadros writes:
> This is useful on platforms (e.g. TI AM437x) that don't
> have ID available on a GPIO but do have the OTG block.
>
> We can obtain the ID state via the OTG block and use it
> for dual-role switching.
>
> Signed-off-by: Roger Quadros
patch one applied fine to
Hi,
Baolin Wang writes:
> void dwc3_gadget_exit(struct dwc3 *dwc)
> {
> + int epnum;
> + unsigned long flags;
> +
> + spin_lock_irqsave(>lock, flags);
> + for (epnum = 2; epnum < DWC3_ENDPOINTS_NUM; epnum++) {
Hi,
Baolin Wang writes:
> void dwc3_gadget_exit(struct dwc3 *dwc)
> {
> + int epnum;
> + unsigned long flags;
> +
> + spin_lock_irqsave(>lock, flags);
> + for (epnum = 2; epnum < DWC3_ENDPOINTS_NUM; epnum++) {
> +
Hi,
Roger Quadros <rog...@ti.com> writes:
> On 05/03/18 13:06, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Baolin Wang <baolin.w...@linaro.org> writes:
>>>>> Roger Quadros <rog...@ti.com> writes:
>>>>>>> Roger Quadro
Hi,
Roger Quadros writes:
> On 05/03/18 13:06, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Baolin Wang writes:
>>>>> Roger Quadros writes:
>>>>>>> Roger Quadros writes:
>>>>>>>> In the following test we get
Hi,
Baolin Wang writes:
>>> Roger Quadros writes:
> Roger Quadros writes:
>> In the following test we get stuck by sleeping forever in
>> _dwc3_set_mode()
>> after which dual-role switching doesn't work.
>>
>> On
Hi,
Baolin Wang writes:
>>> Roger Quadros writes:
> Roger Quadros writes:
>> In the following test we get stuck by sleeping forever in
>> _dwc3_set_mode()
>> after which dual-role switching doesn't work.
>>
>> On dra7-evm's dual-role port,
>> - Load g_zero gadget
Hi,
Roger Quadros writes:
>> Roger Quadros writes:
>>> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
>>> after which dual-role switching doesn't work.
>>>
>>> On dra7-evm's dual-role port,
>>> - Load g_zero gadget driver and enumerate
Hi,
Roger Quadros writes:
>> Roger Quadros writes:
>>> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
>>> after which dual-role switching doesn't work.
>>>
>>> On dra7-evm's dual-role port,
>>> - Load g_zero gadget driver and enumerate to host
>>> - suspend to mem
Hi,
Thomas Gleixner <t...@linutronix.de> writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner <t...@linutronix.de> writes:
>> > All numbers in micro seconds! What happens if you load the system or
>> > restrict C-States?
>>
>>
Hi,
Thomas Gleixner writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner writes:
>> > All numbers in micro seconds! What happens if you load the system or
>> > restrict C-States?
>>
>> added intel_idle.max_cstate=0 to cmdline. Still
Thomas Gleixner <t...@linutronix.de> writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner <t...@linutronix.de> writes:
>> > Enable the hrtimer and scheduling tracepoints. That should give you a hint
>> > what's going on.
>>
>> T
Thomas Gleixner writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner writes:
>> > Enable the hrtimer and scheduling tracepoints. That should give you a hint
>> > what's going on.
>>
>> Thanks, that does give me a lot more information.
Hi,
Thomas Gleixner <t...@linutronix.de> writes:
> On Tue, 27 Feb 2018, Felipe Balbi wrote:
>> I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
>> final) where rtctest fails sometimes which PIE coming too late with
>> frequencies >= 1024 Hz.
Hi,
Thomas Gleixner writes:
> On Tue, 27 Feb 2018, Felipe Balbi wrote:
>> I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
>> final) where rtctest fails sometimes which PIE coming too late with
>> frequencies >= 1024 Hz.
>>
>&
Hi,
Roger Quadros writes:
> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
> after which dual-role switching doesn't work.
>
> On dra7-evm's dual-role port,
> - Load g_zero gadget driver and enumerate to host
> - suspend to mem
> - disconnect USB cable
Hi,
Roger Quadros writes:
> In the following test we get stuck by sleeping forever in _dwc3_set_mode()
> after which dual-role switching doesn't work.
>
> On dra7-evm's dual-role port,
> - Load g_zero gadget driver and enumerate to host
> - suspend to mem
> - disconnect USB cable to host and
Hi folks,
I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
final) where rtctest fails sometimes which PIE coming too late with
frequencies >= 1024 Hz.
I've modified rtctest.c a bit so that it continues running even after
first failure just so I could get a glimpse of how
Hi folks,
I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
final) where rtctest fails sometimes which PIE coming too late with
frequencies >= 1024 Hz.
I've modified rtctest.c a bit so that it continues running even after
first failure just so I could get a glimpse of how
Hi,
Amelie Delaunay writes:
> On some boards, especially when vbus supply requires large current,
> and the charge pump on the PHY isn't enough, an external vbus power switch
> may be used.
> Add support for this optional external vbus supply in ehci-platform.
>
>
Hi,
Amelie Delaunay writes:
> On some boards, especially when vbus supply requires large current,
> and the charge pump on the PHY isn't enough, an external vbus power switch
> may be used.
> Add support for this optional external vbus supply in ehci-platform.
>
> Signed-off-by: Amelie Delaunay
Hi,
Richard Leitner writes:
> From: Richard Leitner
>
> For some userspace applications information on the number of
> over-current conditions at specific USB hub ports is relevant.
>
> In our case we have a series of USB hardware (using the cp210x
Hi,
Richard Leitner writes:
> From: Richard Leitner
>
> For some userspace applications information on the number of
> over-current conditions at specific USB hub ports is relevant.
>
> In our case we have a series of USB hardware (using the cp210x driver)
> which communicates using a
Hi,
Richard Leitner writes:
> From: Richard Leitner
>
> For some userspace applications information on the number of
> over-current conditions at specific USB hub ports is relevant. Therefore
> introduce a oc_counter in the usb port struct which
Hi,
Richard Leitner writes:
> From: Richard Leitner
>
> For some userspace applications information on the number of
> over-current conditions at specific USB hub ports is relevant. Therefore
> introduce a oc_counter in the usb port struct which is exported via
> sysfs.
relevant how? What
ncy on HAS_DMA, as they are selected from
> SND_SOC_APQ8016_SBC.
>
> Signed-off-by: Geert Uytterhoeven <ge...@linux-m68k.org>
for drivers/usb/gadget/:
Acked-by: Felipe Balbi <felipe.ba...@linux.intel.com>
--
balbi
signature.asc
Description: PGP signature
cted from
> SND_SOC_APQ8016_SBC.
>
> Signed-off-by: Geert Uytterhoeven
for drivers/usb/gadget/:
Acked-by: Felipe Balbi
--
balbi
signature.asc
Description: PGP signature
-by: Geert Uytterhoeven <ge...@linux-m68k.org>
Should I take this or is it going with the rest of the series? If you
wanna take it through Trivial or something like that:
Acked-by: Felipe Balbi <felipe.ba...@linux.intel.com>
--
balbi
signature.asc
Description: PGP signature
301 - 400 of 7706 matches
Mail list logo