[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140628205433.0ef4a8cf28a7fe4861a733dd@gmx.de>
Date: Sat, 28 Jun 2014 20:54:33 +0200
From: Marc Dietrich <marvin24@....de>
To: Alexander Holler <holler@...oftware.de>
Cc: John Stultz <john.stultz@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
John Whitmore <arigead@...il.com>,
Alessandro Zummo <a.zummo@...ertech.it>
Subject: Re: [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules
On Sat, 28 Jun 2014 09:32:50 +0200
Alexander Holler <holler@...oftware.de> wrote:
> Am 28.06.2014 09:18, schrieb Alexander Holler:
> > Am 27.06.2014 19:27, schrieb John Stultz:
> >> Its been pointed out that the RTC hctosys functionality doesn't
> >> work well with RTC modules, which may not be loaded until after
> >> late_init().
> >>
> >> While there have been other attempts to sovle this, this patchset
> >> is a very quick 10 minute effort to show how I'd try to resolve
> >> this. There likely are still issues here, but I'd be happy to
> >> make fixes and adjustments to ensure it works.
>
> How long you needed to getthe idea?
>
> >>
> >> Feedback and comments always appreciated!
> >
> > And it still uses the non-deterministic and therefor almost unusable
> > rtcN. Well done.
>
> Besides that the current hctosys-mechanism doesn't really work with
> hot-plugable devices at all. Guess what N will be when you unplug and
> plug in such a RTC again.
We have a patch in the kernel which binds the rtc number to the
hw device, so this even works for hotpluggable devices (at least on
systems supporting device-tree). Not sure what your needs are.
Marc
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists