On Wed, Mar 25, 2015 at 04:39:08PM -0700, Chen-Yu Tsai wrote:
> Hi Maxime,
>
> On Thu, Mar 19, 2015 at 2:18 AM, maxime.ripard
> wrote:
> > Hi Kevin,
> >
> > On Thu, Mar 19, 2015 at 12:05:06PM +0800, kevin.z.m...@gmail.com wrote:
> >> >> One questi
On Wed, Mar 25, 2015 at 04:39:08PM -0700, Chen-Yu Tsai wrote:
Hi Maxime,
On Thu, Mar 19, 2015 at 2:18 AM, maxime.ripard
maxime.rip...@free-electrons.com wrote:
Hi Kevin,
On Thu, Mar 19, 2015 at 12:05:06PM +0800, kevin.z.m...@gmail.com wrote:
One question I couldn't find any answer
Hi Kevin,
On Thu, Mar 19, 2015 at 12:05:06PM +0800, kevin.z.m...@gmail.com wrote:
> >> One question I couldn't find any answer to is that does the SMP bit is
> >> set in secondary_startup?
> >>
> >> I couldn't find where it was set, but it still looks like the right
> >> thing to do, so I would
Hi Kevin,
On Thu, Mar 19, 2015 at 12:05:06PM +0800, kevin.z.m...@gmail.com wrote:
One question I couldn't find any answer to is that does the SMP bit is
set in secondary_startup?
I couldn't find where it was set, but it still looks like the right
thing to do, so I would expect the code
On Fri, Jun 20, 2014 at 02:13:58PM +0800, Chen-Yu Tsai wrote:
> > If these two clocks are these different though, maybe it would just be
> > easier to add a new driver. These are trivial enough anyway.
>
> Yes it is. But it adds more of the same boilerplate code than actual
> differences of the
On Fri, Jun 20, 2014 at 02:13:58PM +0800, Chen-Yu Tsai wrote:
If these two clocks are these different though, maybe it would just be
easier to add a new driver. These are trivial enough anyway.
Yes it is. But it adds more of the same boilerplate code than actual
differences of the
On Thu, Apr 17, 2014 at 09:43:40AM +0200, Arend van Spriel wrote:
> + linux-ser...@vger.kernel.org
>
> On 16/04/14 15:09, Hans de Goede wrote:
> >Hi,
> >
> >On 04/16/2014 12:39 PM, Chen-Yu Tsai wrote:
> >>Hi,
> >>
> >>On Wed, Apr 16, 2014 at 5:44 PM, Maxime Ripard
> >> wrote:
> >>>Hi,
> >>>
>
On Wed, Apr 16, 2014 at 06:39:28PM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> On Wed, Apr 16, 2014 at 5:44 PM, Maxime Ripard
> wrote:
> > Hi,
> >
> > Please try to keep me in CC, even though the ML doesn't make it easy..
>
> Sorry about that.
>
> > On Wed, Apr 16, 2014 at 12:06:59AM +0800, Chen-Yu
On Wed, Apr 16, 2014 at 06:39:28PM +0800, Chen-Yu Tsai wrote:
Hi,
On Wed, Apr 16, 2014 at 5:44 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Hi,
Please try to keep me in CC, even though the ML doesn't make it easy..
Sorry about that.
On Wed, Apr 16, 2014 at 12:06:59AM
On Thu, Apr 17, 2014 at 09:43:40AM +0200, Arend van Spriel wrote:
+ linux-ser...@vger.kernel.org
On 16/04/14 15:09, Hans de Goede wrote:
Hi,
On 04/16/2014 12:39 PM, Chen-Yu Tsai wrote:
Hi,
On Wed, Apr 16, 2014 at 5:44 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Hi,
On Mon, Dec 09, 2013 at 10:59:38AM +0800, Chen-Yu Tsai wrote:
> On Sat, Dec 7, 2013 at 7:06 PM, Tomasz Figa wrote:
> > On Saturday 07 of December 2013 11:07:37 maxime.ripard wrote:
> >> On Sat, Dec 07, 2013 at 09:23:27AM +0800, Chen-Yu Tsai wrote:
> >> > Point tak
On Mon, Dec 09, 2013 at 10:59:38AM +0800, Chen-Yu Tsai wrote:
On Sat, Dec 7, 2013 at 7:06 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
On Saturday 07 of December 2013 11:07:37 maxime.ripard wrote:
On Sat, Dec 07, 2013 at 09:23:27AM +0800, Chen-Yu Tsai wrote:
Point taken. The current
On Sat, Dec 07, 2013 at 09:23:27AM +0800, Chen-Yu Tsai wrote:
> Point taken. The current implementation will override settings passed from
> platform data. ORing the two would be better.
Platform_data and DT-based configuration are pretty unlikely to be
used together, so ORing it doesn't have
On Sat, Dec 07, 2013 at 09:23:27AM +0800, Chen-Yu Tsai wrote:
Point taken. The current implementation will override settings passed from
platform data. ORing the two would be better.
Platform_data and DT-based configuration are pretty unlikely to be
used together, so ORing it doesn't have much
Hi Kevin,
On Thu, Aug 01, 2013 at 08:34:35AM +0800, kevin.z.m wrote:
> > Ok, just so that we're on the same page, we have two oscillators running
> > at 32kHz, the internal being always there, and the external that could
> > or could not be there, and it's each different hardware block that can
>
Hi Kevin,
On Thu, Aug 01, 2013 at 08:34:35AM +0800, kevin.z.m wrote:
Ok, just so that we're on the same page, we have two oscillators running
at 32kHz, the internal being always there, and the external that could
or could not be there, and it's each different hardware block that can
be
On Wed, Jul 31, 2013 at 08:10:32PM +0800, kevin.z.m wrote:
> > How does one select either the internal or the external 32kHz
> > oscillator? Is this done in software (I can't find any reference to that
> > in the user manuals) or in hardware?
> For A20, it should be in the Timer module, and
Hi Kevin,
On Wed, Jul 31, 2013 at 04:11:11PM +0800, kevin.z.m wrote:
> Hi, Maxime,
>
> > The problem is a bit more complex than that.
>
> > On the A31, the losc clock is actually a mux between an external
> > oscillator running at 32kHz, and the internal oscillator running at
> > 667MHz, that
Hi Kevin,
On Wed, Jul 31, 2013 at 04:11:11PM +0800, kevin.z.m wrote:
Hi, Maxime,
The problem is a bit more complex than that.
On the A31, the losc clock is actually a mux between an external
oscillator running at 32kHz, and the internal oscillator running at
667MHz, that would be
On Wed, Jul 31, 2013 at 08:10:32PM +0800, kevin.z.m wrote:
How does one select either the internal or the external 32kHz
oscillator? Is this done in software (I can't find any reference to that
in the user manuals) or in hardware?
For A20, it should be in the Timer module, and there is a
Hi Thomas,
On Fri, Jun 28, 2013 at 04:02:23PM +0200, Thomas Gleixner wrote:
> On Fri, 28 Jun 2013, 张猛 wrote:
> > > The A10 manual from http://free-electrons.com/~maxime/pub/datasheet/
> > > does not seem to contain any details about what bad things may happen
> > > if we try to read CNT64_LO_REG
On Fri, Jun 28, 2013 at 01:29:12PM +0300, Siarhei Siamashka wrote:
> > NOTICE: This e-mail and any included attachments are intended only
> > for the sole use of named and intended recipient (s) only. If you
> > are the named and intended recipient, please note that the
> > information contained
On Fri, Jun 28, 2013 at 01:29:12PM +0300, Siarhei Siamashka wrote:
NOTICE: This e-mail and any included attachments are intended only
for the sole use of named and intended recipient (s) only. If you
are the named and intended recipient, please note that the
information contained in this
Hi Thomas,
On Fri, Jun 28, 2013 at 04:02:23PM +0200, Thomas Gleixner wrote:
On Fri, 28 Jun 2013, 张猛 wrote:
The A10 manual from http://free-electrons.com/~maxime/pub/datasheet/
does not seem to contain any details about what bad things may happen
if we try to read CNT64_LO_REG while
24 matches
Mail list logo
