public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v9] usb: add MediaTek USB3 DRD driver
Date: Wed, 14 Oct 2020 15:03:44 +0200	[thread overview]
Message-ID: <a91f2ae2-45dc-9aab-9ca3-59bd60ad404e@denx.de> (raw)
In-Reply-To: <1602678559.29336.93.camel@mhfsdcap03>

On 10/14/20 2:29 PM, Chunfeng Yun wrote:
> On Wed, 2020-10-14 at 12:56 +0200, Marek Vasut wrote:
>> On 10/14/20 10:50 AM, Chunfeng Yun wrote:
>>> This patch adds support for the MediaTek USB3 DRD controller,
>>> its host side is based on xHCI, this driver supports device mode
>>> and host mode.
>>
>> This patch doesn't seem to apply to u-boot-usb/next , and also,
>> u-boot-usb/next does not build:
> 
> There is error:
>  aarch64:  +   mt8512_bm1_emmc
> +aarch64-linux-ld.bfd: drivers/usb/gadget/udc/built-in.o: in function
> `usb_gadget_handle_interrupts':
> +drivers/usb/gadget/udc/udc-uclass.c:56: undefined reference to
> `dm_usb_gadget_handle_interrupts'
> 
> It seems that the gadget of mtu3 is not enabled, but the default mode is
> gadget mode, not sure why not works.
> 
> I sent a patch to try to fix it:
> 
> https://patchwork.ozlabs.org/project/uboot/patch/1602678229-19372-1-git-send-email-chunfeng.yun at mediatek.com/
> configs: mt8512: enable device mode of mtu3 explicitly
> 
> 
> Sorry for inconvenience

That's fine, but can you please rebase this on usb/next and resend, so I
can apply it ?

Also, you can use either of the travis/gitlab CI to build-test the
patches before submitting them.

  reply	other threads:[~2020-10-14 13:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14  8:50 [PATCH v9] usb: add MediaTek USB3 DRD driver Chunfeng Yun
2020-10-14 10:56 ` Marek Vasut
2020-10-14 12:29   ` Chunfeng Yun
2020-10-14 13:03     ` Marek Vasut [this message]
2020-10-15  1:49       ` Chunfeng Yun
2020-10-15 12:28         ` Marek Vasut
2020-10-16  1:43           ` Chunfeng Yun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a91f2ae2-45dc-9aab-9ca3-59bd60ad404e@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox