Configure the clock source to external clock if available.
External clock is preferred as it can be ticking during suspend.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/rtc/rtc-omap.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git
rtc can either be supplied from internal 32k clock or external crystal
generated 32k clock. Internal clock is SOC specific and the external
clock is board dependent. Adding the corresponding nodes.
Signed-off-by: Keerthy j-keer...@ti.com
---
Documentation/devicetree/bindings/rtc/rtc-omap.txt |
The rtc can be clocked by an internal 32K clock. Adding the support
to enable the same.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/rtc/rtc-omap.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c
index 8b6355f..f31c012 100644
Currently apart from dra7, omap5 and amx3 all the other SoCs
are identified using cpu_is_* functions which is not right since
they are all SoCs(System on Chips). Hence changing the SoC
identific??tion code to use soc_is instead of cpu_is and keeping
defines for cpu_is where needed. This allows us
The series is applicable for all am437x series of processors.
It adds clock handling support. Boot tested on am437x-gp-evm.
Keerthy (3):
ARM: dts: AM437x: Add the internal and external clock nodes for rtc
rtc: omap: Add internal clock enabling support
rtc: omap: Add external clock enabling
On Tuesday 18 August 2015 02:22 PM, Johan Hovold wrote:
On Tue, Aug 18, 2015 at 02:13:28PM +0530, Keerthy wrote:
The series is applicable for all am437x series of processors.
It adds clock handling support. Boot tested on am437x-gp-evm.
Keerthy (2):
ARM: dts: AM437x: Add the internal and
Configure the clock source to external clock if available.
External clock is preferred as it can be ticking during suspend.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/rtc/rtc-omap.c | 33 ++---
1 file changed, 30 insertions(+), 3 deletions(-)
diff --git
The rtc can be clocked by an internal 32K clock. Adding the support
to enable the same.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/rtc/rtc-omap.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c
index 8b6355f..f31c012 100644
rtc can either be supplied from internal 32k clock or external crystal
generated 32k clock. Internal clock is SOC specific and the external
clock is board dependent. Adding the corresponding nodes.
Signed-off-by: Keerthy j-keer...@ti.com
---
arch/arm/boot/dts/am4372.dtsi| 2 ++
The series is applicable for all am437x series of processors.
It adds clock handling support. Boot tested on am437x-gp-evm.
Keerthy (2):
ARM: dts: AM437x: Add the internal and external clock nodes for rtc
rtc: omap: Add external clock enabling support
Changes in v3:
* Split internal and
On Tue, Aug 18, 2015 at 11:48:44AM +0530, Keerthy wrote:
Configure the clock source to external clock if available.
External clock is preferred as it can be ticking during suspend.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/rtc/rtc-omap.c | 33 ++---
1
* NeilBrown n...@brown.name [150729 17:29]:
Now that twl4030_bci_probe can safely return -EPROBE_DEFER,
do so when devm_usb_get_phy_by_node returns that error.
Signed-off-by: NeilBrown n...@brown.name
---
drivers/power/twl4030_charger.c |6 +-
1 file changed, 5 insertions(+), 1
The rtc can be clocked by an internal 32K clock. Adding the support
to enable the same.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/rtc/rtc-omap.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c
index 8b6355f..f31c012 100644
rtc can either be supplied from internal 32k clock or external crystal
generated 32k clock. Internal clock is SOC specific and the external
clock is board dependent. Adding the corresponding nodes.
Signed-off-by: Keerthy j-keer...@ti.com
---
arch/arm/boot/dts/am4372.dtsi| 2 ++
Configure the clock source to external clock if available.
External clock is preferred as it can be ticking during suspend.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/rtc/rtc-omap.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git
The series is applicable for all am437x series of processors.
It adds clock handling support. Boot tested on am437x-gp-evm.
Keerthy (2):
ARM: dts: AM437x: Add the internal and external clock nodes for rtc
rtc: omap: Add external clock enabling support
Changes in v4:
* Optimized pointer
On Tue, Aug 18, 2015 at 02:13:28PM +0530, Keerthy wrote:
The series is applicable for all am437x series of processors.
It adds clock handling support. Boot tested on am437x-gp-evm.
Keerthy (2):
ARM: dts: AM437x: Add the internal and external clock nodes for rtc
rtc: omap: Add external
As per CCF documentation (clk.txt) the clk_prepare/unprepare APIs
are not allowed in atomic context. But now OMAP GPIO driver
uses them while applying debounce settings and as part
of PM runtime irqsafe operations:
- omap_gpio_debounce() is holding the lock with IRQs off.
+
This patch converts TI OMAP GPIO driver to use generic irq handler
instead of chained IRQ handler. This way OMAP GPIO driver will be
compatible with RT kernel where it will be forced thread IRQ handler
while in non-RT kernel it still will be executed in HW IRQ context.
As part of this change the
The PM runtime API can't be used in atomic contex on -RT even if
it's configured as irqsafe. As result, below error report can
be seen when PM runtime API called from IRQ chip's callbacks
irq_startup/irq_shutdown/irq_set_type, because they are
protected by RAW spinlock:
BUG: sleeping function
According to TRMs:
Required input line stable =
(the value of the GPIO_DEBOUNCINGTIME[7:0].DEBOUNCETIME + 1) × 31,
where the value of the GPIO_DEBOUNCINGTIME[7:0].DEBOUNCETIME bit field
is from 0 to 255.
But now omap2_set_gpio_debounce() will calculate debounce time and
behave incorrectly in
Switch OMAP GPIO driver to use platform_get_irq(), because
it is not recommened to use platform_get_resource(pdev, IORESOURCE_IRQ, ..)
for requesting IRQ resources any more, as they can be not ready yet
in case of DT-boot.
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
---
The access to HW registers has to be be protected in
omap_gpio_irq_handler(), as it may race with code executed on
another CPUs.
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
---
drivers/gpio/gpio-omap.c | 8
1 file changed, 8 insertions(+)
diff --git
The bank-chip.irqdomain is uninitialized at the moment when
irq_domain_remove() is called, so remove this call.
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
---
drivers/gpio/gpio-omap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpio/gpio-omap.c
Hi,
This patch series contains set of trivial fixes and improvements, and also
patches which fixes wrong APIs usage in atomic context as for -RT as for
non-RT kernel. The final goal of this series is to make TI OMAP GPIO
driver compatible with -RT kernel as much as possible.
Patch 1-4: trivial
On Tuesday 18 August 2015 03:40 PM, Keerthy wrote:
Currently apart from dra7, omap5 and amx3 all the other SoCs
are identified using cpu_is_* functions which is not right since
they are all SoCs(System on Chips). Hence changing the SoC
identificätion code to use soc_is instead of cpu_is and
On Thu, Aug 13, 2015 at 03:08:45AM -0700, Tony Lindgren wrote:
The following changes since commit 24da741c678f865de3182194604dbddcc7fc7f3c:
Merge branch 'dm814x-soc' into omap-for-v4.3/soc (2015-07-23 21:59:18 -0700)
are available in the git repository at:
On Thu, Aug 13, 2015 at 03:08:46AM -0700, Tony Lindgren wrote:
The following changes since commit ed05637c30e6d13e5793aab64d6a6e57e30228af:
ARM: dts: omap3-devkit8000: Add ADS7846 Touchscreen support (2015-08-06
02:43:09 -0700)
are available in the git repository at:
On Tue, 18 Aug 2015 01:07:58 -0700 Tony Lindgren t...@atomide.com
wrote:
* NeilBrown n...@brown.name [150729 17:29]:
Now that twl4030_bci_probe can safely return -EPROBE_DEFER,
do so when devm_usb_get_phy_by_node returns that error.
Signed-off-by: NeilBrown n...@brown.name
---
HI,
On Mon, Aug 17, 2015 at 06:28:11PM -0700, Matt Reimer wrote:
This doesn't seem to work for higher speeds, like 2.6 MHz. hssclh and
hsscll end up going negative.
My case is an OMAP3 trying to configure i2c1 at 2.6 MHz, on which it talks
to TPS65950. I end up with the following values:
On Fri, Jul 24, 2015 at 9:03 AM, Pali Rohár pali.ro...@gmail.com wrote:
Hello,
when on N900 (real HW or qemu) I run this command
/ # echo 0 /sys/devices/platform/omapdss/overlay0/enabled echo 0
/sys/class/graphics/fb0/size
then kernel crash with this error message
/ # [ 29.904113]
Add DCAN sleep pins to save some power during suspend.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts | 24
1 file changed, 20 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts
On Tuesday 28 July 2015 13:56:02 Pali Rohár wrote:
On Friday 24 July 2015 18:03:42 Pali Rohár wrote:
Hello,
when on N900 (real HW or qemu) I run this command
/ # echo 0 /sys/devices/platform/omapdss/overlay0/enabled echo 0
/sys/class/graphics/fb0/size
then kernel crash with
On 8/18/2015 4:10 AM, Grygorii Strashko wrote:
Hi,
This patch series contains set of trivial fixes and improvements, and also
patches which fixes wrong APIs usage in atomic context as for -RT as for
non-RT kernel. The final goal of this series is to make TI OMAP GPIO
driver compatible with -RT
34 matches
Mail list logo
