[rtc-linux] Re: [PATCHv4 2/2] rtc: cpcap: new rtc driver

2017-03-08 Thread Alexandre Belloni
On 02/03/2017 at 01:27:09 +0100, Sebastian Reichel wrote: > This driver supports the Motorola CPCAP PMIC found on > some of Motorola's mobile phones, such as the Droid 4. > > Tested-by: Tony Lindgren > Signed-off-by: Sebastian Reichel > --- > Changes since PATCHv3: > - Modified DT binding docum

[rtc-linux] Re: [PATCHv4 1/2] dt-bindings: Add vendor prefix for Motorola

2017-03-08 Thread Alexandre Belloni
On 02/03/2017 at 01:27:08 +0100, Sebastian Reichel wrote: > Motorola was involved in semiconductor and mobile phone business. > The "motorola," prefix is already used by a couple of bindings: > > * rtc/rtc-cmos.txt > * mfd/motorola-cpcap.txt > * regulator/cpcap-regulator.txt > > Apart from that i

[rtc-linux] Re: [PATCH] rtc: omap: mark PM methods as __maybe_unused

2017-03-08 Thread Alexandre Belloni
On 01/03/2017 at 15:34:38 -0800, Dmitry Torokhov wrote: > Instead of using #ifdef guards around PM methods, let's annotate > them as __maybe_unused, as it provides better compile coverage. > > Also drop empty stub for omap_rtc_runtime_resume(). > > Signed-off-by: Dmitry Torokhov > --- > drivers

[rtc-linux] Re: [PATCH] rtc: omap: remove incorrect __exit markups

2017-03-08 Thread Alexandre Belloni
On 01/03/2017 at 15:33:23 -0800, Dmitry Torokhov wrote: > Even if bus is not hot-pluggable, devices can be unbound from the > driver via sysfs, so we should not be using __exit annotations on > remove() methods. The only exception is drivers registered with > platform_driver_probe(), which specific

[rtc-linux] Re: [PATCH 00/13] rtc: Add OF device table to I2C drivers that are missing it

2017-03-08 Thread Alexandre Belloni
On 03/03/2017 at 11:29:11 -0300, Javier Martinez Canillas wrote: > Hello, > > This series add OF device ID tables to RTC I2C drivers whose devices are > either used in Device Tree source files or are listed in binding docs as > a compatible string. > > That's done because the plan is to change th

[rtc-linux] Re: Kernel without RTC

2017-03-08 Thread Thomas Gleixner
On Wed, 8 Mar 2017, Alexandre Belloni wrote: > On 08/03/2017 at 13:33:33 +, Hadimani, Jagadish wrote: > > Hello Alexandre, > > > > I guess the Linux kernel uses HPET timer... > > But can we can force Linux kernel to use Tsc or per core timer... > > > > That is probably the case but your are

[rtc-linux] Re: Kernel without RTC

2017-03-08 Thread Alexandre Belloni
On 08/03/2017 at 13:33:33 +, Hadimani, Jagadish wrote: > Hello Alexandre, > > I guess the Linux kernel uses HPET timer... > But can we can force Linux kernel to use Tsc or per core timer... > That is probably the case but your are targeting the wrong subsystem. The timekeeping is done using

[rtc-linux] Re: Kernel without RTC

2017-03-08 Thread Hadimani, Jagadish
Hello Alexandre, I guess the Linux kernel uses HPET timer... But can we can force Linux kernel to use Tsc or per core timer... Sent from my iPhone > On 8 Mar 2017, at 6:47 PM, Alexandre Belloni > wrote: > > Hi, > >> On 07/03/2017 at 00:48:18 +0530, Shah, Nehal-bakulchandra wrote: >> Hi, >>

[rtc-linux] Re: Kernel without RTC

2017-03-08 Thread Alexandre Belloni
Hi, On 07/03/2017 at 00:48:18 +0530, Shah, Nehal-bakulchandra wrote: > Hi, > > Currently we are having hardware which does not have RTC. It is single > processor system. However it does have TSC timer. > > Now, how to use scheduler with only TSC as current kernel scheduler leverage > the RTC f

[rtc-linux] Re: [PATCH v3 3/3] arm64: dts: marvell: add RTC description for Armada 7K/8K

2017-03-08 Thread Gregory CLEMENT
Hi, On lun., févr. 20 2017, Gregory CLEMENT wrote: > This RTC IP is found in the CP110 master and slave which are part of the > Armada 8K SoCs and of the subset family the Armada 7K. > > There is one RTC in each CP but the RTC requires an external > oscillator. However on the Armada 80x0, the