From: Andreas Barth <aba@not.so.argh.org>
To: Kelvin Cheung <keguang.zhang@gmail.com>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
ralf@linux-mips.org, wuzhangjin@gmail.com, r0bertz@gentoo.org,
chenj@lemote.com
Subject: Re: [PATCH] MIPS: Add basic support for Loongson1B
Date: Thu, 15 Sep 2011 09:07:53 +0200 [thread overview]
Message-ID: <20110915070752.GU15003@mails.so.argh.org> (raw)
In-Reply-To: <CAJhJPsUXvGJBB-YiLB53VSf8GRXHjkrPRf3F3YE5ekOz-OVqgQ@mail.gmail.com>
* Kelvin Cheung (keguang.zhang@gmail.com) [110915 05:28]:
> >> > Doesn't any of the existing clock drivers work?
> >> >
> >> > Is this clock part of the CPU? Otherwise it would make sense to move
> >> > it out to the generic drivers section.
> >
> > What's the answer to this questions?
>
> I just did what other platform did, such as ar7, ath79, bcm63xx and
> jz4740. Could you have a look at their clock.c/clk.c?
Just it was done before doesn't mean it should be done again.
In an ideal world, a new platform would mean to just add
autodetection, the device tree, and the possibility of optimizing for
the CPU. Any drivers should be with the drivers, not with the
platform. We're not there yet, but we should at least try to make
things as generic as possible.
(Or to quote someone else: Didn't the mips maintainer learn anything
from the arm mess?)
> I did not just duplicate code, modified exactly. The prom-routines of
> loongson platform does not fit loongson1.For instance, the
> "cpu_clock_freq" parameter is not needed. The cpu freq. could be get
> from the PLL register directly. Moreover, the routines does not
> include the parameter "ethaddr", which is useful for embedded system.
So why not make this optional? Or depend on the system type for what
you return?
Andi
next prev parent reply other threads:[~2011-09-15 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 10:47 [PATCH] MIPS: Add basic support for Loongson1B keguang.zhang
2011-09-14 11:31 ` Andreas Barth
2011-09-14 13:54 ` Kelvin Cheung
2011-09-14 16:00 ` Andreas Barth
2011-09-15 3:27 ` Kelvin Cheung
2011-09-15 7:07 ` Andreas Barth [this message]
2011-09-14 11:51 ` Lars-Peter Clausen
2011-09-14 14:12 ` Kelvin Cheung
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=20110915070752.GU15003@mails.so.argh.org \
--to=aba@not.so.argh.org \
--cc=chenj@lemote.com \
--cc=keguang.zhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=r0bertz@gentoo.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.com \
/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.