[PATCH v2] tps65218: Use devm_regmap_add_irq_chip and clean up error path in probe

2018-12-06 Thread Keerthy
Use devm_regmap_add_irq_chip and clean up error path in probe. Hence clean up the probe error path and the remove function. Reported-by: Christian Hohnstaedt Signed-off-by: Keerthy --- Changes in v2: * Cleaned up remove function as well. drivers/mfd/tps65218.c | 18 +++--- 1

Re: [PATCH] mfd: tps65218: Use devm_regmap_add_irq_chip and clean up error path in probe

2018-12-06 Thread J, KEERTHY
On 12/7/2018 2:21 AM, Sebastian Reichel wrote: Hi, On Thu, Dec 06, 2018 at 11:07:44PM +0530, Keerthy wrote: Use devm_regmap_add_irq_chip and clean up error path in probe. Reported-by: Christian Hohnstaedt Signed-off-by: Keerthy --- Boot tested on am437x-gp-evm. This is missing cleanup

[PATCH] mfd: tps65218: Use devm_regmap_add_irq_chip and clean up error path in probe

2018-12-06 Thread Keerthy
Use devm_regmap_add_irq_chip and clean up error path in probe. Reported-by: Christian Hohnstaedt Signed-off-by: Keerthy --- Boot tested on am437x-gp-evm. drivers/mfd/tps65218.c | 14 +++--- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/drivers/mfd/tps65218.c b

Re: [PATCH 1/3] ARM: davinci: define gpio interrupts as separate resources

2018-11-19 Thread J, KEERTHY
tely will need explicit calls to platform_get_irq as it will be involving interrupt router and interrupt numbers need not be continuous. So i do not think reverting the patch is the right idea. Regards, Keerthy gpio: davinci: Do not assume continuous IRQ numbering Currently the drive

[PATCH] soc: ti: wkup_m3: Add PRCM int16 as the wake up source

2018-11-11 Thread Keerthy
Add PRCM int16 as the wake up source. Signed-off-by: Keerthy --- drivers/soc/ti/wkup_m3_ipc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/soc/ti/wkup_m3_ipc.c b/drivers/soc/ti/wkup_m3_ipc.c index f5cb8c0..d65e361 100644 --- a/drivers/soc/ti/wkup_m3_ipc.c +++ b/drivers/soc/ti

Re: [PATCH 1/2] opp: ti-opp-supply: Dynamically update u_volt_min

2018-11-11 Thread J, KEERTHY
On 11/8/2018 11:24 AM, Viresh Kumar wrote: On 07-11-18, 10:04, Keerthy wrote: The voltage range (min, max) provided in the device tree is from the data manual and is pretty big, catering to a wide range of devices. On a i2c read/write failure the regulator_set_voltage_triplet function falls

[PATCH 1/2] opp: ti-opp-supply: Dynamically update u_volt_min

2018-11-06 Thread Keerthy
be lesser than the optimal value and in that case that can lead to a hang or crash. Hence set the u_volt_min dynamically to the optimal voltage value. Fixes: 9a835fa6e47 ("PM / OPP: Add ti-opp-supply driver") Signed-off-by: Keerthy --- drivers/opp/ti-opp-supply.c | 3 +++ 1 file changed, 3

[PATCH 2/2] opp: ti-opp-supply: Correct the supply in _get_optimal_vdd_voltage call

2018-11-06 Thread Keerthy
_get_optimal_vdd_voltage call provides new_supply_vbb->u_volt as the reference voltage while it should be really new_supply_vdd->u_volt. Fixes: 9a835fa6e47 ("PM / OPP: Add ti-opp-supply driver") Signed-off-by: Keerthy --- drivers/opp/ti-opp-supply.c | 2 +- 1 file changed, 1

[PATCH 0/2] opp: ti-opp-supply: Fixes

2018-11-06 Thread Keerthy
The series brings in couple of fixes to the ti-opp-supply driver. One of them updates u_volt_min dynamically and avoids hang due to lesser static u_volt_min and the other fixes the supply in _get_optimal_vdd_voltage. Keerthy (2): power: opp: ti-opp-supply: Dynamically update u_volt_min power

[RFC PATCH] i2c: busses: omap: Add the master_xfer_irqless hook

2018-10-18 Thread Keerthy
From: Tero Kristo Add the master_xfer_irqless hook to enable i2c transactions in irq disabled contexts like the poweroff case. Signed-off-by: Tero Kristo Signed-off-by: Keerthy --- This is based on Wolfam's series: https://www.spinics.net/lists/linux-renesas-soc/msg33215.html Tested

Re: [PATCH 4/5] gpio: davinci: Remove unneeded GPIO macro

2018-09-18 Thread Keerthy
On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote: > This macro does nothing and has only one user, remove it. Tested for gpio interrupts on k2g and da850-lcdk Tested-by: Keerthy Acked-by: Keerthy > > Signed-off-by: Andrew F. Davis > --- > arch/arm/mach-davin

Re: [PATCH 5/5] gpio: davinci: Move driver local definitions to driver

2018-09-18 Thread Keerthy
On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote: > These defines, structs and inline functions are used only internally by > the driver, they do not belong in platform_data. Move them. Tested for gpio interrupts on k2g and da850-lcdk Tested-by: Keerthy Acked-by: K

Re: [PATCH 3/5] gpio: davinci: Allocate the correct amount of memory for controller

2018-09-18 Thread Keerthy
'nbank' unused, instead of removing it, > move it down and use it to clean up a loop. For loops with multiple > initializers and/or iteration expressions, especially ones that don't > use those loop counters are quite hard to follow, fix this. > Tested for gpio interrupts on k2g and da8

Re: [PATCH 2/5] gpio: davinci: Use dev name for label and automatic base selection

2018-09-18 Thread Keerthy
On Wednesday 19 September 2018 12:56 AM, Linus Walleij wrote: > On Fri, Aug 31, 2018 at 12:13 PM Andrew F. Davis wrote: > >> Use dev_name to get a unique label and use -1 for a base to get our >> selection automatically. We pull in all GPIOs per chip now so this >> does not have the effect of

Re: [PATCH] dt-bindings: power: Introduce suspend states supported properties

2018-09-12 Thread Keerthy
On Wednesday 12 September 2018 04:32 PM, Sudeep Holla wrote: > > > On 12/09/18 05:09, Keerthy wrote: >> Introuduce linux generic suspend states supported properties. >> It is convenient for the generic suspend path to have >> the knowledge of the sus

[PATCH] dt-bindings: power: Introduce suspend states supported properties

2018-09-11 Thread Keerthy
states are supported. Signed-off-by: Keerthy --- .../devicetree/bindings/power/power-states.txt | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/power-states.txt diff --git a/Documentation/devicetree/bindings/power/power

Re: [PATCH 2/5] gpio: davinci: Use dev name for label and automatic base selection

2018-09-09 Thread Keerthy
On Sunday 09 September 2018 01:11 AM, Grygorii Strashko wrote: > > > On 09/06/2018 09:16 AM, Keerthy wrote: >> >> >> On Wednesday 05 September 2018 04:07 PM, Linus Walleij wrote: >>> On Mon, Sep 3, 2018 at 7:40 AM Keerthy wrote: >>>> On Satu

Re: [PATCH 2/5] gpio: davinci: Use dev name for label and automatic base selection

2018-09-06 Thread Keerthy
On Wednesday 05 September 2018 04:07 PM, Linus Walleij wrote: > On Mon, Sep 3, 2018 at 7:40 AM Keerthy wrote: >> On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote: >>> Use dev_name to get a unique label and use -1 for a base to get our >>> selection au

Re: [PATCH 2/5] gpio: davinci: Use dev name for label and automatic base selection

2018-09-02 Thread Keerthy
On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote: > Use dev_name to get a unique label and use -1 for a base to get our > selection automatically. We pull in all GPIOs per chip now so this > does not have the effect of out of order labels like before. > > We do these both together

Re: [PATCH v2] clocksource: ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs

2018-08-28 Thread J, KEERTHY
On 8/8/2018 6:44 PM, Keerthy wrote: The 32k clocksource is NONSTOP for non-am43 SoCs. Hence add the flag for all the other SoCs. A gentle ping on this one. Reported-by: Tony Lindgren Signed-off-by: Keerthy Acked-by: Tony Lindgren --- Changes in v2: * Changed am43 compatible

Re: [PATCH] soc: ti: pm33xx: Enable DS0 for the platforms on which it is functional

2018-08-22 Thread J, KEERTHY
On 8/22/2018 2:13 PM, Johan Hovold wrote: On Wed, Aug 22, 2018 at 01:50:29PM +0530, J, KEERTHY wrote: On 8/22/2018 1:07 PM, Johan Hovold wrote: On Wed, Aug 22, 2018 at 09:34:09AM +0200, Johan Hovold wrote: On Wed, Aug 22, 2018 at 11:02:31AM +0530, Keerthy wrote: Enable DS0 for only

Re: [PATCH] soc: ti: pm33xx: Enable DS0 for the platforms on which it is functional

2018-08-22 Thread J, KEERTHY
On 8/22/2018 1:07 PM, Johan Hovold wrote: On Wed, Aug 22, 2018 at 09:34:09AM +0200, Johan Hovold wrote: On Wed, Aug 22, 2018 at 11:02:31AM +0530, Keerthy wrote: Enable DS0 for only those platforms on which it is functional Signed-off-by: Keerthy --- arch/arm/mach-omap2/pm33xx-core.c

[PATCH] soc: ti: pm33xx: Enable DS0 for the platforms on which it is functional

2018-08-21 Thread Keerthy
Enable DS0 for only those platforms on which it is functional Signed-off-by: Keerthy --- arch/arm/mach-omap2/pm33xx-core.c| 5 + drivers/soc/ti/pm33xx.c | 9 + include/linux/platform_data/pm33xx.h | 2 ++ 3 files changed, 16 insertions(+) diff --git a/arch/arm/mach

[PATCH v6 1/2] rtc: omap: use of_device_is_system_power_controller function

2018-08-15 Thread Keerthy
Use of_device_is_system_power_controller instead of manually reading the system-power-controller property from the device tree node. Reviewed-by: Johan Hovold Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/rtc/rtc

[PATCH v6 2/2] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-08-15 Thread Keerthy
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll over try again. Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 25 +++-- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c index 44ff4cc

Re: [PATCH v5 2/2] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-08-14 Thread Keerthy
On Tuesday 14 August 2018 02:53 PM, Johan Hovold wrote: > On Wed, Jul 25, 2018 at 11:21:22AM +0530, Keerthy wrote: >> Cut down the shutdown time from 2 seconds to 1 sec. In case of roll >> over try again. >> >> Signed-off-by: Keerthy >> --- >> >>

Re: [PATCH v5 2/2] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-08-14 Thread Keerthy
On Wednesday 25 July 2018 03:00 PM, Alexandre Belloni wrote: > Hi, > > On 25/07/2018 11:21:22+0530, Keerthy wrote: >> Cut down the shutdown time from 2 seconds to 1 sec. In case of roll >> over try again. >> >> Signed-off-by: Keerthy >> --- >> &g

[PATCH v2] clocksource: ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs

2018-08-08 Thread Keerthy
The 32k clocksource is NONSTOP for non-am43 SoCs. Hence add the flag for all the other SoCs. Reported-by: Tony Lindgren Signed-off-by: Keerthy Acked-by: Tony Lindgren --- Changes in v2: * Changed am43 compatible to more generic ti,am43 to cover epos boards. * Added Tony's Ack. drivers

Re: [PATCH] clocksource: ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs

2018-08-08 Thread J, KEERTHY
On 8/8/2018 12:28 PM, Tony Lindgren wrote: * Keerthy [180807 09:29]: The 32k clocksource is NONSTOP for non-am43 SoCs. Hence add the flag for all the other SoCs. Reported-by: Tony Lindgren Signed-off-by: Keerthy Acked-by: Tony Lindgren Thanks Tony. Lokesh pointed out about am43x

Re: [PATCH] arm: dts: am4372: setup rtc as system-power-controller

2018-08-08 Thread Keerthy
On Wednesday 08 August 2018 02:36 PM, Tony Lindgren wrote: > * Keerthy [180725 05:59]: >> RTC alarm2 is connected to pmic_en line and hence can be used to control >> the pmic enabling/disabling. Hence add the system-power-controller for rtc >> node. >>

[PATCH] clocksource: ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs

2018-08-07 Thread Keerthy
The 32k clocksource is NONSTOP for non-am43 SoCs. Hence add the flag for all the other SoCs. Reported-by: Tony Lindgren Signed-off-by: Keerthy --- drivers/clocksource/timer-ti-32k.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/clocksource/timer-ti-32k.c b/drivers

[tip:timers/core] clocksource: ti-32k: Remove CLOCK_SOURCE_SUSPEND_NONSTOP flag

2018-08-02 Thread tip-bot for Keerthy
Commit-ID: c77aee71bbc67c4b0e56f4ce10406b85d4c929c1 Gitweb: https://git.kernel.org/tip/c77aee71bbc67c4b0e56f4ce10406b85d4c929c1 Author: Keerthy AuthorDate: Thu, 2 Aug 2018 12:05:16 +0530 Committer: Thomas Gleixner CommitDate: Thu, 2 Aug 2018 13:35:08 +0200 clocksource: ti-32k: Remove

[PATCH] clocksource: ti-32k: Remove CLOCK_SOURCE_SUSPEND_NONSTOP flag

2018-08-02 Thread Keerthy
the CLOCK_SOURCE_SUSPEND_NONSTOP flag. Suggested-by: Grygorii Strashko Signed-off-by: Keerthy --- drivers/clocksource/timer-ti-32k.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/clocksource/timer-ti-32k.c b/drivers/clocksource/timer-ti-32k.c index 880a861..7368e8e

Re: [PATCH 01/14] thermal: ti-soc-thermal: fix TALERT IRQ handling for DRA752

2018-07-26 Thread Keerthy
On Wednesday 25 July 2018 07:57 PM, Bartlomiej Zolnierkiewicz wrote: > On Wednesday, July 11, 2018 07:49:41 AM J, KEERTHY wrote: >> >> On 5/14/2018 5:12 PM, Bartlomiej Zolnierkiewicz wrote: >>> .report_temperature is not set in dra752_data which >>> results

[PATCH] arm: dts: am4372: setup rtc as system-power-controller

2018-07-24 Thread Keerthy
RTC alarm2 is connected to pmic_en line and hence can be used to control the pmic enabling/disabling. Hence add the system-power-controller for rtc node. Signed-off-by: Keerthy --- arch/arm/boot/dts/am4372.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/am4372.dtsi b

[PATCH v5 1/2] rtc: omap: use of_device_is_system_power_controller function

2018-07-24 Thread Keerthy
Use of_device_is_system_power_controller instead of manually reading the system-power-controller property from the device tree node. Reviewed-by: Johan Hovold Signed-off-by: Keerthy --- Changes in v5: * Added Johan's Reviewed-by drivers/rtc/rtc-omap.c | 3 +-- 1 file changed, 1 insertion

[PATCH v5 2/2] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-24 Thread Keerthy
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll over try again. Signed-off-by: Keerthy --- Changes in v5: * Added an additional check to see if ALARM2 status is not set before retrying. * Cleaned up comments * Also reduced mdelay to 1S lesser as per this commit

Re: [PATCH v4 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-20 Thread Keerthy
On Thursday 19 July 2018 06:16 PM, Keerthy wrote: > > > On Thursday 19 July 2018 06:06 PM, Johan Hovold wrote: >> On Thu, Jul 19, 2018 at 05:52:17PM +0530, Keerthy wrote: >>> On Thursday 19 July 2018 05:23 PM, Keerthy wrote: >>>> On Thursday 19 Ju

Re: [PATCH v4 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-19 Thread Keerthy
On Thursday 19 July 2018 06:06 PM, Johan Hovold wrote: > On Thu, Jul 19, 2018 at 05:52:17PM +0530, Keerthy wrote: >> On Thursday 19 July 2018 05:23 PM, Keerthy wrote: >>> On Thursday 19 July 2018 03:32 PM, Johan Hovold wrote: >>>> On Thu, Jul 12, 2018 at 1

Re: [PATCH v4 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-19 Thread Keerthy
On Thursday 19 July 2018 05:23 PM, Keerthy wrote: > > > On Thursday 19 July 2018 03:32 PM, Johan Hovold wrote: >> On Thu, Jul 12, 2018 at 10:37:37AM +0530, Keerthy wrote: >>> Cut down the shutdown time from 2 seconds to 1 sec. In case of roll >>> over try agai

Re: [PATCH v4 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-19 Thread Keerthy
On Thursday 19 July 2018 03:32 PM, Johan Hovold wrote: > On Thu, Jul 12, 2018 at 10:37:37AM +0530, Keerthy wrote: >> Cut down the shutdown time from 2 seconds to 1 sec. In case of roll >> over try again. >> >> Signed-off-by: Keerthy >> --- >> >>

Re: 4.18.0-rc1-next-20180619 boot failed on beagle board x15

2018-07-17 Thread Keerthy
ith the process here, does >>>> this require anything on my end? And would that require the >>>> accompanying patch to be reverted: "ata: ahci: rpm_put port on >>>> port_stop to match rpm_get in port_start"? There shouldn't be any >>>> problem leaving that one in, but I just want to know before submitting >>>> my next patch set. >>> >>> Well usually the maintainer just reverts the regression causing >>> patch in the related branch and that's it. >>> >>> Stephen, can you please revert in next until we hear back from >>> Tejun? >> >> OK, I have reverted that commit from today. Please let me know when the >> problem is fixed in the libata tree ... Hi Stephen, Thanks for the revert. commit 1dcbe5f2c615337cb7d4e13fab198ab716180733 Author: Stephen Rothwell Date: Tue Jul 17 19:02:59 2018 +1000 With the above top commit i confirm that BEAGLE-X15, AM572X-IDK, AM574X-IDK, DRA7, DRA72 TI platforms booted to prompt. Regards, Keerthy > > Thanks! > > Tony > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >

[PATCH v4 2/4] rtc: OMAP: Add support for rtc-only mode

2018-07-11 Thread Keerthy
the OMAP_RTC_PMIC_REG for any external wake ups for PMIC like the pushbutton and shuts off the PMIC. Hence the split in omap_rtc_power_off. Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 53 -- 1 file changed, 38 insertions(+), 15 deletions(-) diff

[PATCH v4 0/4] rtc: OMAP: Add support for rtc-only mode

2018-07-11 Thread Keerthy
Prepare rtc driver for rtc-only with DDR in self-refresh mode. The patch series is based on top of Johan Hovald's series: https://lkml.kernel.org/r/20180704090558.16647-1-jo...@kernel.org Tested for suspend/resume and poweroff on am437x-gp-evm. Keerthy (4): rtc: omap: Cut down the shutdown

[PATCH v4 4/4] rtc: interface: Add power_off_program to rtc_class_ops

2018-07-11 Thread Keerthy
Add an interface function to set up the rtc for a power_off mode. Signed-off-by: Keerthy --- drivers/rtc/interface.c | 12 drivers/rtc/rtc-omap.c | 1 + include/linux/rtc.h | 2 ++ 3 files changed, 15 insertions(+) diff --git a/drivers/rtc/interface.c b/drivers/rtc

[PATCH v4 3/4] rtc: omap: use of_device_is_system_power_controller function

2018-07-11 Thread Keerthy
Use of_device_is_system_power_controller instead of manually reading the system-power-controller property from the device tree node. Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc

[PATCH v4 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-11 Thread Keerthy
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll over try again. Signed-off-by: Keerthy --- Changes in v4: * Fixed a compilation issue. * Extended the roll over check post interrupt programming. drivers/rtc/rtc-omap.c | 13 +++-- 1 file changed, 11 insertions

Re: [PATCH v3 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-11 Thread J, KEERTHY
On 7/11/2018 7:24 PM, Johan Hovold wrote: On Tue, Jul 10, 2018 at 12:20:49PM +0530, Keerthy wrote: Cut down the shutdown time from 2 seconds to 1 sec. In case of roll over try again. Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 9 +++-- 1 file changed, 7 insertions(+), 2

Re: [PATCH 04/14] thermal: ti-soc-thermal: cleanup COUNTER feature handling for OMAP5

2018-07-10 Thread J, KEERTHY
caused by this patch. Acked-by: Keerthy Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/thermal/ti-soc-thermal/omap5-thermal-data.c | 9 - drivers/thermal/ti-soc-thermal/omap5xxx-bandgap.h | 3 --- 2 files changed, 12 deletions(-) diff --git a/drivers/thermal/ti-soc-thermal

Re: [PATCH 03/14] thermal: ti-soc-thermal: fix comments in omap4-thermal-data.c

2018-07-10 Thread J, KEERTHY
On 5/14/2018 5:12 PM, Bartlomiej Zolnierkiewicz wrote: The comments about ADC code values are incorrect. Fix them. Acked-by: Keerthy Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/thermal/ti-soc-thermal/omap4-thermal-data.c | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [PATCH 02/14] thermal: ti-soc-thermal: fix comment in omap5xxx-bandgap.h

2018-07-10 Thread J, KEERTHY
On 5/14/2018 5:12 PM, Bartlomiej Zolnierkiewicz wrote: The comment for OMAP5430.CORE register offsets is incorrect. Fix it. Acked-by: Keerthy Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/thermal/ti-soc-thermal/omap5xxx-bandgap.h | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH 01/14] thermal: ti-soc-thermal: fix TALERT IRQ handling for DRA752

2018-07-10 Thread J, KEERTHY
On 5/14/2018 5:12 PM, Bartlomiej Zolnierkiewicz wrote: .report_temperature is not set in dra752_data which results in temperature updates not being propagated by ti_bandgap_talert_irq_handler() (it doesn't make much sense to handle TALERT IRQ without reporting temperature updates to the

[PATCH v3 4/4] rtc: interface: Add power_off_program to rtc_class_ops

2018-07-10 Thread Keerthy
Add an interface function to set up the rtc for a power_off mode. Signed-off-by: Keerthy --- Alexandre, If you feel power_off_program will be very use case specific then I can name this as custom_rtc_program so that even other rtc drivers if need be can use this for a custom programming

[PATCH v3 2/4] rtc: OMAP: Add support for rtc-only mode

2018-07-10 Thread Keerthy
the OMAP_RTC_PMIC_REG for any external wake ups for PMIC like the pushbutton and shuts off the PMIC. Hence the split in omap_rtc_power_off. Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 58 +- 1 file changed, 43 insertions(+), 15 deletions(-) diff

[PATCH v3 3/4] rtc: omap: use of_device_is_system_power_controller function

2018-07-10 Thread Keerthy
Use of_device_is_system_power_controller instead of manually reading the system-power-controller property from the device tree node. Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc

[PATCH v3 0/4] rtc: OMAP: Add support for rtc-only mode

2018-07-10 Thread Keerthy
Prepare rtc driver for rtc-only with DDR in self-refresh mode. The patch series is based on top of Johan Hovald's series: https://lkml.kernel.org/r/20180704090558.16647-1-jo...@kernel.org Tested for suspend/resume and poweroff on am437x-gp-evm. Keerthy (4): rtc: omap: Cut down the shutdown

[PATCH v3 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec

2018-07-10 Thread Keerthy
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll over try again. Signed-off-by: Keerthy --- drivers/rtc/rtc-omap.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c index 323ff55..14f2241 100644

Re: [PATCH v2] rtc: OMAP: Add support for rtc-only mode

2018-07-09 Thread Keerthy
On Monday 09 July 2018 02:59 PM, Alexandre Belloni wrote: > On 09/07/2018 09:55:53+0200, Johan Hovold wrote: >> On Mon, Jul 09, 2018 at 11:41:49AM +0530, Keerthy wrote: >>> Prepare rtc driver for rtc-only with DDR in self-refresh mode. >>> omap_rtc_power_off now s

Re: [PATCH v2] rtc: OMAP: Add support for rtc-only mode

2018-07-09 Thread Keerthy
On Monday 09 July 2018 01:25 PM, Johan Hovold wrote: > On Mon, Jul 09, 2018 at 11:41:49AM +0530, Keerthy wrote: >> Prepare rtc driver for rtc-only with DDR in self-refresh mode. >> omap_rtc_power_off now should cater to two features: >> >> 1) RTC plus DDR in self-ref

[PATCH v2 1/2] ARM: OMAP2+: sleep33/43xx: Make sleep actions configurable

2018-07-09 Thread Keerthy
context, put the memory into self refresh and disable the EMIF, and/or invoke the wkup_m3 when entering into WFI. Signed-off-by: Dave Gerlach Signed-off-by: Tero Kristo Signed-off-by: Keerthy --- Changes in v2: * Swapped the bit definitons from patch 2 to 1. arch/arm/mach-omap2/pm33xx

[PATCH v2 2/2] ARM: OMAP2+: sleep33/43xx: Add RTC-Mode support

2018-07-09 Thread Keerthy
and am43xx_emif_sram_table Signed-off-by: Dave Gerlach Signed-off-by: Keerthy --- Changes in v2: * Swapped the bit definitons from patch 2 to 1 arch/arm/mach-omap2/pm-asm-offsets.c | 2 ++ arch/arm/mach-omap2/pm33xx-core.c| 10 +++ arch/arm/mach-omap2/sleep33xx.S | 5 ++-- arch/arm/mach-omap2

[PATCH v2] rtc: OMAP: Add support for rtc-only mode

2018-07-09 Thread Keerthy
the OMAP_RTC_PMIC_REG for any external wake ups for PMIC like the pushbutton and shuts off the PMIC. Hence the split in omap_rtc_power_off. Signed-off-by: Keerthy --- Changes in v2: * Add details in the commit log. * Use of_device_is_system_power_controller to check if rtc node is indeed

[PATCH 2/2] ARM: OMAP2+: sleep43xx: Add RTC-Mode support

2018-07-04 Thread Keerthy
Add support for RTC mode to low level suspend code. This includes providing the rtc base address for the assembly code to configuring the PMIC_PWR_EN line late in suspend to enter RTC+DDR mode. Signed-off-by: Dave Gerlach Signed-off-by: Keerthy --- arch/arm/mach-omap2/pm-asm-offsets.c | 2

[PATCH 1/2] ARM: OMAP2+: sleep33/43xx: Make sleep actions configurable

2018-07-04 Thread Keerthy
context, put the memory into self refresh and disable the EMIF, and/or invoke the wkup_m3 when entering into WFI. Signed-off-by: Dave Gerlach Signed-off-by: Tero Kristo Signed-off-by: Keerthy --- arch/arm/mach-omap2/pm33xx-core.c| 10 --- arch/arm/mach-omap2/sleep33xx.S | 44

Re: [PATCH] rtc: OMAP: Add support for rtc-only mode

2018-07-04 Thread Keerthy
On Wednesday 04 July 2018 01:11 PM, Alexandre Belloni wrote: > Hi, > > On 04/07/2018 12:03:45+0530, Keerthy wrote: >> Prepare rtc driver for rtc-only mode. This involes splitting the power-off >> function so that an external driver can initiate the programming of >

[PATCH] rtc: OMAP: Add support for rtc-only mode

2018-07-04 Thread Keerthy
Prepare rtc driver for rtc-only mode. This involes splitting the power-off function so that an external driver can initiate the programming of setting the power_off to be triggered in the next second. Signed-off-by: Keerthy --- drivers/rtc/interface.c | 12 drivers/rtc/rtc-omap.c | 164

Re: [PATCH] thermal: ti-soc-thermal: remove dead code

2018-07-02 Thread Keerthy
On Monday 02 July 2018 10:00 PM, Eduardo Valentin wrote: > Keerthy, > > On Fri, Jun 29, 2018 at 06:10:26PM +0200, Bartlomiej Zolnierkiewicz wrote: >> >> Hi, >> >> On Wednesday, May 02, 2018 03:20:35 PM Bartlomiej Zolnierkiewicz wrote: >>> Majority of t

[PATCH v3 3/4] clk: ti: Add functions to save/restore clk context

2018-06-21 Thread Keerthy
From: Russ Dill SoCs like AM43XX lose clock registers context during RTC-only suspend. Hence add functions to save/restore the clock registers context. Signed-off-by: Keerthy Signed-off-by: Russ Dill --- Changes in v2: * Replaced clk_dflt_restore instances

[PATCH v3 2/4] clk: clk: Add clk_gate_restore_context function

2018-06-21 Thread Keerthy
The clock gate restore context function enables or disables the gate clocks based on the enable_count. This is done in cases where the clock context is lost and based on the enable_count the clock either needs to be enabled/disabled. Signed-off-by: Keerthy --- Changes in v2: * Renamed

[PATCH v3 1/4] clk: clk: Add functions to save/restore clock context en-masse

2018-06-21 Thread Keerthy
From: Russ Dill Deep enough power saving mode can result into losing context of the clock registers also, and they need to be restored once coming back from the power saving mode. Hence add functions to save/restore clock context. Signed-off-by: Keerthy Signed-off-by: Russ Dill

[PATCH v3 4/4] soc: ti: pm33xx: Save/restore clk context based on enable_off_mode setting

2018-06-21 Thread Keerthy
Save/restore clk context based on enable_off_mode setting. The context needs to be saved at the very end of suspend path and restored at the beginning of resume path. Signed-off-by: Keerthy --- No Changes in v2 arch/arm/mach-omap2/pm33xx-core.c| 15 +++ drivers/soc/ti/pm33xx.c

[PATCH v3 0/4] clk: clk: Add functions to save/restore clock context en-masse

2018-06-21 Thread Keerthy
: * Renamed clk_dflt_restore to clk_gate_restore_context Changes in v3: Corrected the e-mail address of linux-omap list Keerthy (2): clk: clk: Add clk_gate_restore_context function soc: ti: pm33xx: Save/restore clk context based on enable_off_mode setting Russ Dill (2): clk: clk: Add

Re: [PATCH v2 0/4] clk: clk: Add functions to save/restore clock context en-masse

2018-06-21 Thread Keerthy
On Thursday 21 June 2018 01:40 PM, Keerthy wrote: > Deep enough power saving mode can result into losing context of the clock > registers also, and they need to be restored once coming back from the power > saving mode. Hence add functions to save/restore clock context. >

[PATCH v2 2/4] clk: clk: Add clk_gate_restore_context function

2018-06-21 Thread Keerthy
The clock gate restore context function enables or disables the gate clocks based on the enable_count. This is done in cases where the clock context is lost and based on the enable_count the clock either needs to be enabled/disabled. Signed-off-by: Keerthy --- Changes in v2: * Renamed

[PATCH v2 4/4] soc: ti: pm33xx: Save/restore clk context based on enable_off_mode setting

2018-06-21 Thread Keerthy
Save/restore clk context based on enable_off_mode setting. The context needs to be saved at the very end of suspend path and restored at the beginning of resume path. Signed-off-by: Keerthy --- No Changes in v2 arch/arm/mach-omap2/pm33xx-core.c| 15 +++ drivers/soc/ti/pm33xx.c

[PATCH v2 0/4] clk: clk: Add functions to save/restore clock context en-masse

2018-06-21 Thread Keerthy
: * Renamed clk_dflt_restore to clk_gate_restore_context Keerthy (2): clk: clk: Add clk_gate_restore_context function soc: ti: pm33xx: Save/restore clk context based on enable_off_mode setting Russ Dill (2): clk: clk: Add functions to save/restore clock context en-masse clk: ti: Add

[PATCH v2 3/4] clk: ti: Add functions to save/restore clk context

2018-06-21 Thread Keerthy
From: Russ Dill SoCs like AM43XX lose clock registers context during RTC-only suspend. Hence add functions to save/restore the clock registers context. Signed-off-by: Keerthy Signed-off-by: Russ Dill --- Changes in v2: * Replaced clk_dflt_restore instances

[PATCH v2 1/4] clk: clk: Add functions to save/restore clock context en-masse

2018-06-21 Thread Keerthy
From: Russ Dill Deep enough power saving mode can result into losing context of the clock registers also, and they need to be restored once coming back from the power saving mode. Hence add functions to save/restore clock context. Signed-off-by: Keerthy Signed-off-by: Russ Dill

Re: [PATCH 2/4] clk: clk: Add clk_dflt_restore

2018-06-19 Thread J, KEERTHY
On 6/19/2018 11:36 AM, Tero Kristo wrote: On 19/06/18 07:28, Keerthy wrote: The default restore context function enables or disables the clock based on the enable_count. This is done in cases where the clock context is lost and based on the enable_count the clock either needs to be enabled

[PATCH 1/4] clk: clk: Add functions to save/restore clock context en-masse

2018-06-18 Thread Keerthy
From: Russ Dill Deep enough power saving mode can result into losing context of the clock registers also, and they need to be restored once coming back from the power saving mode. Hence add functions to save/restore clock context. Signed-off-by: Keerthy Signed-off-by: Russ Dill --- drivers

[PATCH 3/4] clk: ti: Add functions to save/restore clk context

2018-06-18 Thread Keerthy
From: Russ Dill SoCs like AM43XX lose clock registers context during RTC-only suspend. Hence add functions to save/restore the clock registers context. Signed-off-by: Keerthy Signed-off-by: Russ Dill --- drivers/clk/ti/clock.h| 2 + drivers/clk/ti/divider.c | 36

[PATCH 2/4] clk: clk: Add clk_dflt_restore

2018-06-18 Thread Keerthy
-by: Keerthy --- drivers/clk/clk.c| 19 +++ include/linux/clk-provider.h | 2 ++ 2 files changed, 21 insertions(+) diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c index 7347e06..c201b8b 100644 --- a/drivers/clk/clk.c +++ b/drivers/clk/clk.c @@ -910,6 +910,25 @@ static

[PATCH 0/4] clk: clk: Add functions to save/restore clock context en-masse

2018-06-18 Thread Keerthy
Deep enough power saving mode can result into losing context of the clock registers also, and they need to be restored once coming back from the power saving mode. Hence add functions to save/restore clock context. Tested for DS0 on am437x-gp-evm Based on top of linux-next Keerthy (2): clk

[PATCH 4/4] soc: ti: pm33xx: Save/restore clk context based on enable_off_mode setting

2018-06-18 Thread Keerthy
Save/restore clk context based on enable_off_mode setting. The context needs to be saved at the very end of suspend path and restored at the beginning of resume path. Signed-off-by: Keerthy --- arch/arm/mach-omap2/pm33xx-core.c| 15 +++ drivers/soc/ti/pm33xx.c | 13

Re: [PATCH 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-14 Thread J, KEERTHY
On 6/14/2018 4:48 PM, Linus Walleij wrote: On Thu, Jun 14, 2018 at 10:51 AM, Keerthy wrote: I think the idea is to make it possible to use GPIOLIB_IRQCHIP for banked IRQs but the infrastructure is not yet inside the gpiolib so it is a bit taped on the side right now. Okay. I will take

Re: [PATCH 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-14 Thread Keerthy
On Thursday 14 June 2018 01:59 PM, Linus Walleij wrote: > On Wed, Jun 6, 2018 at 11:18 AM, Keerthy wrote: > >> Currently the driver assumes that the interrupts are continuous >> and does platform_get_irq only once and assumes the rest are continuous, >> instead call

Re: [PATCH 1/2] gpio: davinci: Move fetching IRQ to beginning of probe

2018-06-12 Thread Keerthy
On Tuesday 12 June 2018 08:05 PM, J, KEERTHY wrote: > > > On 6/12/2018 6:39 PM, Linus Walleij wrote: >> On Wed, Jun 6, 2018 at 11:18 AM, Keerthy wrote: >> >>> Currently IRQ resource fetching is done at the very end of probe. >>> In case the of IRQ r

[PATCH v4 1/2] gpio: davinci: Shuffle IRQ resource fetching from DT to beginning of probe

2018-06-12 Thread Keerthy
This is needed in case of PROBE_DEFER if IRQ resource is not yet ready. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850-lcdk board. Changes in v3: Changed type of bank_irq to int from unsigned drivers/gpio/gpio-davinci.c | 29 +++-- 1 file

[PATCH v4 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-12 Thread Keerthy
Currently the driver assumes that the interrupts are continuous and does platform_get_irq only once and assumes the rest are continuous, instead call platform_get_irq for all the interrupts and store them in an array for later use. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850

Re: [PATCH v3 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-12 Thread J, KEERTHY
On 6/13/2018 6:36 AM, J, KEERTHY wrote: On 6/13/2018 1:36 AM, Grygorii Strashko wrote: On 06/12/2018 02:59 AM, Keerthy wrote: Currently the driver assumes that the interrupts are continuous and does platform_get_irq only once and assumes the rest are continuous, instead call

Re: [PATCH v3 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-12 Thread J, KEERTHY
On 6/13/2018 1:36 AM, Grygorii Strashko wrote: On 06/12/2018 02:59 AM, Keerthy wrote: Currently the driver assumes that the interrupts are continuous and does platform_get_irq only once and assumes the rest are continuous, instead call platform_get_irq for all the interrupts and store them

Re: [PATCH 1/2] gpio: davinci: Move fetching IRQ to beginning of probe

2018-06-12 Thread J, KEERTHY
On 6/12/2018 6:39 PM, Linus Walleij wrote: On Wed, Jun 6, 2018 at 11:18 AM, Keerthy wrote: Currently IRQ resource fetching is done at the very end of probe. In case the of IRQ resource not being ready, we defer probe and need to revert prior changes. Hence move it to the beginning

[PATCH v3 1/2] gpio: davinci: Shuffle IRQ resource fetching from DT to beginning of probe

2018-06-12 Thread Keerthy
This is needed in case of PROBE_DEFER if IRQ resource is not yet ready. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850-lcdk board. Changes in v3: Changed type of bank_irq to int from unsigned * Changed irqs type from unsigned to int drivers/gpio/gpio-davinci.c | 29

[PATCH v3 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-12 Thread Keerthy
Currently the driver assumes that the interrupts are continuous and does platform_get_irq only once and assumes the rest are continuous, instead call platform_get_irq for all the interrupts and store them in an array for later use. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850

Re: [PATCH v2 1/2] gpio: davinci: Shuffle IRQ resource fetching from DT to beginning of probe

2018-06-11 Thread Keerthy
On Tuesday 12 June 2018 11:15 AM, Alexander Stein wrote: > On Tuesday, June 12, 2018, 7:27:52 AM CEST Keerthy wrote: >> This is needed in case of PROBE_DEFER if IRQ resource is not yet ready. >> >> Signed-off-by: Keerthy >> --- >> [...] >> --- a/drive

[PATCH v2 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-11 Thread Keerthy
Currently the driver assumes that the interrupts are continuous and does platform_get_irq only once and assumes the rest are continuous, instead call platform_get_irq for all the interrupts and store them in an array for later use. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850

[PATCH v2 1/2] gpio: davinci: Shuffle IRQ resource fetching from DT to beginning of probe

2018-06-11 Thread Keerthy
This is needed in case of PROBE_DEFER if IRQ resource is not yet ready. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850-lcdk and keystone-k2g-evm boards. No Changes in v2 drivers/gpio/gpio-davinci.c | 29 +++-- 1 file changed, 11 insertions(+), 18

[PATCH 2/2] gpio: davinci: Do not assume continuous IRQ numbering

2018-06-06 Thread Keerthy
Currently the driver assumes that the interrupts are continuous and does platform_get_irq only once and assumes the rest are continuous, instead call platform_get_irq for all the interrupts and store them in an array for later use. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850

[PATCH 1/2] gpio: davinci: Move fetching IRQ to beginning of probe

2018-06-06 Thread Keerthy
Currently IRQ resource fetching is done at the very end of probe. In case the of IRQ resource not being ready, we defer probe and need to revert prior changes. Hence move it to the beginning of the probe so as to avoid reverting. Signed-off-by: Keerthy --- Tested for GPIO Interrupts on da850

[PATCH v2] ARM: dts: da850: Fix interrups property for gpio

2018-06-05 Thread Keerthy
The intc #interrupt-cells is equal to 1. Currently gpio node has 2 cells per IRQ which is wrong. Remove the additional cell for each of the interrupts. Signed-off-by: Keerthy Fixes: 2e38b946dc54 ("ARM: davinci: da850: add GPIO DT node") --- Changes in v2: * Fixed $Subject arch/ar

  1   2   3   4   5   6   7   8   9   10   >