From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from sabertooth01.qualcomm.com ([65.197.215.72]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Z331Z-0001Uf-A1 for ath10k@lists.infradead.org; Thu, 11 Jun 2015 14:00:06 +0000 From: Kalle Valo Subject: Re: [PATCH v3] ath10k: add 'cryptmode' param to support raw tx injection and software crypto References: <1433812382-10287-1-git-send-email-cfliu.tw@gmail.com> Date: Thu, 11 Jun 2015 16:59:31 +0300 In-Reply-To: <1433812382-10287-1-git-send-email-cfliu.tw@gmail.com> (Liu CF's message of "Mon, 8 Jun 2015 18:13:02 -0700") Message-ID: <87vbeubb24.fsf@kamboji.qca.qualcomm.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Liu CF/TW Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Liu CF/TW writes: > This change supports hardware crypto engine bypass by enabling raw > Rx/Tx encap mode. This enables use cases such as software crypto and raw > tx injection. This change introduces a new module param 'cryptmode'. > > cryptmode: > > 0: Use hardware crypto engine globally with native Wi-Fi mode TX/RX > encapsulation to the firmware. This is the default mode. > 1: Use sofware crypto engine globally with raw mode TX/RX encapsulation > to the firmware. These two values are ok. > 2: Supports both hardware and software crypto with raw mode TX/RX > encapsulation to the firmware. By default hardware crypto engine is > used. To use software crypto in this mode, set the per ath10k_vif > 'nohwcrypt' flag value to True.* > *) The patch for setting vif specific 'nohwcrypt' flag when > cryptmode=2 would be a separate patch to mac80211. But this the problematic one. I cannot apply something to ath10k until Johannes applies the mac80211 part. Didn't I mention this already earlier? At least I was supposed to do that. And most importantly does Johannes even agree with the approach? IIRC he was pretty reluctant about configuring the crypto mode via nl80211. I suggest splitting the patch into two: patch 1 adding support for cryptmode values 0 and 1, patch 2 adding support for cryptmode 2. That way we can commit patch 1 early and see what we can do with patch 2. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k