All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Luca Coelho <luca@coelho.fi>
Cc: balbi@ti.com, mturquette@linaro.org, james.hogan@imgtec.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: add flags to distinguish xtal clocks
Date: Wed, 13 Nov 2013 15:40:10 +0100	[thread overview]
Message-ID: <20131113144010.GB3538@lukather> (raw)
In-Reply-To: <1384243549.12583.36.camel@porter.coelho.fi>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

On Tue, Nov 12, 2013 at 10:05:49AM +0200, Luca Coelho wrote:
> > What I'm not really convinced about is *how* you carry that metadata
> > in the DT, that's all, nothing more.
> 
> Okay, I get you.  My point is that being a crystal or not *is* a
> characteristic of the clock, so I think it could be part of the flags
> that describe it.

Yeah, but then, a crystal has a slightly different behaviour and
property than a oscillator, therefore the two aren't fully
"compatible" with each other.

> In any case, it's not really my call.  This is about the clock and it's
> not even my home turf (wireless). ;)
> 
> Thanks for your comments.  And I'm sorry if the tone of my previous
> email sounded harsh, it was not supposed to. :)

That's fine, don't worry :)

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: add flags to distinguish xtal clocks
Date: Wed, 13 Nov 2013 15:40:10 +0100	[thread overview]
Message-ID: <20131113144010.GB3538@lukather> (raw)
In-Reply-To: <1384243549.12583.36.camel@porter.coelho.fi>

On Tue, Nov 12, 2013 at 10:05:49AM +0200, Luca Coelho wrote:
> > What I'm not really convinced about is *how* you carry that metadata
> > in the DT, that's all, nothing more.
> 
> Okay, I get you.  My point is that being a crystal or not *is* a
> characteristic of the clock, so I think it could be part of the flags
> that describe it.

Yeah, but then, a crystal has a slightly different behaviour and
property than a oscillator, therefore the two aren't fully
"compatible" with each other.

> In any case, it's not really my call.  This is about the clock and it's
> not even my home turf (wireless). ;)
> 
> Thanks for your comments.  And I'm sorry if the tone of my previous
> email sounded harsh, it was not supposed to. :)

That's fine, don't worry :)

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131113/1233f854/attachment.sig>

  reply	other threads:[~2013-11-13 14:45 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 21:05 [RFC] clk: add flags to distinguish xtal clocks Luciano Coelho
2013-07-04 21:05 ` Luciano Coelho
2013-07-04 22:25 ` Mike Turquette
2013-07-04 22:37   ` Luciano Coelho
2013-07-04 22:37     ` Luciano Coelho
2013-07-04 23:19     ` Mike Turquette
2013-07-05  7:54       ` Luciano Coelho
2013-07-05  7:54         ` Luciano Coelho
2013-07-29 13:50         ` Luciano Coelho
2013-07-29 13:50           ` Luciano Coelho
2013-10-07  7:44           ` Mike Turquette
2013-10-08 15:27             ` Felipe Balbi
2013-10-08 15:27               ` Felipe Balbi
2013-10-16 10:24               ` Luca Coelho
2013-10-16 10:24                 ` Luca Coelho
2013-10-23  9:24                 ` Mike Turquette
2013-10-23  9:24                   ` Mike Turquette
2013-10-23 11:35                   ` Luca Coelho
2013-10-23 11:35                     ` Luca Coelho
2013-11-08 18:00                     ` [PATCH] " Felipe Balbi
2013-11-08 18:00                       ` Felipe Balbi
2013-11-08 18:00                       ` Felipe Balbi
2013-11-08 19:16                       ` Luca Coelho
2013-11-08 19:16                         ` Luca Coelho
2013-11-10 11:37                       ` Maxime Ripard
2013-11-10 11:37                         ` Maxime Ripard
2013-11-11 19:42                         ` Felipe Balbi
2013-11-11 19:42                           ` Felipe Balbi
2013-11-11 19:42                           ` Felipe Balbi
2013-11-11 19:50                           ` Luca Coelho
2013-11-11 19:50                             ` Luca Coelho
2013-11-11 20:59                             ` Maxime Ripard
2013-11-11 20:59                               ` Maxime Ripard
2013-11-12  8:05                               ` Luca Coelho
2013-11-12  8:05                                 ` Luca Coelho
2013-11-13 14:40                                 ` Maxime Ripard [this message]
2013-11-13 14:40                                   ` Maxime Ripard
2013-11-11 20:54                           ` Maxime Ripard
2013-11-11 20:54                             ` Maxime Ripard
2013-11-11 16:27                       ` Stephen Warren
2013-11-11 16:27                         ` Stephen Warren
2013-11-11 19:43                         ` Felipe Balbi
2013-11-11 19:43                           ` Felipe Balbi
2013-11-11 19:43                           ` Felipe Balbi
2013-07-05 13:12 ` [RFC] " James Hogan
2013-07-05 13:12   ` James Hogan
2013-07-05 13:21   ` Felipe Balbi
2013-07-05 13:21     ` Felipe Balbi
2013-07-05 13:22   ` Luciano Coelho
2013-07-05 13:22     ` Luciano Coelho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131113144010.GB3538@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=balbi@ti.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=luca@coelho.fi \
    --cc=mturquette@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.