All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Felipe Balbi <balbi@ti.com>,
	mturquette@linaro.org,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	james.hogan@imgtec.com, luca@coelho.fi
Subject: Re: [PATCH] clk: add flags to distinguish xtal clocks
Date: Mon, 11 Nov 2013 13:43:55 -0600	[thread overview]
Message-ID: <20131111194355.GC19212@saruman.home> (raw)
In-Reply-To: <5281058E.5050607@wwwdotorg.org>

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

Hi,

On Mon, Nov 11, 2013 at 09:27:58AM -0700, Stephen Warren wrote:
> On 11/08/2013 11:00 AM, Felipe Balbi wrote:
> > From: Luciano Coelho <luca@coelho.fi>
> > 
> > Add a flag that indicate whether the clock is a crystal or not.
> > 
> > Additionally, parse a new device tree binding in clk-fixed-rate to set
> > this flag.
> > 
> > If clock-xtal isn't set, the clock framework will assume clock to be
> > generated by an oscillator.  There's only one user for this binding
> > right now which is Texas Instruments' WiLink devices which need to know
> > details about the clock in order to initialize the underlying WiFi HW
> > correctly.
> 
> Why on earth does it care? Surely the WiFi HW doesn't care about
> crystal-vs-non-crystal, but rather some facet of the clock signal that
> the type of source implies. Shouldn't the DT property describe that
> facet of the signal, rather than the reason why it has that facet?

well, if you can figure out what that facet is, then _do_ tell. Luca has
tried for months to get that information with no success.

-- 
balbi

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

WARNING: multiple messages have this Message-ID (diff)
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: add flags to distinguish xtal clocks
Date: Mon, 11 Nov 2013 13:43:55 -0600	[thread overview]
Message-ID: <20131111194355.GC19212@saruman.home> (raw)
In-Reply-To: <5281058E.5050607@wwwdotorg.org>

Hi,

On Mon, Nov 11, 2013 at 09:27:58AM -0700, Stephen Warren wrote:
> On 11/08/2013 11:00 AM, Felipe Balbi wrote:
> > From: Luciano Coelho <luca@coelho.fi>
> > 
> > Add a flag that indicate whether the clock is a crystal or not.
> > 
> > Additionally, parse a new device tree binding in clk-fixed-rate to set
> > this flag.
> > 
> > If clock-xtal isn't set, the clock framework will assume clock to be
> > generated by an oscillator.  There's only one user for this binding
> > right now which is Texas Instruments' WiLink devices which need to know
> > details about the clock in order to initialize the underlying WiFi HW
> > correctly.
> 
> Why on earth does it care? Surely the WiFi HW doesn't care about
> crystal-vs-non-crystal, but rather some facet of the clock signal that
> the type of source implies. Shouldn't the DT property describe that
> facet of the signal, rather than the reason why it has that facet?

well, if you can figure out what that facet is, then _do_ tell. Luca has
tried for months to get that information with no success.

-- 
balbi
-------------- 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/20131111/b9e5646b/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@ti.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Felipe Balbi <balbi@ti.com>, <mturquette@linaro.org>,
	Linux ARM Kernel Mailing List 
	<linux-arm-kernel@lists.infradead.org>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<james.hogan@imgtec.com>, <luca@coelho.fi>
Subject: Re: [PATCH] clk: add flags to distinguish xtal clocks
Date: Mon, 11 Nov 2013 13:43:55 -0600	[thread overview]
Message-ID: <20131111194355.GC19212@saruman.home> (raw)
In-Reply-To: <5281058E.5050607@wwwdotorg.org>

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

Hi,

On Mon, Nov 11, 2013 at 09:27:58AM -0700, Stephen Warren wrote:
> On 11/08/2013 11:00 AM, Felipe Balbi wrote:
> > From: Luciano Coelho <luca@coelho.fi>
> > 
> > Add a flag that indicate whether the clock is a crystal or not.
> > 
> > Additionally, parse a new device tree binding in clk-fixed-rate to set
> > this flag.
> > 
> > If clock-xtal isn't set, the clock framework will assume clock to be
> > generated by an oscillator.  There's only one user for this binding
> > right now which is Texas Instruments' WiLink devices which need to know
> > details about the clock in order to initialize the underlying WiFi HW
> > correctly.
> 
> Why on earth does it care? Surely the WiFi HW doesn't care about
> crystal-vs-non-crystal, but rather some facet of the clock signal that
> the type of source implies. Shouldn't the DT property describe that
> facet of the signal, rather than the reason why it has that facet?

well, if you can figure out what that facet is, then _do_ tell. Luca has
tried for months to get that information with no success.

-- 
balbi

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

  reply	other threads:[~2013-11-11 19:44 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
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 [this message]
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=20131111194355.GC19212@saruman.home \
    --to=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 \
    --cc=swarren@wwwdotorg.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.