From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Tue, 02 Feb 2016 00:34:37 +0100 (CET) Received: from localhost.localdomain ([127.0.0.1]:41984 "EHLO linux-mips.org" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S27010131AbcBAXef0lbti (ORCPT ); Tue, 2 Feb 2016 00:34:35 +0100 Received: from scotty.linux-mips.net (localhost.localdomain [127.0.0.1]) by scotty.linux-mips.net (8.15.2/8.14.8) with ESMTP id u11NYY7M028754; Tue, 2 Feb 2016 00:34:34 +0100 Received: (from ralf@localhost) by scotty.linux-mips.net (8.15.2/8.15.2/Submit) id u11NYYMQ028753; Tue, 2 Feb 2016 00:34:34 +0100 Date: Tue, 2 Feb 2016 00:34:34 +0100 From: Ralf Baechle To: Alban Cc: Antony Pavlov , linux-mips@linux-mips.org, Gabor Juhos Subject: Re: [RFC v3 02/14] MIPS: ath79: use clk-ath79.c driver for AR913X/AR933X Message-ID: <20160201233433.GA28652@linux-mips.org> References: <1453580251-2341-1-git-send-email-antonynpavlov@gmail.com> <1453580251-2341-3-git-send-email-antonynpavlov@gmail.com> <20160125232428.6472f4e6@tock> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160125232428.6472f4e6@tock> User-Agent: Mutt/1.5.24 (2015-08-30) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 51605 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ralf@linux-mips.org Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Mon, Jan 25, 2016 at 11:24:28PM +0100, Alban wrote: > > + if (IS_ENABLED(CONFIG_OF) && mips_machtype == ATH79_MACH_GENERIC_OF) { > > + return; > > + } > > + > > I think it would make more sense to move the whole implementation to > drivers/clk, otherwise we'll need to maintain two implementations. As a general rule, if there's a driver subsystem for something, I want code to go there, not arch/mips. Ralf