Re: [PATCH] arm: omap2: board-generic: use omap4_local_timer_init for AM437x

On Wednesday 21 October 2015 02:35 AM, Felipe Balbi wrote: > AM437x-based boards, can use omap4_local_timer_init() > just fine. Let's use that instead. This is breaking AM43x-epos board. Today's Linux next: http://pastebin.ubuntu.com/13122620/ Reverting this patch:

Re: [PATCH] ARM: OMAP2+: Fix oops with LPAE and more than 2GB of memory

On Saturday 17 October 2015 12:53 AM, Tony Lindgren wrote: > * Lokesh Vutla <a0131...@ti.com> [151015 08:21]: [..snip..] >>> > > 8< --From c37732f6cea23d15fa357cf698833c03ce05 Mon > Sep 17 00:00:00 2001 > Date: Fri, 16 Oct 2015 12:1

Re: [PATCH] ARM: OMAP2+: Fix oops with LPAE and more than 2GB of memory

Hi Tony, On Wednesday 14 October 2015 09:32 PM, Tony Lindgren wrote: > * Lokesh Vutla <a0131...@ti.com> [151013 20:53]: >> Hi Tony, >> >> On Wednesday 14 October 2015 04:43 AM, Tony Lindgren wrote: >>> On boards with more than 2GB of RAM booting goe

Re: [PATCH] ARM: OMAP2+: Fix oops with LPAE and more than 2GB of memory

+Richard On Thursday 15 October 2015 07:35 PM, Tony Lindgren wrote: > * Lokesh Vutla <a0131...@ti.com> [151015 01:02]: >> Hi Tony, >> >> On Wednesday 14 October 2015 09:32 PM, Tony Lindgren wrote: >>> * Lokesh Vutla <a0131...@ti.com> [151013 20:53]: >&

Re: [PATCH] ARM: OMAP2+: Fix oops with LPAE and more than 2GB of memory

Hi Tony, On Wednesday 14 October 2015 04:43 AM, Tony Lindgren wrote: > On boards with more than 2GB of RAM booting goes wrong with things not working > and we're getting lots of l3 warnings: > > WARNING: CPU: 0 PID: 1 at drivers/bus/omap_l3_noc.c:147 > l3_interrupt_handler+0x260/0x384() >

Re: [PATCH] mmc: omap_hsmmc: fix initialization order of mmc block devices

On Tuesday 13 October 2015 01:14 PM, Heiko Schocher wrote: > Hello Lokesh, > > Am 13.10.2015 um 08:46 schrieb Lokesh Vutla: >> +Nishanth, >> >> On Tuesday 13 October 2015 10:59 AM, Heiko Schocher wrote: >>> On embedded devices, often there is a combination of

Re: [PATCH] mmc: omap_hsmmc: fix initialization order of mmc block devices

+Nishanth, On Tuesday 13 October 2015 10:59 AM, Heiko Schocher wrote: > On embedded devices, often there is a combination of > removable mmc devices (e.g. MMC/SD cards) and hard > wired ones (e.g. eMMC). Depending on the hardware > configuration, the 'mmcblkN' node might change if > the removable

Re: [PATCH] ARM: DRA7: hwmod: Remove elm address space from hwmod data

On Tuesday 13 October 2015 07:14 PM, Franklin S Cooper Jr wrote: > ELM address information is provided by device tree. No longer need > to include this information within hwmod. Reviewed-by: Lokesh Vutla <lokeshvu...@ti.com> Thanks and regards, Lokesh > > Signed-off-by: Fr

Re: [PATCHv4] arm: omap2: timer: always define omap4_local_timer_init

Hi Felipe, On Tuesday 29 September 2015 09:45 PM, Felipe Balbi wrote: > omap4_local_timer_init() can be used by other > platforms as is. At least AM437x wants to use > it. Instead of making omap4-only and providing > a stub for builds without OMAP4, we can just > make sure that function is always

Re: [PATCHv4] arm: omap2: timer: always define omap4_local_timer_init

On Wednesday 30 September 2015 01:11 PM, Lokesh Vutla wrote: > Hi Felipe, > > On Tuesday 29 September 2015 09:45 PM, Felipe Balbi wrote: >> omap4_local_timer_init() can be used by other >> platforms as is. At least AM437x wants to use >> it. Instead of making omap4-o

Re: [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

Hi Paul, On Monday 28 September 2015 10:05 PM, Paul Walmsley wrote: > On Thu, 24 Sep 2015, Lokesh Vutla wrote: > >> On Thursday 27 August 2015 09:51 AM, Lokesh Vutla wrote: >>> On Thursday 23 July 2015 06:55 PM, Lokesh Vutla wrote: >>>> This series implements

Re: [PATCH 07/17] ARM: dts: am4372: add reset data

Hi Tero, On Thursday 24 September 2015 07:56 PM, Tero Kristo wrote: > Add reset data for pruss, gfx, wkup-m3 and system reset. > > Signed-off-by: Tero Kristo > --- > arch/arm/boot/dts/am4372.dtsi | 24 > 1 file changed, 24 insertions(+) > > diff

Re: [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

Hi Paul, On Thursday 27 August 2015 09:51 AM, Lokesh Vutla wrote: > Hi Paul, > > On Thursday 23 July 2015 06:55 PM, Lokesh Vutla wrote: >> This series implements lock and unlock functions for RTC and hooks >> the same to DRA7 and AMx3xx hwmod. >> This is d

[PATCH v3] crypto: omap-aes: Add support for GCM mode

OMAP AES hw supports AES-GCM mode. Adding support for GCM and RFC4106 GCM mode in omap-aes driver. Signed-off-by: Lokesh Vutla <lokeshvu...@ti.com> --- Tested on BeagleBone-Black: http://pastebin.ubuntu.com/12417512/ Changes since v1: - Addressed comments by Herbert. Previously poste

Re: [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

Hi Paul, On Thursday 23 July 2015 06:55 PM, Lokesh Vutla wrote: This series implements lock and unlock functions for RTC and hooks the same to DRA7 and AMx3xx hwmod. This is dependent on the patch https://patchwork.kernel.org/patch/6578281/, which is queued recently by Paul. Gentle ping

[PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

This series implements lock and unlock functions for RTC and hooks the same to DRA7 and AMx3xx hwmod. This is dependent on the patch https://patchwork.kernel.org/patch/6578281/, which is queued recently by Paul. Changes since v2: - Add kerneldoc for omap_hwmod_rtc_lock() function. Lokesh Vutla

[PATCH v3 3/3] ARM: AMx3xx: RTC: Add lock and unlock functions

Hook omap_hwmod_rtc_unlock/lock functions into RTC hwmod, so that SYSCONFIG register is updated properly. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2

[PATCH v3 2/3] ARM: DRA7: RTC: Add lock and unlock functions

Hook omap_hwmod_rtc_unlock/lock functions into RTC hwmod, so that SYSCONFIG register is updated properly Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c b

[PATCH v3 1/3] ARM: hwmod: RTC: Add lock and unlock functions

registers. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod.h | 2 ++ arch/arm/mach-omap2/omap_hwmod_reset.c | 65 ++ 2 files changed, 67 insertions(+) diff --git a/arch/arm/mach-omap2/omap_hwmod.h b/arch/arm/mach-omap2

[PATCH v2 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

This series implements lock and unlock functions for RTC and hooks the same to DRA7 and AMx3xx hwmod. This is dependent on the patch https://patchwork.kernel.org/patch/6578281/, which is queued recently by Paul. Tested on DRA72-evm: http://pastebin.ubuntu.com/11892356/ Lokesh Vutla (3): ARM

[PATCH v2 2/3] ARM: DRA7: RTC: Add lock and unlock functions

Hook omap_hwmod_rtc_unlock/lock functions into RTC hwmod, so that SYSCONFIG register is updated properly Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c b

[PATCH v2 1/3] ARM: hwmod: RTC: Add lock and unlock functions

registers. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod.h | 2 ++ arch/arm/mach-omap2/omap_hwmod_reset.c | 56 ++ 2 files changed, 58 insertions(+) diff --git a/arch/arm/mach-omap2/omap_hwmod.h b/arch/arm/mach-omap2

[PATCH v2 3/3] ARM: AMx3xx: RTC: Add lock and unlock functions

Hook omap_hwmod_rtc_unlock/lock functions into RTC hwmod, so that SYSCONFIG register is updated properly. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2

Re: [PATCH 3/3] ARM: AMx3xx: hwmod: RTC: Add lock and unlock functions

Hi Paul, On Thursday 16 July 2015 05:44 AM, Paul Walmsley wrote: Hi On Wed, 10 Jun 2015, Lokesh Vutla wrote: RTC IP have kicker feature which prevents spurious writes to its registers. In order to write into any of the RTC registers, KICK values has to be written to KICK registers

Re: [PATCH 2/3] ARM: DRA: hwmod: RTC: Add lock and unlock functions

Hi Paul, On Thursday 16 July 2015 05:43 AM, Paul Walmsley wrote: Hi, some comments. On Wed, 10 Jun 2015, Lokesh Vutla wrote: RTC IP have kicker feature which prevents spurious writes to its registers. In order to write into any of the RTC registers, KICK values has to be written to KICK

Re: [PATCH 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

Hi Tero, On Thursday 16 July 2015 05:33 PM, Tero Kristo wrote: On 07/16/2015 01:13 PM, Paul Walmsley wrote: On Thu, 16 Jul 2015, Tero Kristo wrote: On 07/16/2015 03:15 AM, Paul Walmsley wrote: On Tue, 14 Jul 2015, Tero Kristo wrote: On 07/14/2015 01:09 PM, Lokesh Vutla wrote: Hi

Re: [PATCH 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

Hi, On Wednesday 10 June 2015 02:56 PM, Lokesh Vutla wrote: Some IP blocks like RTC, needs an additional unlocking mechanism for writing to its registers. This patch adds optional lock and unlock function pointers to the IP block's hwmod data which gets executed before and after writing

Re: [PATCH v2 6/7] crypto: omap-aes: Add support for GCM mode

Hi Herbert, On Wednesday 08 July 2015 09:48 AM, Herbert Xu wrote: On Tue, Jul 07, 2015 at 09:01:48PM +0530, Lokesh Vutla wrote: +static int omap_aes_gcm_copy_buffers(struct omap_aes_dev *dd, + struct aead_request *req) [..snip..] +static int do_encrypt_iv

Re: [PATCH v2 6/7] crypto: omap-aes: Add support for GCM mode

On Wednesday 08 July 2015 01:23 PM, Herbert Xu wrote: On Wed, Jul 08, 2015 at 03:48:05PM +0800, Herbert Xu wrote: On Wed, Jul 08, 2015 at 12:29:47PM +0530, Lokesh Vutla wrote: + if (req-assoclen + req-cryptlen == 0) { + scatterwalk_map_and_copy(ctx-auth_tag, req-dst, 0, authlen

Re: [PATCH v2 6/7] crypto: omap-aes: Add support for GCM mode

On Wednesday 08 July 2015 01:18 PM, Herbert Xu wrote: On Wed, Jul 08, 2015 at 12:29:47PM +0530, Lokesh Vutla wrote: + if (req-assoclen + req-cryptlen == 0) { + scatterwalk_map_and_copy(ctx-auth_tag, req-dst, 0, authlen, + 1); + return 0

Re: [PATCH v2 6/7] crypto: omap-aes: Add support for GCM mode

On Wednesday 08 July 2015 09:48 AM, Herbert Xu wrote: On Tue, Jul 07, 2015 at 09:01:48PM +0530, Lokesh Vutla wrote: +static int omap_aes_gcm_copy_buffers(struct omap_aes_dev *dd, + struct aead_request *req) +{ +void *buf_in; +int pages, alen, clen

Re: [PATCH v2 5/7] crypto: aead: Add aead_request_cast() api

On Wednesday 08 July 2015 09:26 AM, Herbert Xu wrote: On Tue, Jul 07, 2015 at 09:01:47PM +0530, Lokesh Vutla wrote: Add aead_request_cast() api to get pointer to aead_request from cryto_async_request. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- include/crypto/internal/aead.h | 6

[PATCH v2 7/7] crypto: tcrypt: Fix AEAD speed tests

The AEAD speed tests doesn't do a wait_for_completition, if the return value is EINPROGRESS or EBUSY. Fixing it here. Also add a test case for gcm(aes). Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- crypto/tcrypt.c | 65 ++--- 1 file

[PATCH v2 3/7] crypto: omap-aes: Fix configuring of AES mode

AES_CTRL_REG is used to configure AES mode. Before configuring any mode we need to make sure all other modes are reset or else driver will misbehave. So mask all modes before configuring any AES mode. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 13

[PATCH v2 1/7] crypto: omap-aes: Fix CTR mode

is not aligned with AES_BLOCK_SIZE. Adding support for omap-aes driver for inputs with length not aligned with AES_BLOCK_SIZE. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 33 - 1 file changed, 16 insertions(+), 17 deletions(-) diff

[PATCH v2 0/7] crypto: omap-aes: Add support for GCM mode

This series does some basic cleanup and adds support for AES GCM mode for omap aes driver. Changes since v1: - Switched GCM to new AEAD interface Lokesh Vutla (7): crypto: omap-aes: Fix CTR mode crypto: omap-aes: Increase priority of hw accelerator crypto: omap-aes: Fix configuring of AES

[PATCH v2 2/7] crypto: omap-aes: Increase priority of hw accelerator

Increasing the priority of omap-aes hw algos, in order to take precedence over sw algos. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c

[PATCH v2 5/7] crypto: aead: Add aead_request_cast() api

Add aead_request_cast() api to get pointer to aead_request from cryto_async_request. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- include/crypto/internal/aead.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/include/crypto/internal/aead.h b/include/crypto/internal/aead.h index

[PATCH v2 6/7] crypto: omap-aes: Add support for GCM mode

OMAP AES hw supports AES-GCM mode. Adding support for GCM mode in omap-aes driver. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/Kconfig| 1 + drivers/crypto/Makefile | 3 +- drivers/crypto/omap-aes-gcm.c | 376

[PATCH v2 4/7] crypto: omap-aes: Use BIT() macro

Use BIT()/GENMASK() macros for all register definitions instead of hand-writing bit masks. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/drivers/crypto/omap

Re: [PATCH 10/10] crypto: tcrypt: Added speed tests for Async AEAD crypto alogrithms

Hi, On Monday 06 July 2015 01:14 PM, Herbert Xu wrote: On Thu, Jul 02, 2015 at 10:48:40AM +0530, Lokesh Vutla wrote: Adding simple speed tests for a range of block sizes for Async AEAD crypto algorithms. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com What's wrong with the existing AEAD

Re: [PATCH 08/10] crypto: omap-aes: gmc: Add algo info

Hi, On Monday 06 July 2015 01:05 PM, Herbert Xu wrote: On Thu, Jul 02, 2015 at 10:48:38AM +0530, Lokesh Vutla wrote: Now the driver supports gcm mode, add omap-aes-gcm algo info to omap-aes driver. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com You're using the old AEAD interface. We

Re: [PATCH 05/10] crypto: omap-aes: Add support for GCM mode

On Thursday 02 July 2015 01:34 PM, Felipe Balbi wrote: On Thu, Jul 02, 2015 at 10:48:35AM +0530, Lokesh Vutla wrote: OMAP AES hw supports aes gcm mode. here you refer to it as 'gcm' Will update it in next revision. Adding support for GCM mode in omap-aes driver. while here

Re: [PATCH 03/10] crypto: aead: Add aead_request_cast() api

On Thursday 02 July 2015 01:28 PM, Felipe Balbi wrote: On Thu, Jul 02, 2015 at 10:48:33AM +0530, Lokesh Vutla wrote: Add aead_request_cast() api to get pointer to aead_request from cryto_async_request. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- include/linux/crypto.h |6

Re: [PATCH 06/10] crypto: omap-aes: gcm: Handle inputs properly

On Thursday 02 July 2015 01:34 PM, Felipe Balbi wrote: On Thu, Jul 02, 2015 at 10:48:36AM +0530, Lokesh Vutla wrote: Its not necessary that assoc data and plain text is passed always. Add these checks before processing the input. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com why can't

Re: [PATCH 08/10] crypto: omap-aes: gmc: Add algo info

On Thursday 02 July 2015 01:30 PM, Stephan Mueller wrote: Am Donnerstag, 2. Juli 2015, 10:48:38 schrieb Lokesh Vutla: Hi Lokesh, Now the driver supports gcm mode, add omap-aes-gcm algo info to omap-aes driver. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c

Re: [PATCH 02/10] crypto: omap-aes: Fix configuring of AES mode

On Thursday 02 July 2015 01:27 PM, Felipe Balbi wrote: On Thu, Jul 02, 2015 at 10:48:32AM +0530, Lokesh Vutla wrote: AES_CTRL_REG is used to configure AES mode. Before configuring any mode we need to make sure all other modes are reset or else driver will misbehave. So mask all modes before

Re: [PATCH 09/10] crypto: omap-aes: gcm: Add support for PIO mode

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 lokeshvu...@ti.com why do you require PIO ? Is there any situation where DMA can't be used? What would

Re: [PATCH 01/10] crypto: omap-aes: Add support for lengths not aligned with AES_BLOCK_SIZE

On Thursday 02 July 2015 01:23 PM, Felipe Balbi wrote: On Thu, Jul 02, 2015 at 10:48:31AM +0530, Lokesh Vutla wrote: OMAP AES driver returns an error if the data is not aligned with AES_BLOCK_SIZE bytes. But OMAP AES hw allows data input upto 1 byte aligned, but still zeros are to be appended

[PATCH] crypto: omap-des: Fix unmapping of dma channels

) [4.328500] [c004a840] (irq_exit) from [c000f9ac] (handle_IRQ+0x50/0xb0) [4.335589] [c000f9ac] (handle_IRQ) from [c0008688] (gic_handle_irq+0x28/0x5c) Removing the duplicate call to dma_unmap_sg(). Reported-by: Tomi Valkeinen tomi.valkei...@ti.com Signed-off-by: Lokesh Vutla lokeshvu...@ti.com

[PATCH 02/10] crypto: omap-aes: Fix configuring of AES mode

AES_CTRL_REG is used to configure AES mode. Before configuring any mode we need to make sure all other modes are reset or else driver will misbehave. So mask all modes before configuring any AES mode. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 13

[PATCH 08/10] crypto: omap-aes: gmc: Add algo info

Now the driver supports gcm mode, add omap-aes-gcm algo info to omap-aes driver. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 22 ++ 1 file changed, 22 insertions(+) diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c index

[PATCH 05/10] crypto: omap-aes: Add support for GCM mode

OMAP AES hw supports aes gcm mode. Adding support for GCM mode in omap-aes driver. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/Makefile |3 +- drivers/crypto/omap-aes-gcm.c | 304 + drivers/crypto/omap-aes.c | 238

[PATCH 10/10] crypto: tcrypt: Added speed tests for Async AEAD crypto alogrithms

Adding simple speed tests for a range of block sizes for Async AEAD crypto algorithms. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- crypto/tcrypt.c | 233 +++ crypto/tcrypt.h |1 + 2 files changed, 234 insertions(+) diff --git

[PATCH 07/10] crypto: omap-aes: gcm: Add support for unaligned lengths

Check if the inputs are not aligned, if not process the input before starting the hw acceleration. Similarly after completition of hw acceleration. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes-gcm.c | 82 + 1 file changed

[PATCH 06/10] crypto: omap-aes: gcm: Handle inputs properly

Its not necessary that assoc data and plain text is passed always. Add these checks before processing the input. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes-gcm.c | 26 -- 1 file changed, 20 insertions(+), 6 deletions(-) diff --git

[PATCH 01/10] crypto: omap-aes: Add support for lengths not aligned with AES_BLOCK_SIZE

for inputs not aligned with AES_BLOCK_SIZE. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 33 - 1 file changed, 16 insertions(+), 17 deletions(-) diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c index 9a28b7e..a923101

[PATCH 03/10] crypto: aead: Add aead_request_cast() api

Add aead_request_cast() api to get pointer to aead_request from cryto_async_request. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- include/linux/crypto.h |6 ++ 1 file changed, 6 insertions(+) diff --git a/include/linux/crypto.h b/include/linux/crypto.h index 10df5d2..20fac3d

[PATCH 04/10] crypto: omap-aes: Use BIT() macro

Use BIT()/GENMASK() macros for all register definitions instead of hand-writing bit masks. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes.c | 36 ++-- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/drivers/crypto/omap

[PATCH 09/10] crypto: omap-aes: gcm: Add support for PIO mode

Add support for PIO mode for GCM mode. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-aes-gcm.c | 10 ++ drivers/crypto/omap-aes.c | 24 ++-- drivers/crypto/omap-aes.h |3 ++- 3 files changed, 26 insertions(+), 11 deletions

[PATCH 00/10] crypto: omap-aes: Add support for GCM mode

This series does some basic cleanup and adds support for AES GCM mode for omap aes driver. Also adds a test case for async aead algos. Tested on BeagelBoneBlack: http://pastebin.ubuntu.com/11808341/ Lokesh Vutla (10): crypto: omap-aes: Add support for lengths not aligned

[PATCH 2/3] ARM: DRA: hwmod: RTC: Add lock and unlock functions

registers. Also hook these functions to RTC hwmod. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod.h | 2 ++ arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 ++ arch/arm/mach-omap2/omap_hwmod_reset.c| 47 +++ 3 files changed

[PATCH 3/3] ARM: AMx3xx: hwmod: RTC: Add lock and unlock functions

hooks omap_hwmod_rtc_unlock/lock functions into RTC hwmod, so that SYSCONFIG register is updated properly. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2

[PATCH 1/3] ARM: OMAP2+: hwmod: add support for lock and unlock hooks

by hwmod code before and after writing sysconfig registers. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod.c | 13 + arch/arm/mach-omap2/omap_hwmod.h | 4 2 files changed, 17 insertions(+) diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch

[PATCH 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

/ AM437x-gp-evm: http://pastebin.ubuntu.com/11689157/ (Used an out of tree patch to enable RTC) Lokesh Vutla (3): ARM: OMAP2+: hwmod: add support for lock and unlock hooks ARM: DRA: hwmod: RTC: Add lock and unlock functions ARM: AMx3xx: RTC: Add lock and unlock functions arch/arm/mach-omap2

[PATCH v2] crypto: omap-sham: Add the offset of sg page to vaddr

-by: Lokesh Vutla lokeshvu...@ti.com --- - Tested on BBB. Logs below. Without this patch: http://pastebin.ubuntu.com/10722994/ With this patch: http://pastebin.ubuntu.com/10722992/ drivers/crypto/omap-sham.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/crypto/omap-sham.c b

Re: [PATCH] crypto: omap-sham: Check for HIGHMEM before mapping SG pages

Hi Herbert, On Wednesday 01 April 2015 07:48 PM, Herbert Xu wrote: On Tue, Mar 31, 2015 at 09:52:23AM +0530, Lokesh Vutla wrote: Commit 26a05489ee0e (crypto: omap-sham - Map SG pages if they are HIGHMEM before accessing) says that HIGHMEM pages may not be mapped so we must kmap them before

Re: [rtc-linux] [PATCH 1/3] rtc: omap: Unlock and Lock rtc registers before and after register writes

Hi, On Wednesday 01 April 2015 09:22 PM, Alexandre Belloni wrote: Hi, On 01/04/2015 at 11:24:56 +0530, Lokesh Vutla wrote : RTC module contains a kicker mechanism to prevent any spurious writes from changing the register values. This mechanism requires two MMR writes to the KICK0 and KICK1

[PATCH v2 0/3] rtc: omap: Fix misc bugs

This patch series fixes miscellaneous bugs in OMAP RTC driver. Tested on BeagleBone-Black. Logs: http://pastebin.ubuntu.com/10723287/ V1 patches can be seen here: http://www.mail-archive.com/linux-omap%40vger.kernel.org/msg115839.html Lokesh Vutla (3): rtc: omap: Unlock and Lock rtc

[PATCH v3 1/3] rtc: omap: Unlock and Lock rtc registers before and after register writes

and leaves it enabled until the rtc driver removal. This eliminates the idea of preventing spurious writes when RTC driver is loaded. So implement rtc lock and unlock functions before and after register writes. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com Acked-by: Alexandre Belloni

[PATCH v2 2/3] rtc: omap: Update Kconfig for OMAP RTC

RTC is present in AM43xx and DRA7xx also. Updating the Kconfig to depend on ARCH_OMAP or ARCH_DAVINCI Signed-off-by: Lokesh Vutla lokeshvu...@ti.com Acked-by: Alexandre Belloni alexandre.bell...@free-electrons.com --- drivers/rtc/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions

[PATCH v2 3/3] rtc: omap: use module_platform_driver

module_platform_driver_probe() prevents driver from requesting probe deferral. So using module_platform_drive() to support probe deferral. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com Acked-by: Alexandre Belloni alexandre.bell...@free-electrons.com --- drivers/rtc/rtc-omap.c | 5 +++-- 1 file

[PATCH v2 1/3] rtc: omap: Unlock and Lock rtc registers before and after register writes

and leaves it enabled until the rtc driver removal. This eliminates the idea of preventing spurious writes when RTC driver is loaded. So implement rtc lock and unlock functions before and after register writes. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- -- This is as advised by Paul

Re: [PATCH v2 1/3] rtc: omap: Unlock and Lock rtc registers before and after register writes

On Thursday 02 April 2015 06:03 PM, Alexandre Belloni wrote: On 02/04/2015 at 16:39:09 +0530, Lokesh Vutla wrote : [..snip..] } +static inline void am3352_rtc_unlock(struct omap_rtc *rtc) +{ +rtc_writel(rtc, OMAP_RTC_KICK0_REG, KICK0_VALUE); +rtc_writel(rtc, OMAP_RTC_KICK1_REG

[PATCH 2/3] rtc: omap: Update Kconfig for OMAP RTC

RTC is present in AM43xx and DRA7xx also. Updating the Kconfig to depend on ARCH_OMAP or ARCH_DAVINCI Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/rtc/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig index

[PATCH 1/3] rtc: omap: Unlock and Lock rtc registers before and after register writes

and leaves it enabled until the rtc driver removal. This eliminates the idea of preventing spurious writes when RTC driver is loaded. So implement rtc lock and unlock functions before and after register writes. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- - This is as advised by Paul

[PATCH 3/3] rtc: omap: use module_platform_driver

module_platform_driver_probe() prevents driver from requesting probe deferral. So using module_platform_drive() to support probe deferral. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/rtc/rtc-omap.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers

[PATCH 0/3] rtc: omap: Fix misc bugs

This patch series fixes miscellaneous bugs in OMAP RTC driver. Tested on DRA72-evm with an out of tree patch for RTC hwmod. Logs: http://pastebin.ubuntu.com/10716566/ Lokesh Vutla (3): rtc: omap: Unlock and Lock rtc registers before and after register writes rtc: omap: Update Kconfig

[PATCH] crypto: omap-aes: Fix support for unequal lengths

a single element SG list for this buffer with length as the total bytes to crypt, which is similar thing that is done in case of unaligned lengths. Fixes: 6242332ff2f3 (crypto: omap-aes - Add support for cases of unaligned lengths) Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto

[PATCH] crypto: omap-sham: Check for HIGHMEM before mapping SG pages

if they are HIGHMEM before accessing) Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-sham.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c index 3c76696..ace5852 100644 --- a/drivers/crypto/omap

[PATCH] crypto: omap-sham: Use pm_runtime_irq_safe()

: scheduling while atomic: kworker/0:2/2676/0x0100 Add pm_runtime_irq_safe() to avoid this. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/crypto/omap-sham.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c index ace5852..81ed511

Re: [PATCH v3] omap-rng: Change RNG_CONFIG_REG to RNG_CONTROL_REG when, checking and disabling TRNG

of entropy generated. Yes you are correct. Patch looks good to me. It should be RNG_CONTROL_REG Acked-by: Lokesh Vutla lokeshvu...@ti.com Thanks and regards, Lokesh Apart from the strange logic, I have reason to suspect that the OMAP4 related code in this driver is driving an Inside Secure IP

Re: [RFC PATCH] ARM: DRA: hwmod: RTC: Add reset function for RTC

, Lokesh - Paul On Fri, 2 Jan 2015, Paul Walmsley wrote: Ping. Are you going to redo this one? - Paul On Wed, 26 Nov 2014, Paul Walmsley wrote: Hi Lokesh On Tue, 25 Nov 2014, Lokesh Vutla wrote: Hi Paul, On Thursday 20 November 2014 10:26 PM, Paul Walmsley wrote: On Thu, 20 Nov

[PATCH v2] ARM: DRA7: hwmod: Fix boot crash with DEBUG_LL enabled on UART3

-by: Felipe Balbi ba...@ti.com Acked-by: Felipe Balbi ba...@ti.com Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- Changes since v1: - Updated $subject and patch description. arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH] ARM: OMAP2+: hwmod: Fix _wait_target_ready() for hwmods without sysc

Hi Paul, On Tuesday 06 January 2015 07:34 AM, Paul Walmsley wrote: Roger, Lokesh, could you try this one instead? Yep, the below patch works on AM437x. Boot logs here: http://paste.ubuntu.com/9680938/ Thanks and regards, Lokesh It passes all the basic tests here except it does not boot on

[PATCH] ARM: DRA7: beagle-x15: hwmod: Fix boot crash with DEBUG_LL

-by: Felipe Balbi ba...@ti.com Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c index ffd6604..b6ea88f

Re: [PATCH] ARM: OMAP2+: hwmod: Fix _wait_target_ready() for hwmods without sysc

Hi Paul, On Saturday 03 January 2015 02:40 AM, Paul Walmsley wrote: + Suman, lakml Hi Roger On Thu, 18 Dec 2014, Roger Quadros wrote: Fixing up Paul's email id. cheers, -roger On 18/12/14 17:49, Roger Quadros wrote: There are quite a few hwmods that don't have sysconfig register

[PATCH] ARM: OMAP2+: hwmod: print error if wait_target_ready() failed

Fixed pr_debug to pr_err when hwmod returns an error when enabling a module. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/omap_hwmod.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2

Re: [PATCH] ARM: OMAP2+: hwmod: Fix _wait_target_ready() for hwmods without sysc

access that checks the module ready state has nothing to do with module's SYSCONFIG or mpu_rt_port. Yes, makes sense. This patch looks good to me. Tested this on AM437x-gp-evm. Tested-by: Lokesh Vutla lokeshvu...@ti.com May be good idea to warn every time if enabling of module is failed? Unrelated

Re: [PATCH V2 2/2] ARM: dra7xx: Fix counter frequency drift for AM572x errata i856.

* 375 / 2 or SYSCLK1 * 75 / 244. Looks good to me. Tested this on DRA7 evm. Tested-by: Lokesh Vutla lokeshvu...@ti.com Thanks and regards, Lokesh Signed-off-by: Len Sorensen lsore...@csclub.uwaterloo.ca --- arch/arm/mach-omap2/control.h |4 arch/arm/mach-omap2/timer.c | 36

Re: [PATCH 2/2] ARM: omap5/dra7xx: Fix counter frequency drift for AM572x errata i856.

Hi Lennart, On Sunday 14 December 2014 10:15 AM, Lennart Sorensen wrote: On Fri, Dec 12, 2014 at 05:08:56PM -0500, Lennart Sorensen wrote: Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external crystal is not enabled at power up. Instead the CPU falls back to using an

Re: [PATCH 1/2] ARM: omap5/dra7xx: Fix frequency typos.

Hi Len, On Saturday 13 December 2014 03:38 AM, Lennart Sorensen wrote: The switch statement of the possible list of SYSCLK1 frequencies is missing a 0 in 4 out of the 7 frequencies. Indeed a good catch !! Reviewed-by: Lokesh Vutla lokeshvu...@ti.com Thanks and regards, Lokesh Signed-off

Re: [RFC/PATCH 2/7] arm: omap: devicetree: add new properties for OMAP devices

Hi Felipe, On Wednesday 10 December 2014 03:57 AM, Felipe Balbi wrote: In order to get rid of some more hwmod data, we introduce a few extra properties to OMAP DT data in order to be able to pass the needed information through DT. Signed-off-by: Felipe Balbi ba...@ti.com ---

[PATCH] drivers: net : cpsw: Update Kconfig for CPSW

CPSW is present in AM33xx, AM43xx, DRA7xx. Updating the Kconfig to depend on ARCH_OMAP2PLUS instead of listing all SoC's. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/net/ethernet/ti/Kconfig | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net

Re: [PATCH] drivers: net : cpsw: Update Kconfig for CPSW

Hi, Please discard this patch. Missed adding something. Will be posting an updated patch. Sorry for the spam. Thanks and regards, Lokesh On Thursday 04 December 2014 10:18 AM, Lokesh Vutla wrote: CPSW is present in AM33xx, AM43xx, DRA7xx. Updating the Kconfig to depend on ARCH_OMAP2PLUS instead

[PATCH v2] drivers: net : cpsw: Update Kconfig for CPSW

CPSW is present in AM33xx, AM43xx, DRA7xx. Updating the Kconfig to depend on ARCH_OMAP2PLUS instead of listing all SoC's. Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- drivers/net/ethernet/ti/Kconfig | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net

[PATCH] ARM: OMAP2+: AM43x: Add ID for ES1.2

. Latest Technical Documentation can be found here: http://www.ti.com/lsds/ti/arm/sitara_arm_cortex_a_processor/arm_cortex_a9_core/am437x_arm_cortex_a9/tech_docs.page Signed-off-by: Lokesh Vutla lokeshvu...@ti.com --- arch/arm/mach-omap2/id.c | 8 ++-- arch/arm/mach-omap2/soc.h | 1 + 2 files

Re: [RFC PATCH] ARM: DRA: hwmod: RTC: Add reset function for RTC

Hi Paul, On Wednesday 26 November 2014 12:34 PM, Paul Walmsley wrote: Hi Lokesh On Tue, 25 Nov 2014, Lokesh Vutla wrote: Hi Paul, On Thursday 20 November 2014 10:26 PM, Paul Walmsley wrote: On Thu, 20 Nov 2014, Lokesh Vutla wrote: On Monday 17 November 2014 10:13 AM, Lokesh Vutla wrote

Re: [RFC PATCH] ARM: DRA: hwmod: RTC: Add reset function for RTC

Hi Paul, On Thursday 20 November 2014 10:26 PM, Paul Walmsley wrote: On Thu, 20 Nov 2014, Lokesh Vutla wrote: On Monday 17 November 2014 10:13 AM, Lokesh Vutla wrote: RTC IP have kicker feature which prevents spurious writes to its registers. In order to write into any of the RTC registers

Re: [PATCH 3/3] drivers: bus: Move omap gpmc code to live under drivers

Hi Tony, On Friday 21 November 2014 03:58 AM, Tony Lindgren wrote: Just move to drivers as further clean-up can now happen there finally. Cc: Arnd Bergmann a...@arndb.de Cc: Roger Quadros rog...@ti.com Signed-off-by: Tony Lindgren t...@atomide.com --- arch/arm/mach-omap2/Kconfig

  1   2   3   >