Yes please. thanks.
Acked-by: Alessandro Zummo
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
ING
> + "mpc5121-rtc: Battery or oscillator failure!\n");
> + out_be32(&rtc->regs->keep_alive, ka);
> + }
> +
> + goto out;
> +
> +out_dispose2:
> + irq_dispose_mapping(rtc->irq_periodic);
> + free_irq(rtc->ir
On Fri, 8 May 2009 09:53:20 -0600
Grant Likely wrote:
> That is fine by me, but since it is known that it will eventually
> support both, I'd like it to be renamed to 5xxx before it is merged to
> avoid a later rename patch.
or 52xx ?
--
Best regards,
Alessandro
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
code
> to separate RTC drivers.
>
> (Alessandro, please correct me if I'm wrong)
yes, that's my dream :)
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing
On Mon, 9 Mar 2009 11:04:17 -0700
Geoff Levand wrote:
>
> Hi,
>
> On 03/09/2009 07:12 AM, Alessandro Zummo wrote:
> > On Mon, 9 Mar 2009 14:26:23 +0100
> > Geert Uytterhoeven wrote:
> >> +
> >> +MODULE_AUTHOR("Sony Corporation");
&g
t; he already has the preceding patches? Can I have your acks, please?
Here's mine. Thanks for your efforts .
Acked-by: Alessandro Zummo
btw I'll pretend I had never seen this patch
if asked in court :)
--
Best regards,
Alessandro
n -= 1;
> + return 0;
> +}
this should be return rtc_valid_tm() .
can't you use functions from rtc-lib.c instead of
that to_tm ?
> +
> +MODULE_AUTHOR("Sony Corporation");
real name, if possible and a contact address
here . Just in case I need someone t
everyone is lazy :)
Seriously, if you want to handle it in the way we wrote
in the previous emails, it's ok for me.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing l
of rtc-generic and information
about their respective rtc hardware along with some general planning about
which future driver would cover which users.
And let's hope this is a beginning :)
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertec
is quite a nonsense .
>
> IMHO these two generic frameworks are quite different: [sg]et_rtc_time()
> abstracts the low-level RTC hardware interface, while RTC class handles the
> interaction with userspace.
When I wrote it my intention was to make it as an abstraction _between_
f them will have its code scattered all around the kernel.
So you either use the old rtc framework, which is perfectly functional,
or you move to the new rtc lass and write the drivers.
Layering a generic framework over another generic framework
is quite a nonsense .
--
Best regards,
Aless
kernel.
they were almost ok but there are still a few things that I
need to check before incorporating them.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
e to the hardware
rtc every 11 minutes as it used to do. normal NTP operations are unaffected.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
http
h/ into seperate drivers under drivers/rtc/ instead?
>
> That's the ideal... although did we get NTP sync working again yet?
not yet. we're close but I've been very busy :(
--
Best regards,
Alessandro Zummo,
Tower Tech
c and m68k RTC support code into individual RTC
> class drivers would add ca. 100+ lines of code for each individual driver.
How different are all of those boards? It's simply a matter
of parameters and offsets? can we group them somehow?
--
Best regards,
Alessandro Zummo,
in asm-generic ;-)
yep, I know :( that hardcoded rtc stuff seems to be everywhere!
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
e assumption that a device has
a fixed major:minor number should be dropped as well.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
RTC devices would use, but they'd have the
> option to use their own instead.
I'll give it a look.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Adds in-kernel hctosys functionality that can
be used by ntp sync code.
This is an RFC and has not been tested, I just want
to check if something similar could solve the problems
of those who want the NTP sync mode.
Signed-off-by: Alessandro Zummo <[EMAIL PROTECTED]>
Cc: Paul Mundt &
ince that's what actually *stores* the time during
> power off cycles.
well, let's start with one... we all lived with one rtc until
a couple of year ago :)
> > +static int rtc_systohc(struct rtc_time *tm)
>
> I think "static" will lose, especially since ...
ivers as an interim measure, but the hooks are called from
> places the rtc class stuff can't safely be called (too early, IIRC,
> but it's a while since I checked).
I think the rtc drivers are too heterogeneous to have a valid
ntp strategy.
--
Best regards,
Alessandro Zum
al fine :)
> I think we're waiting until the RTC class works with NTP before we can
> contemplate that, though.
That will be a long wait, I don't think anyone volunteered for
the ntp code. I've been told some platforms are already using the class.
--
Best regards,
Al
On Wed, 4 Jun 2008 08:40:46 -0500
Kumar Gala <[EMAIL PROTECTED]> wrote:
> > Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
> > Signed-off-by: Alessandro Zummo <[EMAIL PROTECTED]>
>
> Acked-by: Kumar Gala <[EMAIL PROTECTED]>
>
> Is this for 2.6.26
oved 3 months ago.
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
Signed-off-by: Alessandro Zummo <[EMAIL PROTECTED]>
---
Patch already sent on:
* 2008-04-30
arch/powerpc/sysdev/fsl_soc.c |2 +-
drivers/of/of_i2c.c |1 -
drivers/rtc/rtc-ds1374.c |2 +
ing 254,0. I would eventually ack a patch that adds
/dev/rtc at 10,135 as an alias for /dev/rtc0.
however the best solution would be to upgrade hwclock.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
only real open issue is related to the ntp synchronization
mode and will be solved only when we can get rid of it :)
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
___
Linuxppc-dev mailing list
Linuxppc
]>
> > ---
> >
> > drivers/rtc/rtc-pcf8563.c | 107
> > +++--
> > 1 files changed, 27 insertions(+), 80 deletions(-)
>
> Preliminary note: this driver belongs to the RTC subsystem, so it will
> be up to Alessandro Z
28 matches
Mail list logo
