Hi Joakim,
On Sat, 18 Nov 2006 15:51:09 +0100, Joakim Tjernlund wrote:
> > It's OK to schedule or sleep in mpc_xfer. It's not OK to call mpc_xfer
> > from an interrupt context, which is what appears to be happening here.
> > So the ds1307 driver would need to be changed not to directly call
> > i2
> > Of course you can't do that. You're calling rtc_set_time(), which
> > requires a task/sleeping context, from an atomic can't-sleep context
> > (timer irq handler in this case).
> >
> > Whatever your rtc_class_hookup() is doing, it's clearly wrong.
>
> It isn't my rtc_class_hookup(), it is in
>
> On Fri, 17 Nov 2006 18:38:10 +0100, Joakim Tjernlund wrote:
> > On Nov 17, 2006, at 10:38 AM, Joakim Tjernlund wrote:
> >
> > > I get this when I activathte NTP and ntp "sync" the time
> the I2C HW
> > > clock.
> >
> > You may be better off posting this to lkml and copy the i2c
> list (a
On Fri, 17 Nov 2006 18:38:10 +0100, Joakim Tjernlund wrote:
> On Nov 17, 2006, at 10:38 AM, Joakim Tjernlund wrote:
>
> > I get this when I activathte NTP and ntp "sync" the time the I2C HW
> > clock.
>
> You may be better off posting this to lkml and copy the i2c list (and
> rtc if one exist
> -Original Message-
> From:
> Sent: 17 November 2006 17:57
> To: Joakim Tjernlund
> Cc: [EMAIL PROTECTED]
> Subject: Re: RTC , ds1307 I2C driver and NTP does not work.
>
>
> On Nov 17, 2006, at 10:38 AM, Joakim Tjernlund wrote:
>
>> I get this when
switching to kernel/i2c list, see below for details.
Jocke
-Original Message-
From: Kumar Gala [mailto:[EMAIL PROTECTED]
Sent: 17 November 2006 17:57
To: Joakim Tjernlund
Cc: [EMAIL PROTECTED]
Subject: Re: RTC , ds1307 I2C driver and NTP does not work.
On Nov 17, 2006, at 10:38 AM
6 matches
Mail list logo