On Thu, Nov 1, 2018 at 1:28 PM Chen-Yu Tsai <wens@xxxxxxxx> wrote: > > On Thu, Nov 1, 2018 at 3:35 PM Jagan Teki <jagan@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > On Thu, Nov 1, 2018 at 12:07 AM Jagan Teki <jagan@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > From: Jagan Teki <jagan@xxxxxxxxxxxx> > > > > > > Enable AP6356S WiFi/BT combo chip on Orangepi Lite2 board: > > > - WiFi SDIO interface is connected to MMC1 > > > - WiFi WL-PMU-EN pin connected to gpio PM3: attach to mmc-pwrseq > > > - WiFi WL-WAKE-AP pin connected to gpio PM0 > > > - 32kHz external oscillator gate clock from RTC > > You never specified a clock rate for it, so it might actually be wrong. > The default clock rate would be something "around" 32 kHz, but not very > accurate. Meanwhile the WiFi module would have very specific requirements > on frequency and accuracy of this clock. The WiFi part doesn't seem to > care that much, but the Bluetooth part cares very much. It doesn't work > or it would seem to work but you don't get anything off the radio if the > frequency is off (as in off-frequency). True, but why it's not 32K which is stated in manual and schematics do we need to measure the actual rate with oscilloscope? > > > > > > > Signed-off-by: Jagan Teki <jagan@xxxxxxxxxxxx> > > > --- > > > Note: > > > - chip detected, but failed to connect > > > [ 129.084504] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted > > > [ 135.906409] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout > > > > This got fixed. Will send next version. > > Could you wait until I get my RTC changes out? I also have some Bluetooth > patches for AP621x, which is what started all this RTC work, which you might > find interesting. Yes, my intention is the same.
