From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-pcmcia@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] [POWERPC] 8xx: mpc885ads pcmcia support
Date: Wed, 9 May 2007 01:19:16 +0400 [thread overview]
Message-ID: <20070509011916.60853128@localhost.localdomain> (raw)
In-Reply-To: <774F0168-051E-4C6B-9292-8EE731E6D889@kernel.crashing.org>
On Tue, 8 May 2007 09:04:22 -0500
Kumar Gala wrote:
> > + device_type = "pcmcia";
> > + reg = <80 80>;
> > + clock-frequency = <2faf080>;
>
> is the clock-freq fixed?
As I see now, that field is not really required as never extracted or used. The intention was to
use dts value iirc, later it was switched to ppc_proc_freq, but never removed from dts.
Hence I'll do that now.
--
Sincerely, Vitaly
WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linux-pcmcia@lists.infradead.org, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] [POWERPC] 8xx: mpc885ads pcmcia support
Date: Wed, 9 May 2007 01:19:16 +0400 [thread overview]
Message-ID: <20070509011916.60853128@localhost.localdomain> (raw)
In-Reply-To: <774F0168-051E-4C6B-9292-8EE731E6D889@kernel.crashing.org>
On Tue, 8 May 2007 09:04:22 -0500
Kumar Gala wrote:
> > + device_type = "pcmcia";
> > + reg = <80 80>;
> > + clock-frequency = <2faf080>;
>
> is the clock-freq fixed?
As I see now, that field is not really required as never extracted or used. The intention was to
use dts value iirc, later it was switched to ppc_proc_freq, but never removed from dts.
Hence I'll do that now.
--
Sincerely, Vitaly
next prev parent reply other threads:[~2007-05-08 21:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 9:50 [PATCH 0/3] 8xx PCMCIA stuff && cleanup: take 3 Vitaly Bordug
2007-05-08 9:50 ` Vitaly Bordug
2007-05-08 9:50 ` [PATCH 1/3] [POWERPC] 8xx: mpc885ads pcmcia support Vitaly Bordug
2007-05-08 9:50 ` Vitaly Bordug
2007-05-08 14:04 ` Kumar Gala
2007-05-08 14:04 ` Kumar Gala
2007-05-08 17:31 ` Vitaly Bordug
2007-05-08 17:31 ` Vitaly Bordug
2007-05-08 21:19 ` Vitaly Bordug [this message]
2007-05-08 21:19 ` Vitaly Bordug
2007-05-08 9:50 ` [PATCH 2/3] [POWERPC] 8xx: fix whitespace and indentation Vitaly Bordug
2007-05-08 9:50 ` Vitaly Bordug
2007-05-08 9:50 ` [PATCH 3/3] [POWERPC] dts: kill hardcoded phandles Vitaly Bordug
2007-05-08 9:50 ` Vitaly Bordug
-- strict thread matches above, loose matches on Subject: below --
2007-05-08 22:31 [PATCH 0/3] 8xx PCMCIA stuff && cleanup: take 4 Vitaly Bordug
2007-05-08 22:31 ` [PATCH 1/3] [POWERPC] 8xx: mpc885ads pcmcia support Vitaly Bordug
2007-05-08 22:31 ` Vitaly Bordug
2007-05-14 21:21 ` Andrew Morton
2007-05-14 21:21 ` Andrew Morton
[not found] <20070508053049.18428.50622.stgit@localhost.localdomain>
2007-05-08 5:48 ` Vitaly Bordug
2007-05-08 5:48 ` Vitaly Bordug
2007-05-08 6:02 ` Olof Johansson
2007-05-08 6:02 ` Olof Johansson
2007-05-08 0:36 Vitaly Bordug
2007-05-08 5:58 ` Olof Johansson
2007-05-08 5:58 ` Olof Johansson
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=20070509011916.60853128@localhost.localdomain \
--to=vitb@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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.