On 01/09/2016 00:59, Gabriele Mazzotta wrote:
> Return an error if the user tries to set an alarm that isn't
> supported by the hardware.
>
> Signed-off-by: Gabriele Mazzotta
> ---
> drivers/rtc/rtc-cmos.c | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/rt
Return an error if the user tries to set an alarm that isn't
supported by the hardware.
Signed-off-by: Gabriele Mazzotta
---
drivers/rtc/rtc-cmos.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/rtc/rtc-cmos.c b/drivers/rtc/rtc-cmos.c
index 4cdb335..b3f9298 100
Some BIOSes, such as the one of the Dell XPS13 9333, wake the system
when an alarm goes off without informing the OS. If any of the
RTC_IRQMASK bits is set when this happens and hpet is enabled,
the alarm is not automatically cleared at resume. As consequence,
the user must manually clear the alarm
Some platform firmware may interfere with the RTC alarm over suspend,
resulting in the kernel and hardware having different ideas about system
state but also potentially causing problems with firmware that assumes the
OS will clean this case up. This patch restores the RTC alarm on resume
to ensur
Hi Julia,
On Wed, Aug 31, 2016 at 10:05:25AM +0200, Julia Lawall wrote:
> Check for rtc_class_ops structures that are only passed to
> devm_rtc_device_register, rtc_device_register,
> platform_device_register_data, all of which declare the corresponding
> parameter as const. Declare rtc_class_ops
>From 633c012ba6c8f9bc6cf475d2434ca450cd06b18e Mon Sep 17 00:00:00 2001
From: Raghavendra Ganiga
Date: Wed, 31 Aug 2016 22:56:41 +0530
Subject: [PATCH] rtc: ds1347: changed raw spi calls to register map calls
This patch changes calls of spi read write calls to register map
read and write calls in
On Wednesday 31 August 2016 03:18 AM, Alexandre Belloni wrote:
> Hi,
>
> Please fix the subject, this patch is ds1347 specific.
>
Yes I will fix the subject
> On 31/08/2016 at 01:28:33 +0530, RAGHAVENDRA GANIGA wrote :
>> From 2ec82b6c9b99647e31d26c4c828dc7c51af8a633 Mon Sep 17 00:00:00 2001
>
Looks ok,
thank you!
Am 31.08.2016 um 18:15 schrieb Alexandre Belloni:
> The rtc-asm9260 driver uses a discrete spinlock (wrongly uninitialized).
> Use the rtc mutex to lock mmio accesses instead.
>
> Signed-off-by: Alexandre Belloni
> ---
> drivers/rtc/rtc-asm9260.c | 20 +---
On 19/08/2016 at 15:42:23 +0800, Chen-Yu Tsai wrote :
> The ac100 device tree binding specifies the usage of clock-output-names
> to specify the names of its 3 clock outputs. This is needed for orphan
> clock resolution, when the ac100 is probed much later than any clocks
> that consume any of its
The rtc-asm9260 driver uses a discrete spinlock (wrongly uninitialized).
Use the rtc mutex to lock mmio accesses instead.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-asm9260.c | 20 +---
1 file changed, 5 insertions(+), 15 deletions(-)
diff --git a/drivers/rtc/rtc-asm92
The rtc-asm9260 driver compiles correctly on other architectures, add
COMPILE_TEST to improve code coverage.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index e215f50794b6..
On 31/08/2016 at 17:14:27 +0200, Oleksij Rempel wrote :
> Hi
>
> Am 31.08.2016 um 02:18 schrieb Alexandre Belloni:
> > The rtc-asm9260 driver uses a discrete spinlock (wrongly uninitialized).
> > Use the rtc mutex to lock mmio accesses instead.
> >
> > Signed-off-by: Alexandre Belloni
> > ---
>
On 31/08/2016 at 17:05:58 +0200, Gabriele Mazzotta wrote :
> On 31/08/2016 01:28, Alexandre Belloni wrote:
> > Hi,
> >
> > On 25/08/2016 at 16:54:18 +0200, Gabriele Mazzotta wrote :
> >> Hi,
> >>
> >> were you able to verify that no other driver is affect?
> >>
> >
> > I had a closer look at the
Hi
Am 31.08.2016 um 02:18 schrieb Alexandre Belloni:
> The rtc-asm9260 driver uses a discrete spinlock (wrongly uninitialized).
> Use the rtc mutex to lock mmio accesses instead.
>
> Signed-off-by: Alexandre Belloni
> ---
> drivers/rtc/rtc-asm9260.c | 16 ++--
> 1 file changed, 2 in
On 31/08/2016 01:28, Alexandre Belloni wrote:
> Hi,
>
> On 25/08/2016 at 16:54:18 +0200, Gabriele Mazzotta wrote :
>> Hi,
>>
>> were you able to verify that no other driver is affect?
>>
>
> I had a closer look at the issue. I think what is happening is that you
> don't enter the do/while loop in
Enjoy!
The following changes since commit 694d0d0bb2030d2e36df73e2d23d5770511dbc8d:
Linux 4.8-rc2 (2016-08-14 19:11:36 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
ib-mfd-regulator-rtc-v4.9-1
for you to fetch changes up to 5d2fd5
Enjoy!
The following changes since commit 694d0d0bb2030d2e36df73e2d23d5770511dbc8d:
Linux 4.8-rc2 (2016-08-14 19:11:36 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
tags/ib-mfd-regulator-rtc-v4.9
for you to fetch changes up to ddc
On Thu, 11 Aug 2016, Neil Armstrong wrote:
> In order to support the Qualcomm MDM9615 SoC, add support for the
> RPM regulator entries in the qcom-rpm driver.
>
> Acked-by: Bjorn Andersson
> Acked-by: Lee Jones
> Signed-off-by: Neil Armstrong
Quick note. In future can you keep these chronolo
Check for rtc_class_ops structures that are only passed to
devm_rtc_device_register, rtc_device_register,
platform_device_register_data, all of which declare the corresponding
parameter as const. Declare rtc_class_ops structures that have these
properties as const.
The semantic patch that makes t
19 matches
Mail list logo
