On Mon, 16 Oct 2017, David Kozub wrote:
> On Mon, 16 Oct 2017, Thomas Gleixner wrote:
> > --- a/drivers/clocksource/cs5535-clockevt.c
> > +++ b/drivers/clocksource/cs5535-clockevt.c
> > @@ -117,7 +117,8 @@ static irqreturn_t mfgpt_tick(int irq, void *dev_id)
> > /* Turn off the clock (and
On Mon, 16 Oct 2017, David Kozub wrote:
> On Mon, 16 Oct 2017, Thomas Gleixner wrote:
> > --- a/drivers/clocksource/cs5535-clockevt.c
> > +++ b/drivers/clocksource/cs5535-clockevt.c
> > @@ -117,7 +117,8 @@ static irqreturn_t mfgpt_tick(int irq, void *dev_id)
> > /* Turn off the clock (and
On Mon, 16 Oct 2017, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, David Kozub wrote:
On Thu, 12 Oct 2017, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Daniel Lezcano wrote:
The real question is why
/* Set the clock scale and enable the event mode for CMP2 */
val = MFGPT_SCALE |
On Mon, 16 Oct 2017, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, David Kozub wrote:
On Thu, 12 Oct 2017, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Daniel Lezcano wrote:
The real question is why
/* Set the clock scale and enable the event mode for CMP2 */
val = MFGPT_SCALE |
On Thu, 12 Oct 2017, David Kozub wrote:
> On Thu, 12 Oct 2017, Thomas Gleixner wrote:
> > On Thu, 12 Oct 2017, Daniel Lezcano wrote:
> > The real question is why
> >
> >/* Set the clock scale and enable the event mode for CMP2 */
> >val = MFGPT_SCALE | (3 << 8);
> >
> >
On Thu, 12 Oct 2017, David Kozub wrote:
> On Thu, 12 Oct 2017, Thomas Gleixner wrote:
> > On Thu, 12 Oct 2017, Daniel Lezcano wrote:
> > The real question is why
> >
> >/* Set the clock scale and enable the event mode for CMP2 */
> >val = MFGPT_SCALE | (3 << 8);
> >
> >
On Thu, 12 Oct 2017, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Daniel Lezcano wrote:
On 11/10/2017 22:48, David Kozub wrote:
[ ... ]
+ disable_timer(timer);
+ cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
+
/* Set up the IRQ on the MFGPT side */
if
On Thu, 12 Oct 2017, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Daniel Lezcano wrote:
On 11/10/2017 22:48, David Kozub wrote:
[ ... ]
+ disable_timer(timer);
+ cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
+
/* Set up the IRQ on the MFGPT side */
if
On Thu, 12 Oct 2017, Daniel Lezcano wrote:
> On 11/10/2017 22:48, David Kozub wrote:
>
> [ ... ]
>
> >>
> >> + disable_timer(timer);
> >> + cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
> >> +
> >> /* Set up the IRQ on the MFGPT side */
> >> if
On Thu, 12 Oct 2017, Daniel Lezcano wrote:
> On 11/10/2017 22:48, David Kozub wrote:
>
> [ ... ]
>
> >>
> >> + disable_timer(timer);
> >> + cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
> >> +
> >> /* Set up the IRQ on the MFGPT side */
> >> if
On 11/10/2017 22:48, David Kozub wrote:
[ ... ]
>>
>> + disable_timer(timer);
>> + cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
>> +
>> /* Set up the IRQ on the MFGPT side */
>> if (cs5535_mfgpt_setup_irq(timer, MFGPT_CMP2, _irq)) {
>> printk(KERN_ERR
On 11/10/2017 22:48, David Kozub wrote:
[ ... ]
>>
>> + disable_timer(timer);
>> + cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
>> +
>> /* Set up the IRQ on the MFGPT side */
>> if (cs5535_mfgpt_setup_irq(timer, MFGPT_CMP2, _irq)) {
>> printk(KERN_ERR
On Wed, 11 Oct 2017, Daniel Lezcano wrote:
On 10/10/2017 23:19, David Kozub wrote:
On Tue, 10 Oct 2017, Daniel Lezcano wrote:
On 09/10/2017 21:33, David Kozub wrote:
On Mon, 9 Oct 2017, Daniel Lezcano wrote:
On 07/10/2017 23:26, David Kozub wrote:
Hi all,
booting up kernel 4.14-rc3 with
On Wed, 11 Oct 2017, Daniel Lezcano wrote:
On 10/10/2017 23:19, David Kozub wrote:
On Tue, 10 Oct 2017, Daniel Lezcano wrote:
On 09/10/2017 21:33, David Kozub wrote:
On Mon, 9 Oct 2017, Daniel Lezcano wrote:
On 07/10/2017 23:26, David Kozub wrote:
Hi all,
booting up kernel 4.14-rc3 with
On 10/10/2017 23:19, David Kozub wrote:
> On Tue, 10 Oct 2017, Daniel Lezcano wrote:
>
>> On 09/10/2017 21:33, David Kozub wrote:
>>> On Mon, 9 Oct 2017, Daniel Lezcano wrote:
>>>
On 07/10/2017 23:26, David Kozub wrote:
> Hi all,
>
> booting up kernel 4.14-rc3 with
On 10/10/2017 23:19, David Kozub wrote:
> On Tue, 10 Oct 2017, Daniel Lezcano wrote:
>
>> On 09/10/2017 21:33, David Kozub wrote:
>>> On Mon, 9 Oct 2017, Daniel Lezcano wrote:
>>>
On 07/10/2017 23:26, David Kozub wrote:
> Hi all,
>
> booting up kernel 4.14-rc3 with
On Tue, 10 Oct 2017, Daniel Lezcano wrote:
On 09/10/2017 21:33, David Kozub wrote:
On Mon, 9 Oct 2017, Daniel Lezcano wrote:
On 07/10/2017 23:26, David Kozub wrote:
Hi all,
booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
(http://pcengines.ch/alix2c3.htm) dies with:
[
On Tue, 10 Oct 2017, Daniel Lezcano wrote:
On 09/10/2017 21:33, David Kozub wrote:
On Mon, 9 Oct 2017, Daniel Lezcano wrote:
On 07/10/2017 23:26, David Kozub wrote:
Hi all,
booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
(http://pcengines.ch/alix2c3.htm) dies with:
[
On 09/10/2017 21:33, David Kozub wrote:
> On Mon, 9 Oct 2017, Daniel Lezcano wrote:
>
>> On 07/10/2017 23:26, David Kozub wrote:
>>> Hi all,
>>>
>>> booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
>>> (http://pcengines.ch/alix2c3.htm) dies with:
>>>
>>> [ 2.313086]
On 09/10/2017 21:33, David Kozub wrote:
> On Mon, 9 Oct 2017, Daniel Lezcano wrote:
>
>> On 07/10/2017 23:26, David Kozub wrote:
>>> Hi all,
>>>
>>> booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
>>> (http://pcengines.ch/alix2c3.htm) dies with:
>>>
>>> [ 2.313086]
On Mon, 9 Oct 2017, Daniel Lezcano wrote:
On 07/10/2017 23:26, David Kozub wrote:
Hi all,
booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
(http://pcengines.ch/alix2c3.htm) dies with:
[ 2.313086] cs5535-smb cs5535-smb: SCx200 device 'CS5535 ACB0'
registered
[
On Mon, 9 Oct 2017, Daniel Lezcano wrote:
On 07/10/2017 23:26, David Kozub wrote:
Hi all,
booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
(http://pcengines.ch/alix2c3.htm) dies with:
[ 2.313086] cs5535-smb cs5535-smb: SCx200 device 'CS5535 ACB0'
registered
[
On 07/10/2017 23:26, David Kozub wrote:
> Hi all,
>
> booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
> (http://pcengines.ch/alix2c3.htm) dies with:
>
> [ 2.313086] cs5535-smb cs5535-smb: SCx200 device 'CS5535 ACB0'
> registered
> [ 2.338711] cs5535-mfgpt
On 07/10/2017 23:26, David Kozub wrote:
> Hi all,
>
> booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
> (http://pcengines.ch/alix2c3.htm) dies with:
>
> [ 2.313086] cs5535-smb cs5535-smb: SCx200 device 'CS5535 ACB0'
> registered
> [ 2.338711] cs5535-mfgpt
Hi all,
booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
(http://pcengines.ch/alix2c3.htm) dies with:
[2.313086] cs5535-smb cs5535-smb: SCx200 device 'CS5535 ACB0' registered
[2.338711] cs5535-mfgpt cs5535-mfgpt: registered timer 0
[2.355676] ledtrig-cpu:
Hi all,
booting up kernel 4.14-rc3 with CS5535_CLOCK_EVENT_SRC on an ALIX 2c3
(http://pcengines.ch/alix2c3.htm) dies with:
[2.313086] cs5535-smb cs5535-smb: SCx200 device 'CS5535 ACB0' registered
[2.338711] cs5535-mfgpt cs5535-mfgpt: registered timer 0
[2.355676] ledtrig-cpu:
26 matches
Mail list logo