From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Wed, 14 Oct 2020 15:03:44 +0200
Subject: [PATCH v9] usb: add MediaTek USB3 DRD driver
In-Reply-To: <1602678559.29336.93.camel@mhfsdcap03>
References: <1602665439-16792-1-git-send-email-chunfeng.yun@mediatek.com>
 <7ed34781-0e48-da36-b576-d22688687ac7@denx.de>
 <1602678559.29336.93.camel@mhfsdcap03>
Message-ID: <a91f2ae2-45dc-9aab-9ca3-59bd60ad404e@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.