All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
	Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
	Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>,
	Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
	ARM kernel mailing list
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	Peter De Schrijver
	<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: Tegra board file deprecation schedule
Date: Sun, 29 Apr 2012 13:25:05 -0600	[thread overview]
Message-ID: <4F9D9591.60407@wwwdotorg.org> (raw)
In-Reply-To: <1335648381.13148.4.camel@antimon>

On 04/28/2012 03:26 PM, Lucas Stach wrote:
> Am Freitag, den 27.04.2012, 15:24 -0600 schrieb Stephen Warren:
>> Eventually, Tegra support will become device tree only in the mainline
>> kernel; arch/arm/mach-tegra/board* will be deleted.
>>
>> I propose the following policy towards this goal: I'd like to maintain
>> the board files until the relevant device tree file has the same level
>> of functionality. Once that is achieved, and a Linus kernel is release
>> with full support for the board via device tree, the board files can be
>> deleted from the next kernel release.
>>
>> Does anyone have any issues with this?
> 
> Do we have any way to describe the clocks in the device tree?

Not at present, although supporting that will probably be part of
Tegra's support of the common clock API and DT bindings.

> I'm
> planning to add support for the Toradex Colibri T20 processor module,
> which uses a 13MHz external OSC, so the generic clock init in the
> current dt code definitely won't work for this board.

I'm not actually sure that's true. I believe we measure the OSC
frequency during boot, and all the clock driver PLL tables have (or
should have) entries for the various supported crystal frequencies. I
wouldn't be too surprised if it all just worked, or could easily be
fixed to.

(I wouldn't consider this to be related to board file deprecation, since
there are currently no board files to be deprecated that rely on such a
feature anyway)

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra board file deprecation schedule
Date: Sun, 29 Apr 2012 13:25:05 -0600	[thread overview]
Message-ID: <4F9D9591.60407@wwwdotorg.org> (raw)
In-Reply-To: <1335648381.13148.4.camel@antimon>

On 04/28/2012 03:26 PM, Lucas Stach wrote:
> Am Freitag, den 27.04.2012, 15:24 -0600 schrieb Stephen Warren:
>> Eventually, Tegra support will become device tree only in the mainline
>> kernel; arch/arm/mach-tegra/board* will be deleted.
>>
>> I propose the following policy towards this goal: I'd like to maintain
>> the board files until the relevant device tree file has the same level
>> of functionality. Once that is achieved, and a Linus kernel is release
>> with full support for the board via device tree, the board files can be
>> deleted from the next kernel release.
>>
>> Does anyone have any issues with this?
> 
> Do we have any way to describe the clocks in the device tree?

Not at present, although supporting that will probably be part of
Tegra's support of the common clock API and DT bindings.

> I'm
> planning to add support for the Toradex Colibri T20 processor module,
> which uses a 13MHz external OSC, so the generic clock init in the
> current dt code definitely won't work for this board.

I'm not actually sure that's true. I believe we measure the OSC
frequency during boot, and all the clock driver PLL tables have (or
should have) entries for the various supported crystal frequencies. I
wouldn't be too surprised if it all just worked, or could easily be
fixed to.

(I wouldn't consider this to be related to board file deprecation, since
there are currently no board files to be deprecated that rely on such a
feature anyway)

  reply	other threads:[~2012-04-29 19:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 21:24 Tegra board file deprecation schedule Stephen Warren
2012-04-27 21:24 ` Stephen Warren
     [not found] ` <4F9B0E7C.1060408-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-27 21:39   ` Olof Johansson
2012-04-27 21:39     ` Olof Johansson
     [not found]     ` <CAOesGMh3NY4cQERSQY-p0QsMtcCXyhkdGSGnnrckcz8-DPjbBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-27 21:53       ` Stephen Warren
2012-04-27 21:53         ` Stephen Warren
     [not found]         ` <4F9B1568.9070704-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-27 22:00           ` Fabio Estevam
2012-04-27 22:00             ` Fabio Estevam
     [not found]             ` <CAOMZO5Cnd9knDUuc4aZrPrtk5YKUwpr-oJhUnu=z94=9CfY1ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-27 22:20               ` Stephen Warren
2012-04-27 22:20                 ` Stephen Warren
2012-04-28 16:09       ` Marc Dietrich
2012-04-28 16:09         ` Marc Dietrich
2012-04-28 21:34         ` Russell King - ARM Linux
2012-04-28 21:34           ` Russell King - ARM Linux
     [not found]           ` <20120428213456.GD27792-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-04-29 18:11             ` Marc Dietrich
2012-04-29 18:11               ` Marc Dietrich
2012-04-29 18:56               ` Russell King - ARM Linux
2012-04-29 18:56                 ` Russell King - ARM Linux
2012-04-29 19:16               ` Stephen Warren
2012-04-29 19:16                 ` Stephen Warren
     [not found]                 ` <4F9D9396.9070009-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-30  8:58                   ` Marc Dietrich
2012-04-30  8:58                     ` Marc Dietrich
2012-04-30 15:58                     ` Stephen Warren
2012-04-30 15:58                       ` Stephen Warren
     [not found]                       ` <4F9EB68A.3080309-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-30 16:51                         ` Marc Dietrich
2012-04-30 16:51                           ` Marc Dietrich
2012-04-29 19:21         ` Stephen Warren
2012-04-29 19:21           ` Stephen Warren
     [not found]           ` <4F9D94B3.4070903-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-30  9:00             ` Marc Dietrich
2012-04-30  9:00               ` Marc Dietrich
2012-04-28 21:26   ` Lucas Stach
2012-04-28 21:26     ` Lucas Stach
2012-04-29 19:25     ` Stephen Warren [this message]
2012-04-29 19:25       ` Stephen Warren

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=4F9D9591.60407@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
    --cc=dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marvin24-Mmb7MZpHnFY@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
    --cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.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.