linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: at91: add generated clock driver
Date: Thu, 18 Jun 2015 15:28:55 +0200	[thread overview]
Message-ID: <5582C797.80203@atmel.com> (raw)
In-Reply-To: <20150618125918.GC27492@piout.net>

Le 18/06/2015 14:59, Alexandre Belloni a ?crit :
> 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.

I've just posted it BTW.

And it contains the "HAVE_AT91_GENERATED" symbol.

Bye,
-- 
Nicolas Ferre

  reply	other threads:[~2015-06-18 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 13:23 [PATCH] clk: at91: add generated clock driver Nicolas Ferre
2015-06-18  7:12 ` Paul Bolle
2015-06-18  7:33   ` Boris Brezillon
2015-06-18  7:40     ` Nicolas Ferre
2015-06-18  7:54       ` Paul Bolle
2015-06-18 12:40         ` Nicolas Ferre
2015-06-18 14:46           ` Paul Bolle
2015-06-18 12:59         ` Alexandre Belloni
2015-06-18 13:28           ` Nicolas Ferre [this message]
2015-06-18 15:11           ` Paul Bolle
2015-06-18  7:44     ` Paul Bolle
2015-06-18 15:25 ` Boris Brezillon
2015-06-22 16:50   ` Nicolas Ferre

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=5582C797.80203@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).