[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87shxrz74p.fsf@intel.com>
Date: Mon, 09 May 2016 16:35:34 +0300
From: Felipe Balbi <balbi@...nel.org>
To: William Wu <william.wu@...k-chips.com>, gregkh@...uxfoundation.org,
heiko@...ech.de
Cc: briannorris@...gle.com, dianders@...gle.com,
kever.yang@...k-chips.com, huangtao@...k-chips.com,
frank.wang@...k-chips.com, eddie.cai@...k-chips.com,
John.Youn@...opsys.com, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org
Subject: Re: [PATCH] usb: dwc3: add DWC3_GUCTL1 reg for debug
William Wu <william.wu@...k-chips.com> writes:
> On 05/09/2016 08:10 PM, Felipe Balbi wrote:
>> William Wu <william.wu@...k-chips.com> writes:
> Thanks Felipe Balbi and Greg KH. I'm really sorry that I forgot to
> add changelog.
>>> Signed-off-by: William Wu <william.wu@...k-chips.com>
>> no changelog = no commit, sorry. Why do you want to dump GUCTL1?
> Because GUCTL1 can be written by user. For rockchip platform,
> we set GUCTL1.DEV_FORCE_20_CLK_FOR_30_CLK(bit26) to 1 in
> bootrom(used for usb2.0 device only),
> and after kernel boot, I want to check whether this bit can be
> reset to default 0 after core reset.
> Dump GUCTL1 reg from debugfs is more convenient for me.
cool, something like this could go to commit log :-)
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (819 bytes)
Powered by blists - more mailing lists