Re: [PATCH] net: ethernet: ti: davinci_cpdma: fix fixed prio cpdma ctlr configuration

2016-11-10 Thread ivan.khoronzhuk
On 10.11.16 18:37, Grygorii Strashko wrote: On 11/09/2016 05:56 PM, Ivan Khoronzhuk wrote: On 09.11.16 23:09, Grygorii Strashko wrote: On 11/08/2016 07:10 AM, Ivan Khoronzhuk wrote: The dma ctlr is reseted to 0 while cpdma start, thus cpdma ctlr I assume this is because cpdma_ctlr_st

Re: [PATCH v3 5/5] net: ethernet: ti: cpsw: add ethtool channels support

2016-08-17 Thread ivan.khoronzhuk
On 17.08.16 09:22, Mugunthan V N wrote: On Tuesday 16 August 2016 04:55 AM, Ivan Khoronzhuk wrote: These ops allow to control number of channels driver is allowed to work with at cpdma level. The maximum number of channels is 8 for rx and 8 for tx. In dual_emac mode the h/w channels are shared

Re: [PATCH 1/3] net: ethernet: ti: cpdma: fix lockup in cpdma_ctlr_destroy()

2016-07-26 Thread ivan.khoronzhuk
On 26.07.16 19:02, Grygorii Strashko wrote: On 07/23/2016 09:24 AM, Ivan Khoronzhuk wrote: On 22.07.16 16:58, Grygorii Strashko wrote: Fix deadlock in cpdma_ctlr_destroy() which is triggered now on cpsw module removal: cpsw_remove() - cpdma_ctlr_destroy() - spin_lock_irqsave(&ctlr->loc

Re: [PATCH] net: ethernet: ti: cpdma: switch to use genalloc

2016-06-23 Thread ivan.khoronzhuk
On 23.06.16 15:36, Grygorii Strashko wrote: TI CPDMA currently uses a bitmap for tracking descriptors alloactions allocations, but The genalloc already handles the same and can be used as with special memory (SRAM) as with DMA cherent memory chank (dma_alloc_coherent()). Hence, switch to using

Re: [REGRESSION] firmware: dmi_scan: add SBMIOS entry and DMI tables

2016-03-28 Thread ivan.khoronzhuk
Hi Paul, The dmi_remap() is arch dependent function and for mainline used as ioremap_cache for x86, arm.. And only for ia64 as ioremap (where it's same as ioremap_cache). I'm talking about k4.5. It's rather bug of dmi_remap than the patch which just use it. The only reason why the bug wasn't f

Re: [PATCH 3.2 068/221] firmware: dmi_scan: Fix dmi_len type

2015-05-06 Thread ivan.khoronzhuk
Hi Ben, There is no need in this patch for 3.2, only beginning from 3.19. SMBIOSv3 is absent in k3.2, and for previous SMBIOS versions 16-bit dmi len is enough. It should had been mentioned in the commit/code, sorry. On 05.05.15 04:16, Ben Hutchings wrote: 3.2.69-rc1 review patch. If anyone ha

Re: [PATCH 1/2] firmware: dmi_scan: Simplified displayed version

2015-04-27 Thread Ivan.khoronzhuk
Sorry sent it from wrong address, just don't have access to linaro mailbox, at least for now. -- Regards, Ivan Khoronzhuk -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.or

Re: [PATCH] firmware: dmi_scan: Trim DMI table length before exporting it

2015-04-27 Thread Ivan.khoronzhuk
Hi, Jean On 26.04.15 23:47, Jean Delvare wrote: The SMBIOS v3 entry points specify a maximum length for the DMI table, not the exact length. Thus there may be garbage after the end-of-table marker, which we don't want to export to user-space. Adjust dmi_len when we find the end-of-table marker,

Re: [Patch v2 2/3] firmware: dmi_scan: add SBMIOS entry and DMI tables

2015-04-21 Thread Ivan.khoronzhuk
Jean, On 21.04.15 18:36, Jean Delvare wrote: Hi again Ivan, On Mon, 20 Apr 2015 13:19:46 +0300, Ivan Khoronzhuk wrote: + bin_attr_DMI.size = dmi_len; + bin_attr_DMI.private = dmi_table; + ret = sysfs_create_bin_file(tables_kobj, &bin_attr_DMI); + if (!ret) +

Re: [Patch v2 2/3] firmware: dmi_scan: add SBMIOS entry and DMI tables

2015-04-21 Thread Ivan.khoronzhuk
Hi Jean, On 21.04.15 17:24, Jean Delvare wrote: Hi Ivan, On Mon, 20 Apr 2015 13:19:46 +0300, Ivan Khoronzhuk wrote: Some utils, like dmidecode and smbios, need to access SMBIOS entry table area in order to get information like SMBIOS version, size, etc. Currently it's done via /dev/mem. But fo

Re: [Patch 1/3] firmware: dmi_scan: rename dmi_table to dmi_decode_table

2015-04-17 Thread Ivan.khoronzhuk
Hi Jean, On 17.04.15 13:11, Ivan.khoronzhuk wrote: On 17.04.15 11:54, Jean Delvare wrote: Hi Ivan, On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote: On 16.04.15 11:35, Jean Delvare wrote: On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote: Jean, do you want me to pick this

Re: [Patch 1/3] firmware: dmi_scan: rename dmi_table to dmi_decode_table

2015-04-17 Thread Ivan.khoronzhuk
On 17.04.15 11:54, Jean Delvare wrote: Hi Ivan, On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote: On 16.04.15 11:35, Jean Delvare wrote: On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote: Jean, do you want me to pick this patch up or are you going to? Good question, we need

Re: [Patch 1/3] firmware: dmi_scan: rename dmi_table to dmi_decode_table

2015-04-16 Thread Ivan.khoronzhuk
Hi Jean, On 16.04.15 11:35, Jean Delvare wrote: Hi Matt, On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote: On Thu, 02 Apr, at 03:57:01PM, Ivan Khoronzhuk wrote: The "dmi_table" function looks like data instance, but it does DMI table decode. This patch renames it to "dmi_decode_table" n

Re: [Patch 2/3] firmware: dmi_scan: add SBMIOS entry and DMI tables

2015-04-16 Thread Ivan.khoronzhuk
Sorry, sent it from not original mail. On 16.04.15 20:27, subscivan wrote: Jean, On 16.04.15 18:44, Jean Delvare wrote: Hi Ivan, Le Thursday 16 April 2015 à 15:56 +0300, Ivan.khoronzhuk a écrit : On 16.04.15 12:52, Jean Delvare wrote: On Thu, 2 Apr 2015 15:57:02 +0300, Ivan Khoronzhuk

Re: [Patch 2/3] firmware: dmi_scan: add SBMIOS entry and DMI tables

2015-04-16 Thread Ivan.khoronzhuk
Hi Jean, On 16.04.15 12:52, Jean Delvare wrote: Hi Ivan, On Thu, 2 Apr 2015 15:57:02 +0300, Ivan Khoronzhuk wrote: Some utils, like dmidecode and smbios, need to access SMBIOS entry table area in order to get information like SMBIOS version, size, etc. Currently it's done via /dev/mem. But fo

Re: [Patch 2/3] firmware: dmi_scan: add SBMIOS entry and DMI tables

2015-04-03 Thread Ivan.khoronzhuk
On 02.04.15 15:57, Ivan Khoronzhuk wrote: Some utils, like dmidecode and smbios, need to access SMBIOS entry table area in order to get information like SMBIOS version, size, etc. Currently it's done via /dev/mem. But for situation when /dev/mem usage is disabled, the utils have to use dmi sysf

Re: [Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs

2015-04-03 Thread Ivan.khoronzhuk
+ Roy On 02.04.15 18:08, Jean Delvare wrote: Le Thursday 02 April 2015 à 16:02 +0300, Ivan.khoronzhuk a écrit : Hi Jean, Sorry for the late reply. I've send new series "[Patch 0/3] firmware: dmi_scan: add SBMIOS entry point and DMI tables" with all last propositions. Thanks I

Re: [Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs

2015-04-02 Thread Ivan.khoronzhuk
Hi Jean, Sorry for the late reply. I've send new series "[Patch 0/3] firmware: dmi_scan: add SBMIOS entry point and DMI tables" with all last propositions. On 20.03.15 10:16, Jean Delvare wrote: Hi Ivan, On Thu, 19 Mar 2015 19:35:34 +0200, Ivan.khoronzhuk wrote: On 19.03

Re: [dmidecode] [Patch v4] firmware: dmi-sysfs: add SMBIOS entry point area attribute

2015-03-26 Thread Ivan.khoronzhuk
On 26.03.15 15:05, Matt Fleming wrote: On Mon, 16 Mar, at 11:02:29PM, Ivan.khoronzhuk wrote: Matt, I've sent new patch that replaces this one. "[Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs" It can take a while to go via review. OK, thanks Ivan. I've dropp

Re: [Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs

2015-03-19 Thread Ivan.khoronzhuk
On 19.03.15 17:30, Jean Delvare wrote: Hi Ivan, Le Monday 16 March 2015 à 22:57 +0200, Ivan Khoronzhuk a écrit : Some utils, like dmidecode and smbios, need to access SMBIOS entry table area in order to get information like SMBIOS version, size, etc. Currently it's done via /dev/mem. But for

Re: [dmidecode] [Patch v4] firmware: dmi-sysfs: add SMBIOS entry point area attribute

2015-03-19 Thread Ivan.khoronzhuk
On 10.03.15 11:13, Jean Delvare wrote: Hi Ivan, Sorry for the late reply. I think I addressed some points in other replies already, but for completeness let me reply to this post too. Le Wednesday 04 March 2015 à 14:30 +0200, Ivan.khoronzhuk a écrit : On 02/26/2015 11:36 AM, Jean Delvare

Re: [dmidecode] [Patch v4] firmware: dmi-sysfs: add SMBIOS entry point area attribute

2015-03-16 Thread Ivan.khoronzhuk
On 12.03.15 14:22, Matt Fleming wrote: On Tue, 2015-03-10 at 10:13 +0100, Jean Delvare wrote: If Matt is OK to get another version, Let it be smbios_entry_point. If it's more convenient, it should be changed while it's possible. Great, thanks. Ivan, please go ahead and submit a new version,

Re: [dmidecode] [Patch v3] firmware: dmi-sysfs: add SMBIOS entry point area raw attribute

2015-03-07 Thread Ivan.khoronzhuk
Hi Jean, On 03/05/2015 09:46 AM, Jean Delvare wrote: Hi Ivan, On Wed, 04 Mar 2015 14:28:20 +0200, Ivan.khoronzhuk wrote: On 02/26/2015 11:41 AM, Jean Delvare wrote: On Thu, 26 Feb 2015 09:50:42 +0100, Jean Delvare wrote: Please also note that the recently released version 3.0.0 of the

Re: [dmidecode] [Patch v3] firmware: dmi-sysfs: add SMBIOS entry point area raw attribute

2015-03-04 Thread Ivan.khoronzhuk
Hi Jean, See reply at v4. On 02/26/2015 10:50 AM, Jean Delvare wrote: Hi Ivan, Mark and all, Le Tuesday 03 February 2015 à 17:48 +0200, Ivan Khoronzhuk a écrit : On 02/03/2015 04:58 PM, Mark Salter wrote: On Wed, 2015-01-28 at 14:39 +0200, Ivan Khoronzhuk wrote: Some utils, like dmidecode an

Re: [dmidecode] [Patch v3] firmware: dmi-sysfs: add SMBIOS entry point area raw attribute

2015-03-04 Thread Ivan.khoronzhuk
Hi Jean. On 02/26/2015 11:41 AM, Jean Delvare wrote: Replying to myself... On Thu, 26 Feb 2015 09:50:42 +0100, Jean Delvare wrote: Please also note that the recently released version 3.0.0 of the SMBIOS specification introduces a new entry point format, and the firmware is allowed to implement

Re: [dmidecode] [Patch v4] firmware: dmi-sysfs: add SMBIOS entry point area attribute

2015-03-04 Thread Ivan.khoronzhuk
On 02/26/2015 11:36 AM, Jean Delvare wrote: Hi Ivan, Sorry for the late review. On Wed, 4 Feb 2015 19:06:03 +0200, Ivan Khoronzhuk wrote: Some utils, like dmidecode and smbios, need to access SMBIOS entry table area in order to get information like SMBIOS version, size, etc. Currently it's d

Re: [PATCH v3] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-12-26 Thread ivan.khoronzhuk
On 12/18/2013 02:13 PM, Sekhar Nori wrote: On Wednesday 18 December 2013 05:21 PM, ivan.khoronzhuk wrote: Hi, Sekhar This patch is based on "Reuse davinci-nand driver for Keystone arch" series. The series has passed review at https://lkml.org/lkml/2013/12/17/241 and can be fou

Re: [PATCH v3] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-12-18 Thread ivan.khoronzhuk
On 12/05/2013 08:11 PM, Ivan Khoronzhuk wrote: > The problem that the set timings code contains the call of Davinci > platform function davinci_aemif_setup_timing() which is not > accessible if kernel is built for another platform like Keystone. > > The Keysone platform is going to use TI AEMIF dr

Re: [PATCH v4 0/9] Reuse davinci-nand driver for Keystone arch

2013-12-18 Thread ivan.khoronzhuk
On 12/18/2013 09:14 AM, Brian Norris wrote: On Tue, Dec 17, 2013 at 02:59:06PM +0200, Ivan Khoronzhuk wrote: This series contains fixes and updates of Davinci nand driver in order to reuse it for Keystone platform. v3..v4: - mtd: nand: davinci: fix driver registration dropped __init/__e

Re: [PATCH v3 7/9] mtd: nand: davinci: adjust DT properties to MTD generic

2013-12-17 Thread ivan.khoronzhuk
On 12/17/2013 10:50 AM, Brian Norris wrote: > On Thu, Dec 05, 2013 at 07:25:55PM +0200, Ivan Khoronzhuk wrote: >> --- a/drivers/mtd/nand/davinci_nand.c >> +++ b/drivers/mtd/nand/davinci_nand.c >> @@ -558,6 +557,8 @@ static struct davinci_nand_pdata >> "ti,davinci-mask-chipsel",

Re: [PATCH v3 9/9] mtd: nand: davinci: don't request AEMIF address range

2013-12-17 Thread ivan.khoronzhuk
On 12/17/2013 10:42 AM, Brian Norris wrote: On Thu, Dec 05, 2013 at 07:25:57PM +0200, Ivan Khoronzhuk wrote: The TI AEMIF driver registers are used to setup timings for each chip select. The same registers range is used to setup NAND settings. The AEMIF and NAND drivers not use the same register

Re: [PATCH v3 1/9] mtd: nand: davinci: fix driver registration

2013-12-17 Thread ivan.khoronzhuk
On 12/17/2013 11:24 AM, Brian Norris wrote: > On Thu, Dec 05, 2013 at 07:25:49PM +0200, Ivan Khoronzhuk wrote: >> --- a/drivers/mtd/nand/davinci_nand.c >> +++ b/drivers/mtd/nand/davinci_nand.c >> @@ -877,6 +877,7 @@ static int __exit nand_davinci_remove(struct >> platform_device *pdev) >> } >>

Re: [PATCH 2/2] arm: keystone: enable watchdog support

2013-12-10 Thread ivan.khoronzhuk
+ CC devicet...@vger.kernel.org linux-arm-ker...@lists.infradead.org linux-kernel@vger.kernel.org On 12/10/2013 04:47 PM, Ivan Khoronzhuk wrote: After Keystone watchdog driver updates are already merged we can enable WDT in config. Signed-off-by: Ivan Khoronzhuk --- Based on git://git.kernel.o

Re: [PATCH 1/2] arm: dts: keystone: add watchdog entry

2013-12-10 Thread ivan.khoronzhuk
+ CC devicet...@vger.kernel.org linux-arm-ker...@lists.infradead.org linux-kernel@vger.kernel.org On 12/10/2013 04:47 PM, Ivan Khoronzhuk wrote: Add watchdog entry to keystone device tree. Acked-by: Guenter Roeck Signed-off-by: Ivan Khoronzhuk --- Based on git://git.kernel.org/pub/scm/linux/k

Re: [PATCH 2/2] memory: ti-aemif: add bindings for AEMIF driver

2013-12-10 Thread ivan.khoronzhuk
On 12/10/2013 01:09 AM, Kumar Gala wrote: > > On Nov 26, 2013, at 10:27 AM, Grygorii Strashko > wrote: > >> On 11/22/2013 11:04 PM, Kumar Gala wrote: >>> >>> On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote: >>> Add bindings for AEMIF controller drivers/memory/ti-aemif.c >>> >>> Bi

Re: [PATCH v3] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-12-09 Thread ivan.khoronzhuk
On 12/06/2013 11:04 PM, Sekhar Nori wrote: > On 12/5/2013 11:41 PM, Ivan Khoronzhuk wrote: > >> diff --git a/arch/arm/mach-davinci/board-mityomapl138.c >> b/arch/arm/mach-davinci/board-mityomapl138.c >> index 7aa105b..98a66ff 100644 >> --- a/arch/arm/mach-davinci/board-mityomapl138.c >> +++ b/arc

Re: [PATCH v4 1/5] watchdog: davinci: change driver to use WDT core

2013-12-04 Thread ivan.khoronzhuk
On 12/04/2013 08:58 PM, Guenter Roeck wrote: On Wed, Dec 04, 2013 at 08:42:31PM +0200, ivan.khoronzhuk wrote: On 12/04/2013 08:28 PM, Guenter Roeck wrote: On Wed, Dec 04, 2013 at 11:34:46PM +0530, Sekhar Nori wrote: On 11/27/2013 6:18 PM, Ivan Khoronzhuk wrote: To reduce code duplicate and

Re: [PATCH v4 1/5] watchdog: davinci: change driver to use WDT core

2013-12-04 Thread ivan.khoronzhuk
On 12/04/2013 08:28 PM, Guenter Roeck wrote: > On Wed, Dec 04, 2013 at 11:34:46PM +0530, Sekhar Nori wrote: >> On 11/27/2013 6:18 PM, Ivan Khoronzhuk wrote: >>> To reduce code duplicate and increase code readability use WDT core >>> code to handle WDT interface. >>> >>> Remove io_lock as the WDT co

Re: [PATCH v2] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-12-04 Thread ivan.khoronzhuk
On 11/29/2013 06:38 AM, Sekhar Nori wrote: On Wednesday 27 November 2013 08:01 PM, Ivan Khoronzhuk wrote: The problem that the set timings code contains the call of Davinci platform function davinci_aemif_setup_timing() which is not accessible if kernel is built for another platform like Keyston

Re: [PATCH 2/2] memory: ti-aemif: add bindings for AEMIF driver

2013-12-03 Thread ivan.khoronzhuk
On 11/29/2013 05:10 PM, Santosh Shilimkar wrote: On Friday 29 November 2013 10:00 AM, Grygorii Strashko wrote: Hi Kumar Gala, On 11/22/2013 11:06 PM, Kumar Gala wrote: On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk wrote: On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote

Re: [PATCH 1/2] memory: ti-aemif: introduce AEMIF driver

2013-12-03 Thread ivan.khoronzhuk
On 11/29/2013 05:32 PM, Santosh Shilimkar wrote: > On Wednesday 20 November 2013 10:46 AM, Ivan Khoronzhuk wrote: >> Add new AEMIF driver for EMIF16 Texas Instruments controller. >> The EMIF16 module is intended to provide a glue-less interface to >> a variety of asynchronous memory devices like AS

Re: [PATCH v2 00/10] Reuse davinci-nand driver for Keystone arch

2013-12-03 Thread ivan.khoronzhuk
On 11/29/2013 06:28 PM, Santosh Shilimkar wrote: > Ivan, > On Thursday 21 November 2013 06:28 AM, Ivan Khoronzhuk wrote: >> This series contains fixes and updates of Davinci nand driver in >> order to reuse it for Keystone platform. >> >> The series is combination of two following series: >> - Davi

Re: [PATCH v2] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-11-29 Thread ivan.khoronzhuk
On 11/29/2013 06:38 AM, Sekhar Nori wrote: > On Wednesday 27 November 2013 08:01 PM, Ivan Khoronzhuk wrote: >> The problem that the set timings code contains the call of Davinci >> platform function davinci_aemif_setup_timing() which is not >> accessible if kernel is built for another platform like

Re: [PATCH] watchdog: davinci: rename platform driver to davinci-wdt

2013-11-28 Thread ivan.khoronzhuk
On 11/28/2013 08:04 AM, Sekhar Nori wrote: On Wednesday 27 November 2013 09:27 PM, Guenter Roeck wrote: On 11/27/2013 06:00 AM, Sekhar Nori wrote: On Wednesday 27 November 2013 07:01 PM, Ivan Khoronzhuk wrote: As we switch to use the watchdog core which permits more than one active watchdog in

Re: [PATCH v2] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-11-28 Thread ivan.khoronzhuk
+ CC Santosh Shilimkar On 11/27/2013 04:31 PM, Ivan Khoronzhuk wrote: The problem that the set timings code contains the call of Davinci platform function davinci_aemif_setup_timing() which is not accessible if kernel is built for another platform like Keystone. The Keysone platform is going to

Re: [PATCH] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-11-27 Thread ivan.khoronzhuk
On 11/27/2013 03:07 PM, Sekhar Nori wrote: On Wednesday 27 November 2013 04:31 PM, ivan.khoronzhuk wrote: @@ -192,9 +193,15 @@ static __init void davinci_ntosd2_init(void) davinci_cfg_reg(DM644X_ATAEN_DISABLE); /* only one device will be jumpered and detected

Re: [PATCH v2 00/10] Reuse davinci-nand driver for Keystone arch

2013-11-27 Thread ivan.khoronzhuk
On 11/27/2013 03:33 AM, Brian Norris wrote: Hi Ivan, On Thu, Nov 21, 2013 at 01:28:15PM +0200, Ivan Khoronzhuk wrote: This series contains fixes and updates of Davinci nand driver in order to reuse it for Keystone platform. The series is combination of two following series: - Davinci nand driv

Re: [PATCH] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

2013-11-27 Thread ivan.khoronzhuk
On 11/27/2013 10:35 AM, Sekhar Nori wrote: + MTD maintainers On Tuesday 26 November 2013 01:30 AM, Ivan Khoronzhuk wrote: The problem that the set timings code contains the call of Davinci platform function davinci_aemif_setup_timing() which is not accessible if kernel is built for another plat

Re: [PATCH 07/12] memory: davinci-aemif: introduce AEMIF driver

2013-11-27 Thread ivan.khoronzhuk
On 11/27/2013 02:37 AM, Brian Norris wrote: On Tue, Nov 26, 2013 at 01:26:44PM -0500, Santosh Shilimkar wrote: On Tuesday 26 November 2013 12:21 PM, Sekhar Nori wrote: On 11/26/2013 8:35 PM, Santosh Shilimkar wrote: On Tuesday 26 November 2013 02:20 AM, Sekhar Nori wrote: On Monday 11 Novembe

Re: [PATCH v3 1/6] watchdog: davinci: change driver to use WDT core

2013-11-27 Thread ivan.khoronzhuk
On 11/27/2013 09:04 AM, Guenter Roeck wrote: On 11/26/2013 08:31 PM, Sekhar Nori wrote: On Monday 25 November 2013 07:34 PM, Ivan Khoronzhuk wrote: To reduce code duplicate and increase code readability use WDT core code to handle WDT interface. Remove io_lock as the WDT core uses mutex to loc

Re: [PATCH 07/12] memory: davinci-aemif: introduce AEMIF driver

2013-11-26 Thread ivan.khoronzhuk
On 11/26/2013 08:30 PM, Santosh Shilimkar wrote: Ivan, On Tuesday 26 November 2013 12:44 PM, ivan.khoronzhuk wrote: On 11/26/2013 09:20 AM, Sekhar Nori wrote: On Monday 11 November 2013 10:36 PM, Khoronzhuk, Ivan wrote: +static struct platform_driver davinci_aemif_driver = { + .probe

Re: [PATCH 07/12] memory: davinci-aemif: introduce AEMIF driver

2013-11-26 Thread ivan.khoronzhuk
On 11/26/2013 08:26 PM, Santosh Shilimkar wrote: Fair enough Ok, I will do -- Regards, Ivan Khoronzhuk -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.

Re: [PATCH 07/12] memory: davinci-aemif: introduce AEMIF driver

2013-11-26 Thread ivan.khoronzhuk
On 11/26/2013 09:20 AM, Sekhar Nori wrote: > On Monday 11 November 2013 10:36 PM, Khoronzhuk, Ivan wrote: >> Add new AEMIF driver for EMIF16 davinci controller. The EMIF16 module >> is intended to provide a glue-less interface to a variety of >> asynchronous memory devices like ASRA M, NOR and NAND

Re: [PATCH 2/2] memory: ti-aemif: add bindings for AEMIF driver

2013-11-26 Thread ivan.khoronzhuk
On 11/22/2013 11:06 PM, Kumar Gala wrote: On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk wrote: On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: + the chip select signal. + Minimum value is 1 (0 treated as 1). + +- ti

Re: [PATCH 2/2] memory: ti-aemif: add bindings for AEMIF driver

2013-11-26 Thread ivan.khoronzhuk
On 11/22/2013 11:04 PM, Kumar Gala wrote: On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote: Add bindings for AEMIF controller drivers/memory/ti-aemif.c Binding shouldn’t normally refer to code. Just saying something like: Adding binging for TI Async External Memory Interface (AEMIF) co

Re: [PATCH 06/12] mtd: nand: davinci: adjust DT properties to MTD generic

2013-11-26 Thread ivan.khoronzhuk
On 11/26/2013 12:30 PM, Grygorii Strashko wrote: On 11/26/2013 09:03 AM, Sekhar Nori wrote: On Monday 11 November 2013 10:31 PM, Khoronzhuk, Ivan wrote: The properties davinci-ecc-mode, davinci-nand-use-bbt, davinci-nand-buswidth are MTD generic. Correct names for them are: nand-ecc-mode, nand-

Re: [PATCH v2 0/6] Update Davinci watchdog driver

2013-11-25 Thread ivan.khoronzhuk
On 11/25/2013 03:19 PM, ivan.khoronzhuk wrote: On 11/25/2013 03:06 PM, Sekhar Nori wrote: On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote: These patches are intended to update Davinci watchdog to use WDT core and reuse driver for keystone arch, because Keystone uses the similar IP

Re: [PATCH 1/3] mtd: nand: davinci: reuse driver for Keystone arch

2013-11-25 Thread ivan.khoronzhuk
On 11/23/2013 08:15 PM, Arnd Bergmann wrote: On Wednesday 20 November 2013, Ivan Khoronzhuk wrote: --- a/drivers/mtd/nand/davinci_nand.c +++ b/drivers/mtd/nand/davinci_nand.c @@ -523,6 +523,7 @@ static struct nand_ecclayout hwecc4_2048 __initconst = { #if defined(CONFIG_OF) static const stru

Re: [PATCH v3 1/6] watchdog: davinci: change driver to use WDT core

2013-11-25 Thread ivan.khoronzhuk
On 11/25/2013 04:16 PM, Santosh Shilimkar wrote: Ivan, On Monday 25 November 2013 09:04 AM, Ivan Khoronzhuk wrote: To reduce code duplicate and increase code readability use WDT core code to handle WDT interface. Remove io_lock as the WDT core uses mutex to lock each wdt device. Remove wdt_sta

Re: [PATCH v3 5/6] watchdog: davinci: reuse driver for keystone arch

2013-11-25 Thread ivan.khoronzhuk
On 11/25/2013 04:08 PM, Ivan Khoronzhuk wrote: The keystone arch uses the same IP watchdog, so add "ti,keystone-wdt" compatible and correct identity. The Keystone arch is using clocks in DT and source clock for watchdog has to be specified, so add this to binding. Signed-off-by: Ivan Khoronzhuk

Re: [PATCH v2 0/6] Update Davinci watchdog driver

2013-11-25 Thread ivan.khoronzhuk
On 11/25/2013 03:06 PM, Sekhar Nori wrote: On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote: These patches are intended to update Davinci watchdog to use WDT core and reuse driver for keystone arch, because Keystone uses the similar IP like Davinci. This series causes a regression on

Re: Fwd: [PATCH 7/8] watchdog: davinci: add "clocks" property

2013-11-25 Thread ivan.khoronzhuk
On 11/25/2013 02:15 PM, Mark Rutland wrote: On Mon, Nov 25, 2013 at 10:59:45AM +, ivan.khoronzhuk wrote: On 11/23/2013 07:57 PM, Arnd Bergmann wrote: On Wednesday 06 November 2013, ivan.khoronzhuk wrote: @@ -7,6 +7,10 @@ Required properties: - reg : Should contain WDT registers

Re: [PATCH 1/6] watchdog: davinci: change driver to use WDT core

2013-11-25 Thread ivan.khoronzhuk
On 11/25/2013 01:56 PM, Sekhar Nori wrote: On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote: @@ -211,29 +129,34 @@ static int davinci_wdt_probe(struct platform_device *pdev) clk_prepare_enable(wdt_clk); - if (heartbeat < 1 || heartbeat > MAX_HEARTBEAT) - h

Re: Fwd: [PATCH 6/8] watchdog: davinci: reuse driver for keystone arch

2013-11-25 Thread ivan.khoronzhuk
On 11/23/2013 08:02 PM, Arnd Bergmann wrote: > On Wednesday 06 November 2013, ivan.khoronzhuk wrote: > >> @@ -1,13 +1,20 @@ >> -DaVinci Watchdog Timer (WDT) Controller >> +Texas Instruments DaVinci/Keystone Watchdog Timer (WDT) Controller >> >> Required p

Re: Fwd: [PATCH 7/8] watchdog: davinci: add "clocks" property

2013-11-25 Thread ivan.khoronzhuk
On 11/23/2013 07:57 PM, Arnd Bergmann wrote: > On Wednesday 06 November 2013, ivan.khoronzhuk wrote: >> @@ -7,6 +7,10 @@ Required properties: >> >> - reg : Should contain WDT registers location and length >> >> +- clocks: phandle reference to the contro

Re: [PATCH 0/3] Reuse davinci-nand driver for Keystone arch

2013-11-20 Thread ivan.khoronzhuk
On 11/20/2013 10:33 PM, Santosh Shilimkar wrote: On Wednesday 20 November 2013 03:17 PM, Grygorii Strashko wrote: On 11/20/2013 06:24 PM, Ivan Khoronzhuk wrote: This series contains updates of Davinci nand driver, in order to be reused for Keystone platform. Depends on: - Davinci nand driver f

Re: [PATCH 2/2] memory: ti-aemif: add bindings for AEMIF driver

2013-11-20 Thread ivan.khoronzhuk
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: >> +the chip select signal. >> +Minimum value is 1 (0 treated as 1). >> + >> +- ti,cs-wsetup: write setup width, ns >> +Time between the be

Re: [PATCH 6/7] mtd: nand: davinci: extend description of bindings

2013-11-20 Thread ivan.khoronzhuk
On 11/20/2013 05:46 PM, Arnd Bergmann wrote: On Wednesday 20 November 2013, Ivan Khoronzhuk wrote: Extend bindings for davinci_nand driver to be more clear. Signed-off-by: Ivan Khoronzhuk --- .../devicetree/bindings/mtd/davinci-nand.txt | 77 ++-- 1 file changed, 54

Re: [PATCH 10/12] mtd: nand: davinci: don't set timings if AEMIF is used

2013-11-18 Thread ivan.khoronzhuk
On 11/14/2013 04:36 PM, Santosh Shilimkar wrote: On Thursday 14 November 2013 05:53 AM, Nori, Sekhar wrote: On Wednesday 13 November 2013 07:44 PM, Santosh Shilimkar wrote: On Wednesday 13 November 2013 12:02 AM, Sekhar Nori wrote: On Monday 11 November 2013 10:40 PM, Khoronzhuk, Ivan wrote:

Re: [PATCH 07/12] memory: davinci-aemif: introduce AEMIF driver

2013-11-18 Thread ivan.khoronzhuk
On 11/12/2013 06:08 PM, Santosh Shilimkar wrote: > + Greg KH (drivers/memory/* patches goes through his queue) > > On Monday 11 November 2013 12:06 PM, Khoronzhuk, Ivan wrote: >> Add new AEMIF driver for EMIF16 davinci controller. The EMIF16 module >> is intended to provide a glue-less interface t

Re: [PATCH 02/12] mtd: nand: davinci: check required ti,davinci-chipselect property

2013-11-18 Thread ivan.khoronzhuk
On 11/12/2013 05:50 PM, Santosh Shilimkar wrote: On Monday 11 November 2013 11:53 AM, Khoronzhuk, Ivan wrote: The property "ti,davinci-chipselect" is required. So we have to check if it is set. Signed-off-by: Ivan Khoronzhuk --- drivers/mtd/nand/davinci_nand.c | 10 +- 1 file chan

Re: Fwd: [PATCH 4/8] watchdog: davinci: add GET_STATUS option support

2013-11-18 Thread ivan.khoronzhuk
On 11/18/2013 06:24 PM, Guenter Roeck wrote: On Mon, Nov 18, 2013 at 04:21:06PM +0200, ivan.khoronzhuk wrote: On 11/17/2013 04:24 AM, Guenter Roeck wrote: On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote: When watchdog timer is expired we can know about it thought thought -> through or w

Re: Fwd: [PATCH 7/8] watchdog: davinci: add "clocks" property

2013-11-18 Thread ivan.khoronzhuk
On 11/17/2013 04:28 AM, Guenter Roeck wrote: On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote: The Keystone arch is using clocks in DT and source clock for watchdog has to be specified, so add this to binding. Signed-off-by: Ivan Khoronzhuk --- .../devicetree/bindings/watchdog/davinci-wdt.txt

Re: Fwd: [PATCH 1/8] watchdog: davinci: change driver to use WDT core

2013-11-18 Thread ivan.khoronzhuk
On 11/18/2013 04:31 PM, Guenter Roeck wrote: On 11/18/2013 03:47 AM, ivan.khoronzhuk wrote: MODULE_LICENSE("GPL"); -MODULE_ALIAS_MISCDEV(WATCHDOG_MINOR); MODULE_ALIAS("platform:watchdog"); You might want to rename the platform driver to something like davinc

Re: Fwd: [PATCH 6/8] watchdog: davinci: reuse driver for keystone arch

2013-11-18 Thread ivan.khoronzhuk
On 11/17/2013 04:27 AM, Guenter Roeck wrote: On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote: The keystone arch use the same IP watchdog, so add "ti,keystone-wdt" compatible and correct identity. Signed-off-by: Ivan Khoronzhuk --- .../devicetree/bindings/watchdog/davinci-wdt.tx

Re: Fwd: [PATCH 4/8] watchdog: davinci: add GET_STATUS option support

2013-11-18 Thread ivan.khoronzhuk
On 11/17/2013 04:24 AM, Guenter Roeck wrote: > On 11/06/2013 03:32 AM, ivan.khoronzhuk wrote: >> When watchdog timer is expired we can know about it thought > > thought -> through or with > Ok >> GET_STATUS ioctl option. >> >> Signed-off-by: Ivan K

Re: Fwd: [PATCH 3/8] watchdog: davinci: add GET_TIMELEFT option support

2013-11-18 Thread ivan.khoronzhuk
On 11/17/2013 04:22 AM, Guenter Roeck wrote: On 11/06/2013 03:31 AM, ivan.khoronzhuk wrote: Currently, the davinci watchdog can be read while counting, so we can add ability to report the remaining time before the system will reboot. Signed-off-by: Ivan Khoronzhuk --- drivers/watchdog

Re: Fwd: [PATCH 1/8] watchdog: davinci: change driver to use WDT core

2013-11-18 Thread ivan.khoronzhuk
On 11/16/2013 10:29 PM, Guenter Roeck wrote: > On 11/06/2013 03:31 AM, ivan.khoronzhuk wrote: >> To reduce code duplicate and increase code readability use WDT core >> code to handle WDT interface. >> >> Remove io_lock as the WDT core uses mutex to lock each wdt device.

Fwd: [PATCH 1/8] watchdog: davinci: change driver to use WDT core

2013-11-06 Thread ivan.khoronzhuk
To reduce code duplicate and increase code readability use WDT core code to handle WDT interface. Remove io_lock as the WDT core uses mutex to lock each wdt device. Remove wdt_state as the WDT core track state with its own variable. The watchdog_init_timeout() can read timeout value from timeout-

Fwd: [PATCH 2/8] watchdog: davinci: use davinci_wdt_device structure to hold device data

2013-11-06 Thread ivan.khoronzhuk
Some SoCs, like Keystone 2, can support more than one WDT and each watchdog device has to use it's own base address, clock source, wdd device, so add new davinci_wdt_device structure to hold device data. Signed-off-by: Ivan Khoronzhuk --- drivers/watchdog/davinci_wdt.c | 74 +++

Fwd: [PATCH 3/8] watchdog: davinci: add GET_TIMELEFT option support

2013-11-06 Thread ivan.khoronzhuk
Currently, the davinci watchdog can be read while counting, so we can add ability to report the remaining time before the system will reboot. Signed-off-by: Ivan Khoronzhuk --- drivers/watchdog/davinci_wdt.c | 28 1 file changed, 28 insertions(+) diff --git a/driv

Fwd: [PATCH 7/8] watchdog: davinci: add "clocks" property

2013-11-06 Thread ivan.khoronzhuk
The Keystone arch is using clocks in DT and source clock for watchdog has to be specified, so add this to binding. Signed-off-by: Ivan Khoronzhuk --- .../devicetree/bindings/watchdog/davinci-wdt.txt |5 + 1 file changed, 5 insertions(+) diff --git a/Documentation/devicetree/bindings/w

Fwd: [PATCH 8/8] arm: dts: keystone: add watchdog entry

2013-11-06 Thread ivan.khoronzhuk
Add watchdog entry to keystone device tree. Signed-off-by: Ivan Khoronzhuk --- arch/arm/boot/dts/keystone.dts |6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/keystone.dts b/arch/arm/boot/dts/keystone.dts index 100bdf5..a6e5f91 100644 --- a/arch/arm/boot/dts/keyston

Fwd: [PATCH 4/8] watchdog: davinci: add GET_STATUS option support

2013-11-06 Thread ivan.khoronzhuk
When watchdog timer is expired we can know about it thought GET_STATUS ioctl option. Signed-off-by: Ivan Khoronzhuk --- drivers/watchdog/davinci_wdt.c | 13 + 1 file changed, 13 insertions(+) diff --git a/drivers/watchdog/davinci_wdt.c b/drivers/watchdog/davinci_wdt.c index 6cbf2e

Fwd: [PATCH 5/8] watchdog: davinci: add "timeout-sec" property

2013-11-06 Thread ivan.khoronzhuk
Since Davinci WDT has been switched to use WDT core, it became able to support timeout-sec property, so add it to it's binding description. Signed-off-by: Ivan Khoronzhuk --- .../devicetree/bindings/watchdog/davinci-wdt.txt |5 + 1 file changed, 5 insertions(+) diff --git a/Documentat

Fwd: [PATCH 6/8] watchdog: davinci: reuse driver for keystone arch

2013-11-06 Thread ivan.khoronzhuk
The keystone arch use the same IP watchdog, so add "ti,keystone-wdt" compatible and correct identity. Signed-off-by: Ivan Khoronzhuk --- .../devicetree/bindings/watchdog/davinci-wdt.txt | 11 +-- drivers/watchdog/Kconfig |4 ++-- drivers/watchdog/davinci

Fwd: [PATCH 0/8] Update Davinci watchdog driver

2013-11-06 Thread ivan.khoronzhuk
These patches are intended to update Davinci watchdog to use WDT core and reuse driver for keystone arch, because Keystone uses the similar IP like Davinci. See Documentation: Davinci DM646x - http://www.ti.com/lit/ug/spruer5b/spruer5b.pdf Keystone - http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf

Re: [RFC PATCH] Input: gpio_keys: Fix suspend/resume press event lost

2013-02-06 Thread ivan.khoronzhuk
On 02/05/2013 12:40 AM, NeilBrown wrote: On Thu, 31 Jan 2013 15:25:43 +0200 "ivan.khoronzhuk" wrote: On 01/28/2013 08:51 PM, NeilBrown wrote: On Mon, 28 Jan 2013 18:13:14 +0200 "ivan.khoronzhuk" wrote: On 01/22/2013 07:24 AM, NeilBrown wrote: On Mon, 21 Jan 2013 1

Re: [RFC PATCH] Input: gpio_keys: Fix suspend/resume press event lost

2013-01-31 Thread ivan.khoronzhuk
On 01/28/2013 08:51 PM, NeilBrown wrote: On Mon, 28 Jan 2013 18:13:14 +0200 "ivan.khoronzhuk" wrote: On 01/22/2013 07:24 AM, NeilBrown wrote: On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov wrote: Hi Ivan, On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:

Re: [RFC PATCH] Input: gpio_keys: Fix suspend/resume press event lost

2013-01-28 Thread ivan.khoronzhuk
On 01/22/2013 07:24 AM, NeilBrown wrote: On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov wrote: Hi Ivan, On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote: Rebased on linux_omap/master. During suspend/resume the key press can be lost if time of resume sequence is significan

Re: [RFC PATCH] ARM: OMAP4: ID: Improve features detection and check

2012-11-01 Thread ivan.khoronzhuk
On 11/01/2012 01:35 PM, Santosh Shilimkar wrote: On Thursday 01 November 2012 03:53 PM, Ivan Khoronzhuk wrote: Replaces several flags bearing the same meaning. There is no need to set flags due to different omap types here, it can be checked in appropriate places as well. Cc: Tony Lindgren Cc: