On 1/19/2019 12:42 PM, Andreas Kemnade wrote:
On Sat, 19 Jan 2019 12:09:48 +0530
"J, KEERTHY" wrote:
On 1/19/2019 1:18 AM, Tony Lindgren wrote:
* Andreas Kemnade [190118 19:42]:
On Fri, 18 Jan 2019 20:38:47 +0100
Andreas Kemnade wrote:
Hi,
On Fri, 18 Jan 2019 10:36:30
marked by this flag.
And then there are those clocks marked by this flags (on am33xx) which
do not have that autoidle feature at all, so the risk is not too high.
Keerthy, can you please test this series on top of the
related clock patches with your am335x PM test cases?
Can you point me to the clo
d/tps65218.c:284:
+ tps65218_update_bits(tps, TPS65218_REG_CONFIG1,
+ TPS65218_CONFIG1_UVLO_MASK, uvloval,
Some checkpatch warnings to be fixed.
Other than that i tested your patch on am437x-gp-evm for boot and
suspend/resume.
After fixing them you can add my:
Tested-by:
On Thursday 10 January 2019 10:36 AM, Keerthy wrote:
>
>
> On Thursday 10 January 2019 03:06 AM, Tony Lindgren wrote:
>> Hi,
>>
>> * Heiner Kallweit [190109 19:28]:
>>> On 09.01.2019 20:06, Tony Lindgren wrote:
>>>> Commit 6e2d85ec0559 (&q
_MASK;
+ tps65218_options(tps);
Options is not good nomenclature as it doesn't really tell us
anything. Looks like all the values are voltage related to me?
Can we simply call them tps65218_voltage_set_strict,
tps65218_voltage_set_uvlo, tps65218_voltage_set_uv_hyst?
or if you want th
On 12/18/2018 1:35 PM, Christian Hohnstaedt wrote:
Add input voltage configuration options
Signed-off-by: Christian Hohnstaedt
---
Documentation/devicetree/bindings/regulator/tps65218.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git
review by Tony and any of the other OMAP guys.
Adding Keerthy to Cc, he's probably the best person to review these
changes.
Thanks Tony.
But you've dropped the patch, so all he has it a commit log to review?
Lee Jones,
I am subscribed to linux-omap so i have the patch. I will review them
.
Lee Jones,
Do you want me to submit a fix patch? Or you can revert this patch?
Anything fine by me.
Let me know.
Thanks,
Keerthy
Use devm_regmap_add_irq_chip and clean up error path in probe
and also the remove function.
Reported-by: Christian Hohnstaedt
Signed-off-by: Keerthy
---
Changes in v2:
* Cleaned up remove function as well.
Changes in v3:
* Deleted the remove function which was just returning 0
drivers
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
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
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
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
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
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
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
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
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
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
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
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
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
_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
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
_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
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
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
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
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
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
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
'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
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
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
'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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
>> ---
>>
>>
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
>> ---
>>
>>
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
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
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
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
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
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
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.
>>
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.
>>
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
>> ---
>>
>>
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
>> ---
>>
>>
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
>
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
>
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
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
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
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
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
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
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
101 - 200 of 2181 matches
Mail list logo
