Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755017AbbFRM73 (ORCPT ); Thu, 18 Jun 2015 08:59:29 -0400 Received: from down.free-electrons.com ([37.187.137.238]:35650 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753341AbbFRM7U (ORCPT ); Thu, 18 Jun 2015 08:59:20 -0400 Date: Thu, 18 Jun 2015 14:59:18 +0200 From: Alexandre Belloni To: Paul Bolle Cc: Nicolas Ferre , Boris Brezillon , linux-arm-kernel@lists.infradead.org, Ludovic Desroches , Josh Wu , linux-kernel@vger.kernel.org, mturquette@baylibre.com Subject: Re: [PATCH] clk: at91: add generated clock driver Message-ID: <20150618125918.GC27492@piout.net> References: <1434547409-12232-1-git-send-email-nicolas.ferre@atmel.com> <1434611556.2385.8.camel@x220> <20150618093344.7d486e97@bbrezillon> <55827606.7020908@atmel.com> <1434614090.2385.19.camel@x220> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1434614090.2385.19.camel@x220> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1606 Lines: 36 On 18/06/2015 at 09:54:50 +0200, Paul Bolle wrote : > > I'd like though that this matter of fact doesn't block this piece of > > code from being reviewed or even better merged in order to ease this new > > SoC landing... > > The other side of that is that the sama5d2 might never make it, or take > very long to make it, into mainline. And this would then end up being > yet another chunk of code adding no value to mainline. > Come on Paul, you prefer the current situation were each vendor have there tree and when support for an SoC lands in mainline it is already deprecated? You have one vendor here, trying to get support for its SoC even before the silicon is available. Intel is always cited as being a good player in the linux community for doing exactly that. They even have to remove support for a CPU that was never manufactured... The main difference here is that we are no longer doinc everything in mach-xxx so we have to get the driver part mainlined and this requires synchronization. I really belive that you can't blame Nicolas to get the drivers first then the SoC in. Also, Atmel has a good track record and their SocS are almost fully supported in mainline, you can trust that sama5d2 support is going to land there soon. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/