Re: [PATCH] ARM: dts: Fix wl12xx missing clocks that cause hangs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I don't know for sure what determines whether or not it's needed.  I
don't have the WL12xx data sheets from TI in front of me, and you need
a special access to get them.  The Logic PD Torpedo schematic shows a
26MHz signal feeding TCXO_P pin, so it seems reasonable to set it if
its present.  The stock BSP that Logic ships has both the reference
clock and the TCXO defined, so I thought it was worth a try.  I did
comment about it on TI's E2E forum.  I am hoping someone there might
respond.  I am going to send an e-mail to the wlcore authors to see if
they can explain what makes certain parameters optional and also
further define what does 'optional' really mean.  Without the patch, I
was able to get the WiFi working, but scanning was broken.  I'll let
you know what I hear back.

adam

On Thu, Jan 21, 2016 at 11:21 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> * Adam Ford <aford173@xxxxxxxxx> [160121 09:04]:
>> The tcxo-clock-frequency binding is listed as optional,
>> but without it the wl12xx used on the torpedo + wireless
>> may hang.  Scanning also appears broken without this patch.
>
> OK sounds like we may have this missing for other boards as
> well. Do you know when tcxo-clock-frequency is not needed?
> Can it be seen from the schematics or something?
>
> Regards,
>
> Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux