Re: [PATCH V2] thermal/drivers/step_wise: Fix temperature regulation misbehavior

On Friday 08 September 2017 05:17 PM, Daniel Lezcano wrote: > On 08/09/2017 11:49, Keerthy wrote: >> >> >> On Friday 08 September 2017 02:35 PM, Daniel Lezcano wrote: >>> There is a particular situation when the cooling device is cpufreq and the >>> heat

Re: [PATCH V2] thermal/drivers/step_wise: Fix temperature regulation misbehavior

On Friday 08 September 2017 03:19 PM, Keerthy wrote: > > > On Friday 08 September 2017 02:35 PM, Daniel Lezcano wrote: >> There is a particular situation when the cooling device is cpufreq and the >> heat >> dissipation is not efficient enough where the t

Re: [PATCH V2] thermal/drivers/step_wise: Fix temperature regulation misbehavior

On Friday 08 September 2017 03:19 PM, Keerthy wrote: > > > On Friday 08 September 2017 02:35 PM, Daniel Lezcano wrote: >> There is a particular situation when the cooling device is cpufreq and the >> heat >> dissipation is not efficient enough where the t

Re: [PATCH V2] thermal/drivers/step_wise: Fix temperature regulation misbehavior

temperature = <11>; /* millicelsius */ + hysteresis = <2000>; /* millicelsius */ + type = "passive"; + }; +}; + +_cooling_maps { + map1: map1 { + trip = <_high_alert>; + cooling-devi

Re: [PATCH V2] thermal/drivers/step_wise: Fix temperature regulation misbehavior

temperature = <11>; /* millicelsius */ + hysteresis = <2000>; /* millicelsius */ + type = "passive"; + }; +}; + +_cooling_maps { + map1: map1 { + trip = <_high_alert>; + cooling-devi

[PATCH v3] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. This will help in cases of kexec where in a new kernel can boot abruptly. Signed-off-by: Keerthy <j-keer...@ti.com> Acked-by: Kishon Vijay Abraham I <kis...@ti.com> --- Changes in v3: * Pushed the function outside #ifdef CON

[PATCH v3] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. This will help in cases of kexec where in a new kernel can boot abruptly. Signed-off-by: Keerthy Acked-by: Kishon Vijay Abraham I --- Changes in v3: * Pushed the function outside #ifdef CONFIG_PM_SLEEP. * Added more details to commit log

Re: [PATCH v2] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

On Wednesday 06 September 2017 07:26 PM, Keerthy wrote: > Add shutdown handler to cleanly turn off clocks. > > Signed-off-by: Keerthy <j-keer...@ti.com> > Acked-by: Kishon Vijay Abraham I <kis...@ti.com> > --- > > Changes in v2: > > * used a local d

Re: [PATCH v2] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

On Wednesday 06 September 2017 07:26 PM, Keerthy wrote: > Add shutdown handler to cleanly turn off clocks. > > Signed-off-by: Keerthy > Acked-by: Kishon Vijay Abraham I > --- > > Changes in v2: > > * used a local dev pointer instead of dereferen

[PATCH v2] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. Signed-off-by: Keerthy <j-keer...@ti.com> Acked-by: Kishon Vijay Abraham I <kis...@ti.com> --- Changes in v2: * used a local dev pointer instead of dereferencing dev at multiple places. * dra7xx_pcie_stop_link before di

[PATCH v2] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. Signed-off-by: Keerthy Acked-by: Kishon Vijay Abraham I --- Changes in v2: * used a local dev pointer instead of dereferencing dev at multiple places. * dra7xx_pcie_stop_link before disabling clks in the shutdown path. drivers/pci/dwc/pci

[PATCH] ARM: dts: dra7: Set a default parent to mcasp3_ahclkx_mux

Assign a default parent to mcasp3_ahclkx_mux clock using the assigned-clock-parents property. This is helpful in cases like kexec where in the clock parent can be something other than the value at reset. Suggested-by: Tero Kristo <t-kri...@ti.com> Signed-off-by: Keerthy <j-keer.

[PATCH] ARM: dts: dra7: Set a default parent to mcasp3_ahclkx_mux

Assign a default parent to mcasp3_ahclkx_mux clock using the assigned-clock-parents property. This is helpful in cases like kexec where in the clock parent can be something other than the value at reset. Suggested-by: Tero Kristo Signed-off-by: Keerthy --- arch/arm/boot/dts/dra7xx-clocks.dtsi

Re: [PATCH] clk: ti: dra7xx: Reset the mcasp3_ahclkx_mux clock value

On Wednesday 06 September 2017 05:12 PM, Tero Kristo wrote: > On 06/09/17 13:36, Keerthy wrote: >> Reset the mcasp3_ahclkx_mux to abe_24m_fclk. This is needed >> in case of kexec where the reset values might be wiped off. >> >> Signed-off-by: Keerthy <j-keer...@ti.c

Re: [PATCH] clk: ti: dra7xx: Reset the mcasp3_ahclkx_mux clock value

On Wednesday 06 September 2017 05:12 PM, Tero Kristo wrote: > On 06/09/17 13:36, Keerthy wrote: >> Reset the mcasp3_ahclkx_mux to abe_24m_fclk. This is needed >> in case of kexec where the reset values might be wiped off. >> >> Signed-off-by: Keerthy > > Why no

Re: [PATCH] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

On Wednesday 06 September 2017 04:26 PM, Kishon Vijay Abraham I wrote: > > > On Wednesday 06 September 2017 04:23 PM, Kishon Vijay Abraham I wrote: >> Keerthy, >> >> On Wednesday 06 September 2017 04:09 PM, Keerthy wrote: >>> Add shutdown handler to clea

Re: [PATCH] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

On Wednesday 06 September 2017 04:26 PM, Kishon Vijay Abraham I wrote: > > > On Wednesday 06 September 2017 04:23 PM, Kishon Vijay Abraham I wrote: >> Keerthy, >> >> On Wednesday 06 September 2017 04:09 PM, Keerthy wrote: >>> Add shutdown handler to clea

[PATCH] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. Signed-off-by: Keerthy <j-keer...@ti.com> --- drivers/pci/dwc/pci-dra7xx.c | 14 ++ 1 file changed, 14 insertions(+) diff --git a/drivers/pci/dwc/pci-dra7xx.c b/drivers/pci/dwc/pci-dra7xx.c index d4e98f3..66d1cfe 100644 --- a/d

[PATCH] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. Signed-off-by: Keerthy --- drivers/pci/dwc/pci-dra7xx.c | 14 ++ 1 file changed, 14 insertions(+) diff --git a/drivers/pci/dwc/pci-dra7xx.c b/drivers/pci/dwc/pci-dra7xx.c index d4e98f3..66d1cfe 100644 --- a/drivers/pci/dwc/pci

[PATCH] clk: ti: dra7xx: Reset the mcasp3_ahclkx_mux clock value

Reset the mcasp3_ahclkx_mux to abe_24m_fclk. This is needed in case of kexec where the reset values might be wiped off. Signed-off-by: Keerthy <j-keer...@ti.com> --- drivers/clk/ti/clk-7xx.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/drivers/clk/ti/clk-7

[PATCH] clk: ti: dra7xx: Reset the mcasp3_ahclkx_mux clock value

Reset the mcasp3_ahclkx_mux to abe_24m_fclk. This is needed in case of kexec where the reset values might be wiped off. Signed-off-by: Keerthy --- drivers/clk/ti/clk-7xx.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/drivers/clk/ti/clk-7xx.c b/drivers/clk/ti/clk

[PATCH] arm: omap: dra7xx: Set OPT_CLKS_IN_RESET flag for gpio1

gpio1 soft reset fails in the kexec path as the optional clock is not enabled hence enable the HWMOD_CONTROL_OPT_CLKS_IN_RESET flag for gpio1 hwmod. Signed-off-by: Keerthy <j-keer...@ti.com> --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH] arm: omap: dra7xx: Set OPT_CLKS_IN_RESET flag for gpio1

gpio1 soft reset fails in the kexec path as the optional clock is not enabled hence enable the HWMOD_CONTROL_OPT_CLKS_IN_RESET flag for gpio1 hwmod. Signed-off-by: Keerthy --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/mach-omap2

[PATCH v4] mfd: tps65217: Introduce dependency on CONFIG_OF

Currently the driver boots only via device tree hence add a dependency on CONFIG_OF. This leaves with a bunch of unused code so clean that up. This patch also makes use of probe_new function in place of the probe function so as to avoid passing i2c_device_id. Signed-off-by: Keerthy <j-k

[PATCH v4] mfd: tps65217: Introduce dependency on CONFIG_OF

Currently the driver boots only via device tree hence add a dependency on CONFIG_OF. This leaves with a bunch of unused code so clean that up. This patch also makes use of probe_new function in place of the probe function so as to avoid passing i2c_device_id. Signed-off-by: Keerthy Reviewed

Re: [PATCH v3] mfd: tps65217: Introduce dependency on CONFIG_OF

On Wednesday 30 August 2017 01:35 PM, Javier Martinez Canillas wrote: > Hello Keerthy, > > On Wed, Aug 30, 2017 at 7:50 AM, Keerthy <j-keer...@ti.com> wrote: >> Currently the driver boots only via device tree hence add a >> dependency on CONFIG_OF. This leaves with a

Re: [PATCH v3] mfd: tps65217: Introduce dependency on CONFIG_OF

On Wednesday 30 August 2017 01:35 PM, Javier Martinez Canillas wrote: > Hello Keerthy, > > On Wed, Aug 30, 2017 at 7:50 AM, Keerthy wrote: >> Currently the driver boots only via device tree hence add a >> dependency on CONFIG_OF. This leaves with a bunch of unused cod

[PATCH v3] mfd: tps65217: Introduce dependency on CONFIG_OF

Currently the driver boots only via device tree hence add a dependency on CONFIG_OF. This leaves with a bunch of unused code so clean that up. This patch also makes use of probe_new function in place of the probe function so as to avoid passing i2c_device_id. Signed-off-by: Keerthy <j-k

[PATCH v3] mfd: tps65217: Introduce dependency on CONFIG_OF

Currently the driver boots only via device tree hence add a dependency on CONFIG_OF. This leaves with a bunch of unused code so clean that up. This patch also makes use of probe_new function in place of the probe function so as to avoid passing i2c_device_id. Signed-off-by: Keerthy --- Changes

Re: [PATCH v2] mfd: tps65217: Introduce dependency on CONFIG_OF

On Thursday 08 June 2017 07:41 PM, Javier Martinez Canillas wrote: > On Thu, Jun 8, 2017 at 3:32 PM, Enric Balletbo Serra > <eballe...@gmail.com> wrote: >> Hi Keerthy: >> >> 2017-06-08 12:46 GMT+02:00 Keerthy <j-keer...@ti.com>: >>> Currently th

Re: [PATCH v2] mfd: tps65217: Introduce dependency on CONFIG_OF

On Thursday 08 June 2017 07:41 PM, Javier Martinez Canillas wrote: > On Thu, Jun 8, 2017 at 3:32 PM, Enric Balletbo Serra > wrote: >> Hi Keerthy: >> >> 2017-06-08 12:46 GMT+02:00 Keerthy : >>> Currently the driver boots only via device tree hence add a >>

Re: [PATCH] gpio: uniphier: add UniPhier GPIO controller driver

>>> For pinctrl/stm32/pinctrl-stm32.c, >>> I do not see "interrupts", so it just straight maps the irq numbers. >> >> I think OMAP and DaVinci does someting similar too. This is from a recent >> DaVinci patch from Keerthy: >> >> +Example fo

Re: [PATCH] gpio: uniphier: add UniPhier GPIO controller driver

"interrupts", so it just straight maps the irq numbers. >> >> I think OMAP and DaVinci does someting similar too. This is from a recent >> DaVinci patch from Keerthy: >> >> +Example for 66AK2G: >> + >> +gpio0: gpio@2603000 { >> + compat

[PATCH v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy <j-keer...@ti.com> Acked-by: Rob Herring <r...@kernel.org> --- Changes in v4: * Changed documentation link

[PATCH v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy <j-keer...@ti.com> Acked-by: Linus Walleij <l

[PATCH v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy Acked-by: Rob Herring --- Changes in v4: * Changed documentation links. * Added Rob's Ack. * Replaced keystone-k2g

[PATCH v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy Acked-by: Linus Walleij --- Changes in v4: * Couple

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved.

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved.

[v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy <j-keer...@ti.com> Acked-by: Linus Walleij <l

[v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy <j-keer...@ti.com> Acked-by: Rob Herring <r...@kernel.org> --- Changes in v4: * Changed documentation link

[v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy Acked-by: Linus Walleij --- Changes in v4: * Couple

[v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy Acked-by: Rob Herring --- Changes in v4: * Changed documentation links. * Added Rob's Ack. * Replaced keystone-k2g

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved. Oops.

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved. Oops.

Re: [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC

gt;> >> This series depends on Keerthy's gpio node patches on 66AK2G: > Am waiting for Keerthy to send refresh series. Thanks for > note about the deps. Thanks Santosh. I am waiting for a response from Rob H on Suman's question on whether to include power-domains property. > > Regards, > Santosh

Re: [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC

gt;> >> This series depends on Keerthy's gpio node patches on 66AK2G: > Am waiting for Keerthy to send refresh series. Thanks for > note about the deps. Thanks Santosh. I am waiting for a response from Rob H on Suman's question on whether to include power-domains property. > > Regards, > Santosh

[PATCH v2] soc: ti: knav: Add a NULL pointer check for kdev in knav_pool_create

knav_pool_create is an exported function. In the event of a call before knav_queue_probe, we encounter a NULL pointer dereference in the following line. Hence return -EPROBE_DEFER to the caller till the kdev pointer is non-NULL. Signed-off-by: Keerthy <j-keer...@ti.com> --- Changes

[PATCH v2] soc: ti: knav: Add a NULL pointer check for kdev in knav_pool_create

knav_pool_create is an exported function. In the event of a call before knav_queue_probe, we encounter a NULL pointer dereference in the following line. Hence return -EPROBE_DEFER to the caller till the kdev pointer is non-NULL. Signed-off-by: Keerthy --- Changes in v2: * Fixed returning

Re: [PATCH] mfd: lp87565: Convert to use devm_mfd_add_devices

On Sunday 30 July 2017 04:28 PM, Axel Lin wrote: > This fixes missing mfd_remove_devices() call when unload the module. Reviewed-by: Keerthy <j-keer...@ti.com> > > Signed-off-by: Axel Lin <axel@ingics.com> > --- > drivers/mfd/lp87565.c | 7 +++ > 1 fi

Re: [PATCH] mfd: lp87565: Convert to use devm_mfd_add_devices

On Sunday 30 July 2017 04:28 PM, Axel Lin wrote: > This fixes missing mfd_remove_devices() call when unload the module. Reviewed-by: Keerthy > > Signed-off-by: Axel Lin > --- > drivers/mfd/lp87565.c | 7 +++ > 1 file changed, 3 insertions(+), 4 deletions(-) > &

[PATCH] soc: ti: knav: Add a NULL pointer check for kdev in knav_pool_create

knav_pool_create is an exported function. In the event of a call before knav_queue_probe, we encounter a NULL pointer dereference in the following line. Hence return -EPROBE_DEFER to the caller till the kdev pointer is non-NULL. Signed-off-by: Keerthy <j-keer...@ti.com> --- drivers/

[PATCH] soc: ti: knav: Add a NULL pointer check for kdev in knav_pool_create

knav_pool_create is an exported function. In the event of a call before knav_queue_probe, we encounter a NULL pointer dereference in the following line. Hence return -EPROBE_DEFER to the caller till the kdev pointer is non-NULL. Signed-off-by: Keerthy --- drivers/soc/ti/knav_qmss_queue.c | 3

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Monday 24 July 2017 11:54 PM, Rob Herring wrote: > On Tue, Jul 18, 2017 at 04:27:15PM +0530, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy <j-keer...@ti.com> >> --- >> Documentation/devicetree/bindings/gp

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Monday 24 July 2017 11:54 PM, Rob Herring wrote: > On Tue, Jul 18, 2017 at 04:27:15PM +0530, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy >> --- >> Documentation/devicetree/bindings/gpio/gpio-davinci.

Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

On Friday 21 July 2017 04:14 AM, Grygorii Strashko wrote: > > > On 07/20/2017 05:28 PM, David Miller wrote: >> From: Grygorii Strashko >> Date: Thu, 20 Jul 2017 11:08:09 -0500 >> >>> In general patch looks good to me, but it's really unexpected to >>> receive IRQs

Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

On Friday 21 July 2017 04:14 AM, Grygorii Strashko wrote: > > > On 07/20/2017 05:28 PM, David Miller wrote: >> From: Grygorii Strashko >> Date: Thu, 20 Jul 2017 11:08:09 -0500 >> >>> In general patch looks good to me, but it's really unexpected to >>> receive IRQs while CPSW is probing ;( >>

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Friday 21 July 2017 03:04 AM, Grygorii Strashko wrote: > > > On 07/20/2017 05:05 AM, Johan Hovold wrote: >> On Thu, Jul 20, 2017 at 03:32:27PM +0530, Keerthy wrote: >>> On Thursday 20 July 2017 03:20 PM, Johan Hovold wrote: >>>> On Thu, Jul 20, 201

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Friday 21 July 2017 03:04 AM, Grygorii Strashko wrote: > > > On 07/20/2017 05:05 AM, Johan Hovold wrote: >> On Thu, Jul 20, 2017 at 03:32:27PM +0530, Keerthy wrote: >>> On Thursday 20 July 2017 03:20 PM, Johan Hovold wrote: >>>> On Thu, Jul 20, 201

[PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

to n->poll being NULL which is called as part of net_rx_action function. Suggested-by: Sekhar Nori <nsek...@ti.com> Signed-off-by: Keerthy <j-keer...@ti.com> --- drivers/net/ethernet/ti/cpsw.c | 49 +- 1 file changed, 25 insertions(+), 24 del

[PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

to n->poll being NULL which is called as part of net_rx_action function. Suggested-by: Sekhar Nori Signed-off-by: Keerthy --- drivers/net/ethernet/ti/cpsw.c | 49 +- 1 file changed, 25 insertions(+), 24 deletions(-) diff --git a/drivers/net/ethernet

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Thursday 20 July 2017 03:35 PM, Johan Hovold wrote: > On Thu, Jul 20, 2017 at 03:32:27PM +0530, Keerthy wrote: >> On Thursday 20 July 2017 03:20 PM, Johan Hovold wrote: >>> On Thu, Jul 20, 2017 at 02:40:37PM +0530, Keerthy wrote: >>>> On Thursday 20 Jul

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Thursday 20 July 2017 03:35 PM, Johan Hovold wrote: > On Thu, Jul 20, 2017 at 03:32:27PM +0530, Keerthy wrote: >> On Thursday 20 July 2017 03:20 PM, Johan Hovold wrote: >>> On Thu, Jul 20, 2017 at 02:40:37PM +0530, Keerthy wrote: >>>> On Thursday 20 Jul

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Thursday 20 July 2017 03:20 PM, Johan Hovold wrote: > On Thu, Jul 20, 2017 at 02:40:37PM +0530, Keerthy wrote: >> >> >> On Thursday 20 July 2017 12:14 PM, Keerthy wrote: >>> >>> >>> On Wednesday 19 July 2017 04:40 PM, Johan Hovold wrote: >&g

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Thursday 20 July 2017 03:20 PM, Johan Hovold wrote: > On Thu, Jul 20, 2017 at 02:40:37PM +0530, Keerthy wrote: >> >> >> On Thursday 20 July 2017 12:14 PM, Keerthy wrote: >>> >>> >>> On Wednesday 19 July 2017 04:40 PM, Johan Hovold wrote: >&g

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Thursday 20 July 2017 12:14 PM, Keerthy wrote: > > > On Wednesday 19 July 2017 04:40 PM, Johan Hovold wrote: >> On Tue, Jul 18, 2017 at 04:27:14PM +0530, Keerthy wrote: >>> Currently davinci_gpio_irq_setup return value is ignored. Handle the >>> return va

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Thursday 20 July 2017 12:14 PM, Keerthy wrote: > > > On Wednesday 19 July 2017 04:40 PM, Johan Hovold wrote: >> On Tue, Jul 18, 2017 at 04:27:14PM +0530, Keerthy wrote: >>> Currently davinci_gpio_irq_setup return value is ignored. Handle the >>> return va

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Wednesday 19 July 2017 04:40 PM, Johan Hovold wrote: > On Tue, Jul 18, 2017 at 04:27:14PM +0530, Keerthy wrote: >> Currently davinci_gpio_irq_setup return value is ignored. Handle the >> return value appropriately. >> >> Signed-off-by: Keerthy <j-keer...@ti.com

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Wednesday 19 July 2017 04:40 PM, Johan Hovold wrote: > On Tue, Jul 18, 2017 at 04:27:14PM +0530, Keerthy wrote: >> Currently davinci_gpio_irq_setup return value is ignored. Handle the >> return value appropriately. >> >> Signed-off-by: Keerthy >> --- >

Re: [PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

On Wednesday 19 July 2017 03:07 PM, Johan Hovold wrote: > On Tue, Jul 18, 2017 at 04:27:13PM +0530, Keerthy wrote: >> Use the devm version of gpiochip_add_data and pass on the >> return value. Reset the static variables to 0 before returning. > > You need to describe

Re: [PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

On Wednesday 19 July 2017 03:07 PM, Johan Hovold wrote: > On Tue, Jul 18, 2017 at 04:27:13PM +0530, Keerthy wrote: >> Use the devm version of gpiochip_add_data and pass on the >> return value. Reset the static variables to 0 before returning. > > You need to describe

Re: [PATCH 4/4] ARM: dts: keystone-k2g-evm: Add gpio nodes

On Wednesday 19 July 2017 12:43 AM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> keystone-k2g has 2 instances of gpio. The first one has all the 144 GPIOs > > Please use 66AK2G for keystone-k2g. Okay > >> functional( 9 banks wi

Re: [PATCH 4/4] ARM: dts: keystone-k2g-evm: Add gpio nodes

On Wednesday 19 July 2017 12:43 AM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> keystone-k2g has 2 instances of gpio. The first one has all the 144 GPIOs > > Please use 66AK2G for keystone-k2g. Okay > >> functional( 9 banks wi

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Tuesday 18 July 2017 05:01 PM, Sekhar Nori wrote: > Hi Keerthy, > > On Tuesday 18 July 2017 04:27 PM, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy <j-keer...@ti.com> >> --- >> Documentation/

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Tuesday 18 July 2017 05:01 PM, Sekhar Nori wrote: > Hi Keerthy, > > On Tuesday 18 July 2017 04:27 PM, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy >> --- >> Documentation/devicetree/bindings/gpio/gp

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Tuesday 18 July 2017 10:24 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Currently davinci_gpio_irq_setup return value is ignored. Handle the >> return value appropriately. >> >> Signed-off-by: Keerthy <j-keer...@

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Tuesday 18 July 2017 10:24 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Currently davinci_gpio_irq_setup return value is ignored. Handle the >> return value appropriately. >> >> Signed-off-by: Keerthy >> -

Re: [PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

On Tuesday 18 July 2017 10:20 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Use the devm version of gpiochip_add_data and pass on the >> return value. Reset the static variables to 0 before returning. >> >> Signed-

Re: [PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

On Tuesday 18 July 2017 10:20 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Use the devm version of gpiochip_add_data and pass on the >> return value. Reset the static variables to 0 before returning. >> >> Signed-off-by: Keer

[PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

Add a separate compatible for keystone-k2g soc Signed-off-by: Keerthy <j-keer...@ti.com> --- Documentation/devicetree/bindings/gpio/gpio-davinci.txt | 3 ++- drivers/gpio/gpio-davinci.c | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/Documen

[PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

Add a separate compatible for keystone-k2g soc Signed-off-by: Keerthy --- Documentation/devicetree/bindings/gpio/gpio-davinci.txt | 3 ++- drivers/gpio/gpio-davinci.c | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree

[PATCH 0/4] gpio: davinci: Add keystone-k2g support and few clean ups

The driver patches should have no dependency but the device Tree will need the above set. Keerthy (4): gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data gpio: davinci: Handle the return value of davinci_gpio_irq_setup function gpio: davinci: Add a separate compatible

[PATCH 0/4] gpio: davinci: Add keystone-k2g support and few clean ups

The driver patches should have no dependency but the device Tree will need the above set. Keerthy (4): gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data gpio: davinci: Handle the return value of davinci_gpio_irq_setup function gpio: davinci: Add a separate compatible

[PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

Currently davinci_gpio_irq_setup return value is ignored. Handle the return value appropriately. Signed-off-by: Keerthy <j-keer...@ti.com> --- drivers/gpio/gpio-davinci.c | 18 +- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/drivers/gpio/gpio-davinci.c b/d

[PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

Currently davinci_gpio_irq_setup return value is ignored. Handle the return value appropriately. Signed-off-by: Keerthy --- drivers/gpio/gpio-davinci.c | 18 +- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/drivers/gpio/gpio-davinci.c b/drivers/gpio/gpio

[PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

Use the devm version of gpiochip_add_data and pass on the return value. Reset the static variables to 0 before returning. Signed-off-by: Keerthy <j-keer...@ti.com> --- drivers/gpio/gpio-davinci.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/gpi

[PATCH 4/4] ARM: dts: keystone-k2g-evm: Add gpio nodes

keystone-k2g has 2 instances of gpio. The first one has all the 144 GPIOs functional( 9 banks with 16 gpios = 144). The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy <j-keer...@ti.com> --- arch/arm/boot/dts/keystone-k2g.dts

[PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

Use the devm version of gpiochip_add_data and pass on the return value. Reset the static variables to 0 before returning. Signed-off-by: Keerthy --- drivers/gpio/gpio-davinci.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/gpio/gpio-davinci.c b/drivers

[PATCH 4/4] ARM: dts: keystone-k2g-evm: Add gpio nodes

keystone-k2g has 2 instances of gpio. The first one has all the 144 GPIOs functional( 9 banks with 16 gpios = 144). The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy --- arch/arm/boot/dts/keystone-k2g.dtsi | 42

Re: [rtc-linux] Re: [PATCH] RTC: Add functionality to read/write rtc scratch registers

On Friday 14 July 2017 02:13 AM, Alexandre Belloni wrote: > Hi, > > On 05/05/2017 at 00:38:27 +0200, Alexandre Belloni wrote: >> Hi, >> >> On 03/05/2017 at 11:39:34 +0530, Keerthy wrote: >>> On Tuesday 18 April 2017 10:50 AM, Keerthy wrote: >>>> F

Re: [rtc-linux] Re: [PATCH] RTC: Add functionality to read/write rtc scratch registers

On Friday 14 July 2017 02:13 AM, Alexandre Belloni wrote: > Hi, > > On 05/05/2017 at 00:38:27 +0200, Alexandre Belloni wrote: >> Hi, >> >> On 03/05/2017 at 11:39:34 +0530, Keerthy wrote: >>> On Tuesday 18 April 2017 10:50 AM, Keerthy wrote: >>>&

[PATCH] regulator: lp87565: Fix the initial voltage range

The latest documentation reveals that initial voltage range that is supported is starting from 0.6V for all the PMICs belonging to lp87565 family. Fix the same. Signed-off-by: Keerthy <j-keer...@ti.com> Fixes: f0168a9bf ("regulator: lp87565: Add support for lp87565 PMIC regulators&quo

[PATCH] regulator: lp87565: Fix the initial voltage range

The latest documentation reveals that initial voltage range that is supported is starting from 0.6V for all the PMICs belonging to lp87565 family. Fix the same. Signed-off-by: Keerthy Fixes: f0168a9bf ("regulator: lp87565: Add support for lp87565 PMIC regulators") --- drivers/regulat

Re: [PATCH v2] gpio: lp87565: Add support for GPIO

On Thursday 15 June 2017 12:03 PM, Keerthy wrote: > Add driver for lp87565 PMIC family GPIOs. Three GPIOs are supported > and can be configured in Open-drain output or Push-pull output. > > Signed-off-by: Keerthy <j-keer...@ti.com> > --- > > Latest versi

Re: [PATCH v2] gpio: lp87565: Add support for GPIO

On Thursday 15 June 2017 12:03 PM, Keerthy wrote: > Add driver for lp87565 PMIC family GPIOs. Three GPIOs are supported > and can be configured in Open-drain output or Push-pull output. > > Signed-off-by: Keerthy > --- > > Latest version of mfd patch: > > https:/

[PATCH v2] gpio: lp87565: Add support for GPIO

Add driver for lp87565 PMIC family GPIOs. Three GPIOs are supported and can be configured in Open-drain output or Push-pull output. Signed-off-by: Keerthy <j-keer...@ti.com> --- Latest version of mfd patch: https://patchwork.kernel.org/patch/9783079/ Changes in v2: * included *

[PATCH v2] gpio: lp87565: Add support for GPIO

Add driver for lp87565 PMIC family GPIOs. Three GPIOs are supported and can be configured in Open-drain output or Push-pull output. Signed-off-by: Keerthy --- Latest version of mfd patch: https://patchwork.kernel.org/patch/9783079/ Changes in v2: * included * stored the struct regmap

Re: [PATCH 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time

On Tuesday 13 June 2017 07:28 PM, Michał Mirosław wrote: Missing commit log? > Signed-off-by: Michał Mirosław > --- > drivers/regulator/tps65910-regulator.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git

Re: [PATCH 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time

On Tuesday 13 June 2017 07:28 PM, Michał Mirosław wrote: Missing commit log? > Signed-off-by: Michał Mirosław > --- > drivers/regulator/tps65910-regulator.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/drivers/regulator/tps65910-regulator.c >

[PATCH v5] mfd: lp87565: Add lp87565 PMIC support

2-phase outputs configuration, Buck0 is master for Buck0/1 output and Buck2 is master for Buck2/3 output. Signed-off-by: Keerthy <j-keer...@ti.com> Acked-by: Rob Herring <r...@kernel.org> --- The other patches are already pulled by Mark. Hence posting the remaining patch. Changes in

<    2   3   4   5   6   7   8   9   10   11   >