Hi Bjorn,
Thanks for your review comments.
On Mon, Feb 08 2021, Bjorn Andersson wrote:
> On Mon 08 Feb 00:00 CST 2021, Baruch Siach wrote:
>> From: Balaji Prakash J <bjagadee@xxxxxxxxxxxxxx>
>>
>> DWC_USB3_GFLADJ and DWC_USB3_GUCTL registers contain options
>> to control the behavior of controller with respect to SOF and ITP.
>> The reset values of these registers are aligned for 19.2 MHz
>> reference clock source. This change will add option to override
>> these settings for reference clock other than 19.2 MHz
>>
>> Tested on IPQ6018 SoC based CP01 board with 24MHz reference clock.
>>
>> Signed-off-by: Balaji Prakash J <bjagadee@xxxxxxxxxxxxxx>
>> [ baruch: mention tested hardware ]
>> Signed-off-by: Baruch Siach <baruch@xxxxxxxxxx>
>> ---
>> .../devicetree/bindings/usb/dwc3.txt | 5 ++
>> drivers/usb/dwc3/core.c | 52 +++++++++++++++++++
>> drivers/usb/dwc3/core.h | 12 +++++
>> 3 files changed, 69 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/usb/dwc3.txt b/Documentation/devicetree/bindings/usb/dwc3.txt
>> index 1aae2b6160c1..4ffa87b697dc 100644
>> --- a/Documentation/devicetree/bindings/usb/dwc3.txt
>> +++ b/Documentation/devicetree/bindings/usb/dwc3.txt
>> @@ -89,6 +89,11 @@ Optional properties:
>> - snps,quirk-frame-length-adjustment: Value for GFLADJ_30MHZ field of GFLADJ
>> register for post-silicon frame length adjustment when the
>> fladj_30mhz_sdbnd signal is invalid or incorrect.
>> + - snps,quirk-ref-clock-adjustment: Value for GFLADJ_REFCLK_* fields of GFLADJ
>> + register for reference clock other than 19.2 MHz is used.
>
> What are typical values for this property? What unit does it have? How
> does it actually relate to the frequency of the reference clock?
Downstream codeaurora kernel (fig branch) sets 0xA87F0 for IPQ6018
(24MHz reference clock), and 0x49459 for IPQ5018 (60MHz). So this value
appears to correlates with clock rate. I have no access to DWC3
documentation. I only tested IPQ6018 hardware.
>> + - snps,quirk-ref-clock-period: Value for REFCLKPER filed of GUCTL. This field
>> + indicates in terms of nano seconds the period of ref_clk. To calculate the
>> + ideal value, REFCLKPER = (1/ref_clk in Hz)*10^9.
>
> Can't we make the dwc3 reference this clock and use clk_get_rate() and
> then do this math in the driver?
This is doable, I believe. Though current code does not identify
specific clocks, as far as I can see.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@xxxxxxxxxx - tel: +972.52.368.4656, http://www.tkos.co.il -
