Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753782AbbGBKSP (ORCPT ); Thu, 2 Jul 2015 06:18:15 -0400 Received: from comal.ext.ti.com ([198.47.26.152]:46266 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753709AbbGBKSJ (ORCPT ); Thu, 2 Jul 2015 06:18:09 -0400 Message-ID: <55950FD7.8080803@ti.com> Date: Thu, 2 Jul 2015 15:47:59 +0530 From: Lokesh Vutla User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: CC: , , , , , , Subject: Re: [PATCH 09/10] crypto: omap-aes: gcm: Add support for PIO mode References: <1435814320-30347-1-git-send-email-lokeshvutla@ti.com> <1435814320-30347-10-git-send-email-lokeshvutla@ti.com> <20150702080636.GH4033@saruman.tx.rr.com> In-Reply-To: <20150702080636.GH4033@saruman.tx.rr.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 780 Lines: 21 On Thursday 02 July 2015 01:36 PM, Felipe Balbi wrote: > On Thu, Jul 02, 2015 at 10:48:39AM +0530, Lokesh Vutla wrote: >> Add support for PIO mode for GCM mode. >> >> Signed-off-by: Lokesh Vutla > > why do you require PIO ? Is there any situation where DMA can't be > used? What would that case be ? Cannot think of any case where DMA can't be used. But the current driver already supports PIO for all other AES modes. I do not want to break it, so added support for PIO for GCM :) Thanks and regards, Lokesh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/