linux-mips
[Top] [All Lists]

Re: [PATCH] generic clk API implementation for MIPS

To: vagabon.xyz@gmail.com
Subject: Re: [PATCH] generic clk API implementation for MIPS
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Wed, 27 Jun 2007 16:51:25 +0900 (JST)
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
In-reply-to: <cda58cb80706261302r67629f62hf560d5229df34663@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <cda58cb80706260820y4db3eacnae4dff0101852d52@mail.gmail.com> <20070627.013312.25479645.anemo@mba.ocn.ne.jp> <cda58cb80706261302r67629f62hf560d5229df34663@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
On Tue, 26 Jun 2007 22:02:53 +0200, "Franck Bui-Huu" <vagabon.xyz@gmail.com> 
wrote:
> It seems that clock configuration highly depends on the board, not the
> arch. For example, a board can have only static clocks which won't be
> unregistered later. In that case most of code provided by the patch is
> useless.
> 
> So maybe the best thing is to let each board implements their own
> generic clock API (exactly like the generic GPIO API you did
> recently). Or make a default implementation (your patch) and allow
> others boards to make their own implementation.

Hmm... I had thought the default implementation would be useful, but
now I change my mind ;)  What people expected on its implementation
would vary too much.

Now I think leaving all implementation to platform code is better.
I'll send rbtx4938 implementation (minimum one just for SPI driver)
soon.

Ralf, please do not apply or queue this patch :)

---
Atsushi Nemoto

<Prev in Thread] Current Thread [Next in Thread>