From: Kever Yang <kever.yang@rock-chips.com>
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>,
"heiko@sntech.de" <heiko@sntech.de>
Cc: "dianders@chromium.org" <dianders@chromium.org>,
"olof@lixom.net" <olof@lixom.net>,
"sonnyrao@chromium.org" <sonnyrao@chromium.org>,
"addy.ke@rock-chips.com" <addy.ke@rock-chips.com>,
"cf@rock-chips.com" <cf@rock-chips.com>,
"xjq@rock-chips.com" <xjq@rock-chips.com>,
"wulf@rock-chips.com" <wulf@rock-chips.com>,
"lyz@rock-chips.com" <lyz@rock-chips.com>,
"hj@rock-chips.com" <hj@rock-chips.com>,
"huangtao@rock-chips.com" <huangtao@rock-chips.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/4] usb: dwc2: add compatible data for rockchip soc
Date: Fri, 08 Aug 2014 08:39:05 +0800 [thread overview]
Message-ID: <53E41C29.9070501@rock-chips.com> (raw)
In-Reply-To: <A2CA0424C0A6F04399FB9E1CD98E0304844C4DF6@US01WEMBX2.internal.synopsys.com>
Paul,
On 08/08/2014 02:26 AM, Paul Zimmerman wrote:
>> From: Kever Yang [mailto:kever.yang@gmail.com] On Behalf Of Kever Yang
>> Sent: Thursday, August 07, 2014 2:35 AM
>>
>> This patch add compatible data for dwc2 controller found on
>> rk3066, rk3188 and rk3288 processors from rockchip.
>>
>> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
>> Acked-by: Paul Zimmerman <paulz@synopsys.com>
>> ---
>>
>> Changes in v4:
>> - max_transfer_size change to 65536, this should be enough
>> for most transfer, the hardware auto-detect will set this
>> to 0x7ffff which may make dma_alloc_coherent fail when
>> non-dword aligned buf from driver like usbnet happen.
> Hi Kever,
>
> Did you test this change thoroughly? I have vague memories of any
> value above 65535 causing problems, at least on my hardware. And I
> see it is set to 65535 in both pci.c and platform.c. I could be
> wrong, but I thought I should mention it.
I test it on rk3288 evb, it works find with 65536, I'm sorry for didn't
mention it in my patch.
The problem in my platform is if the value use hardware auto-detect, it
will be 0x7ffff,
and that will cause the dma_alloc_coherent fail in hcd driver.
The value less than 0x7ffff should be fine for hardware, but for the
software, it depends on
how we use it.
What kind of problem did you met? Software problem or hardware problem?
Maybe I should
pay more attention for this value. :)
>
next prev parent reply other threads:[~2014-08-08 0:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 9:34 [PATCH v4 0/4] Patches to add support for Rockchip dwc2 controller Kever Yang
2014-08-07 9:34 ` [PATCH v4 1/4] Documentation: dt-bindings: add dt binding info for Rockchip dwc2 Kever Yang
2014-08-07 9:34 ` [PATCH v4 2/4] usb: dwc2: add compatible data for rockchip soc Kever Yang
2014-08-07 18:26 ` Paul Zimmerman
2014-08-07 20:52 ` Doug Anderson
2014-08-07 20:59 ` Paul Zimmerman
2014-08-08 1:42 ` Kever.Yang
2014-08-08 0:39 ` Kever Yang [this message]
2014-08-07 9:34 ` [PATCH v4 3/4] ARM: dts: add rk3288 dwc2 controller support Kever Yang
2014-08-07 21:17 ` Doug Anderson
2014-08-07 9:34 ` [PATCH v4 4/4] ARM: dts: Enable USB otg and host1(dwc) on rk3288-evb Kever Yang
2014-08-07 21:23 ` Doug Anderson
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=53E41C29.9070501@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=Paul.Zimmerman@synopsys.com \
--cc=addy.ke@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=hj@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lyz@rock-chips.com \
--cc=olof@lixom.net \
--cc=sonnyrao@chromium.org \
--cc=wulf@rock-chips.com \
--cc=xjq@rock-chips.com \
/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