Return-path: Received: from mail-ve0-f172.google.com ([209.85.128.172]:45606 "EHLO mail-ve0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751582AbaBNBzM (ORCPT ); Thu, 13 Feb 2014 20:55:12 -0500 Received: by mail-ve0-f172.google.com with SMTP id c14so9346314vea.3 for ; Thu, 13 Feb 2014 17:55:11 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <87r4767rmo.fsf@kamboji.qca.qualcomm.com> References: <1392197844-1223-1-git-send-email-yeohchunyeow@gmail.com> <87r4767rmo.fsf@kamboji.qca.qualcomm.com> Date: Fri, 14 Feb 2014 09:55:11 +0800 Message-ID: (sfid-20140214_025517_306889_2C2CD51F) Subject: Re: [PATCH] ath10k: implement drv_get_tsf for ibss merging From: Yeoh Chun-Yeow To: Kalle Valo Cc: "linux-wireless@vger.kernel.org" , "ath10k@lists.infradead.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: > Yeah, this extremely ugly but don't really know any better way to handle > this now. I have observed that we have ath10k_wmi_event_tsf_measurement_report, but no so sure how to trigger this event. > But why do you need to take conf_mutex? Isn't this enough: > > +static u64 ath10k_get_tsf(struct ieee80211_hw *hw, struct ieee80211_vif *vif) > +{ > + /* > + * FIXME: Return 0 for time being. Need to figure out whether FW > + * has the API to fetch 64-bit TSF > + */ > + > + return 0; > +} Ya, I think this is enough for time being. I will submit v2 on this. ----- Chun-Yeow