From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id EA00AE0074B; Mon, 25 Aug 2014 09:00:01 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.220.47 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BA453E004FF for ; Mon, 25 Aug 2014 08:59:54 -0700 (PDT) Received: by mail-pa0-f47.google.com with SMTP id kx10so21213260pab.6 for ; Mon, 25 Aug 2014 08:59:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=J7iodqsggLI9KZf9heLuE7K1duqSzIkylhsKTauzGKQ=; b=gDKSngVB/wIMgkv0v/F0ifVCX7JwEfDcfko7n+1Ahg1/scTR/XcjqvPtmTpBlsSIrf xOYrnfTDXMrdVQEA4dq8Fs0f8o/hLj6k19LnQK0Eet/xHHUXt3objKUNYTnEkTd1n5/f 5dNsWogG67FDX4TlOJ7YzuN57QnKvjP4LNGBIs8aSUPa84Zy/E4zajqCJYLeQ0qgkYJx qOphWTETJDxb3FLScsSFX6oiXxagPkvpFtgpVqmSi7KG1g9Ap87526xSSmK4am/pKXat hlG5DoZIq2QV6NBOzjSAi0qo5kIhDOkyILV3OXetoh5u2dp02uDiqbeIXU/V0qSmYoMR Lp8g== X-Gm-Message-State: ALoCoQnRPER3L1nKRWw3dvyZbXyA9ZEbPWtNGD/+Lwu1xhR/x7WRq90qdva4wrV+3udRjrxPu7VJ X-Received: by 10.69.31.234 with SMTP id kp10mr12386568pbd.138.1408982391473; Mon, 25 Aug 2014 08:59:51 -0700 (PDT) Received: from [192.168.1.11] ([63.226.49.26]) by mx.google.com with ESMTPSA id xu4sm697209pab.30.2014.08.25.08.59.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Aug 2014 08:59:50 -0700 (PDT) Message-ID: <53FB5D72.2060408@boundarydevices.com> Date: Mon, 25 Aug 2014 08:59:46 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Mobile Dev , "meta-freescale@yoctoproject.org" References: In-Reply-To: Subject: Re: WL12xx Wi-Fi on 3.10.17_1.0.0_ga release X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2014 16:00:02 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello, ummm... mdev. On 08/22/2014 04:18 PM, Mobile Dev wrote: > Apologies for the length... > > I see that [Eric's] nitrogen6x boundary tree has some devicetree patches > to enable the TI Wi-Fi module. I am trying to bring it up on our custom > board and I have a few questions: > Since you're asking for support, do you mind identifying yourself? > 1. Where did you get the 'calibrate' utility? There are several repos > out there for it. In general, we've found the calibrate utility to be more or less useless, and since it's a pretty big pain to get and compile, we haven't used it in quite a while. > 2. Did you just use the wlcore/wlcore_sdio/wl12xx drivers in the > 3.10.17 kernel tree or did you pull anything from > backports/compat-wireless/TI? You can answer that question by checking the log. > 3. Related, did you add the compat-wireless recipe to your image? > Ditto. > > I have BT working just fine but I am having issues bringing up the Wi-Fi > side of the card. The first is getting it to calibrate: > > root@custom_board:/lib/firmware/ti-connectivity# ll > drwxr-xr-x 2 root root 4096 Aug 22 20:17 ./ > drwxr-xr-x 4 root root 4096 Aug 22 20:11 ../ > -rwxr-x--- 1 root root 50770 Aug 21 16:09 > TIInit_7.6.15.bts* > -rwxr-x--- 1 root root 13290 Aug 21 16:40 TQS_D_1.7.ini* > -rwxr-x--- 1 root root 49324 Aug 21 16:16 calibrator* > -rwxr-x--- 1 root root 912 Aug 22 20:18 wl1271-nvs.bin* > -rwxr-x--- 1 root root 354600 Aug 21 16:23 > wl127x-fw-5-mr.bin* > -rwxr-x--- 1 root root 352588 Aug 21 16:23 > wl127x-fw-5-plt.bin* > -rwxr-x--- 1 root root 370996 Aug 21 16:23 > wl127x-fw-5-sr.bin* > -rwxr-x--- 1 root root 912 Aug 21 16:23 wl127x-nvs.bin* > root@custom_board:/lib/firmware/ti-connectivity# lsmod > Module Size Used by > arc4 1510 2 > wl12xx 44514 0 > wlcore 141592 1 wl12xx > mac80211 226689 2 wl12xx,wlcore > cfg80211 178563 2 mac80211,wlcore > wlcore_sdio 4381 0 > cdc_acm 14295 0 > evbug 1476 0 > root@custom_board:/lib/firmware/ti-connectivity# echo 152 > > /sys/class/gpio/export > root@custom_board:/lib/firmware/ti-connectivity# echo out > > /sys/class/gpio/gpio152/direction > root@custom_board:/lib/firmware/ti-connectivity# echo 0 > > /sys/class/gpio/gpio152/value > root@custom_board:/lib/firmware/ti-connectivity# cat > /sys/class/gpio/gpio152/value > 0 > root@custom_board:/lib/firmware/ti-connectivity# echo 1 > > /sys/class/gpio/gpio152/value > root@custom_board:/lib/firmware/ti-connectivity# cat > /sys/class/gpio/gpio152/value > 0 > root@custom_board:/lib/firmware/ti-connectivity# ./calibrator plt > calibrate dual > wlcore: power up > wlcore: firmware booted in PLT mode PLT_ON (PLT 6.3.10.0.133) > wlcore: ERROR command complete timeout > ------------[ cut here ]------------ > WARNING: at drivers/net/wireless/ti/wlcore/main.c:790 > wl12xx_queue_recovery_work+0x5c/0x60 [wlcore]() > > > > ---[ end trace 4ae41c0eeb5b4b0b ]--- > wlcore: WARNING TEST command failed > wlcore: WARNING testmode cmd test failed: -110 > Fail to calibratewlcore: power down > The primary challenge in use of the WL12xx against any i.MX device is a quirk in the use of the power-off pin. The WL12xx driver expects writes to the SDHCI_POWER_CONTROL register to control the power-off GPIO directly. http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/drivers/mmc/host/sdhci.c?h=imx_3.10.17_1.0.1_ga#n1289 Since the i.MX SDHCI controllers don't do this, we had to add support for the "power-gpio". > > Usage: ./calibrator [options] plt calibrate [] > > Do calibrate for single or dual band chip > > > Options: > --debug enable netlink debugging > root@custom_board:/lib/firmware/ti-connectivity# > > > I have tried various combinations of drivers and tools but they all have > the same error (command complete timeout). As a test I tried changing > the node in the wlan section to <23 0x2> > from IRQ_TYPE_LEVEL_HIGH and the error changes to timeout waiting for > hardware interrupt so I know it is at least talking. > > Here are the relevant device tree sections: > > > > > &usdhc2 {/* uSDHC2, TiWi wl1271 */ > > > ... > > power-gpio = <&gpio5 24 0>; > Are you using our kernel? Have you validated your source tree against a Nitrogen6x or Nitrogen6_Max board? If so, then you should start looking for what's different. > > > > The second issue is that I can't successfully cycle the wlan0 interface > more than once (ifconfig up, down, up). When I try to bring it up the > second time, I get this: > > > root@custom_board:/lib/firmware/ti-connectivity# ifconfig wlan0 up > wlcore: ERROR timeout waiting for the hardware to complete > initialization > wlcore: ERROR timeout waiting for the hardware to complete > initialization > wlcore: ERROR timeout waiting for the hardware to complete > initialization > wlcore: ERROR firmware boot failed despite 3 retries > ifconfig: SIOCSIFFLAGS: Input/output error > root@custom_board:/lib/firmware/ti-connectivity# > > > I thought it was caused by this > (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258174) so I > changed the SD clock to add a pullup but it didn't work. > This is the primary symptom of not having our patches in place. Regards, Eric