From: "Måns Rullgård" <mans@mansr.com>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>, Mason <slash.tmp@free.fr>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] clocksource/drivers/tango_xtal: Add new timer for Tango SoCs
Date: Fri, 09 Oct 2015 15:51:32 +0100 [thread overview]
Message-ID: <yw1x7fmwjdsb.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <5617D139.1000103@sigmadesigns.com> (Marc Gonzalez's message of "Fri, 9 Oct 2015 16:37:45 +0200")
Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:
> Sigma Designs Tango platforms provide a 27 MHz crystal oscillator.
> Use it for clocksource, sched_clock, and delay_timer.
Given the nature of this hardware, I think it would make much more sense
to support it in a generic fashion. Otherwise the next chip that comes
along with a similar counter will result in near duplicate of this
"driver", and so on. I've suggested this before, and I even sent
patches for it (currently under discussion), but you keep refusing to
listen. Are you that desperate to see your name on a commit? The fact
that you keep rewriting, poorly, code you know I've already made
available suggests this might be the case. You even admit in private
that you couldn't have done this without looking at my tango3 tree.
Frankly, I find your behaviour shameful.
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2015-10-09 14:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 15:10 [PATCH v1] clocksource: Sigma Designs Tango 27 MHz xtal Marc Gonzalez
2015-10-06 23:09 ` Daniel Lezcano
2015-10-07 8:23 ` Marc Gonzalez
2015-10-07 9:47 ` Daniel Lezcano
2015-10-07 11:14 ` Marc Gonzalez
2015-10-07 11:35 ` Daniel Lezcano
2015-10-07 11:35 ` [PATCH v2] clocksource/drivers/tango_xtal: Add new timer for Tango SoCs Marc Gonzalez
2015-10-07 12:31 ` Daniel Lezcano
2015-10-07 13:17 ` Marc Gonzalez
2015-10-07 16:03 ` Daniel Lezcano
2015-10-07 20:12 ` Mason
2015-10-09 12:13 ` [PATCH v3] " Marc Gonzalez
2015-10-09 13:24 ` Daniel Lezcano
2015-10-09 13:46 ` Marc Gonzalez
2015-10-09 14:21 ` Daniel Lezcano
2015-10-09 16:39 ` Nicolas Pitre
2015-10-09 14:37 ` [PATCH v4] " Marc Gonzalez
2015-10-09 14:42 ` Daniel Lezcano
2015-10-09 14:59 ` [PATCH v5] " Marc Gonzalez
2015-10-16 12:07 ` Daniel Lezcano
2015-10-09 14:51 ` Måns Rullgård [this message]
2015-10-09 15:42 ` [PATCH v4] " Marc Gonzalez
2015-10-09 16:01 ` Måns Rullgård
2015-10-09 16:36 ` Marc Gonzalez
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=yw1x7fmwjdsb.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc_gonzalez@sigmadesigns.com \
--cc=slash.tmp@free.fr \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®