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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
>
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
>
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
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
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
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
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
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
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
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
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
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
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
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
:
* 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
:
* 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
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.
>
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.
>
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
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
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
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
:
* 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
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
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
:
* 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
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
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
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
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
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
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
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
-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
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
-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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
201 - 300 of 2181 matches
Mail list logo
