From: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
To: Mans Rullgard <mans@mansr.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Mason <slash.tmp@free.fr>
Subject: Re: [PATCH] clk: add support for Sigma Designs SMP86xx/87xx clocks
Date: Fri, 9 Oct 2015 18:42:09 +0200 [thread overview]
Message-ID: <5617EE61.6080805@sigmadesigns.com> (raw)
In-Reply-To: <1444394121-9587-1-git-send-email-mans@mansr.com>
On 09/10/2015 14:35, Mans Rullgard wrote:
> This adds support for most of the clocks in the Sigma Designs
> SMP86xx (tango3) and SMP87xx (tango4) chips.
>
> Signed-off-by: Mans Rullgard <mans@mansr.com>
> ---
> I'm sending this now to avoid the maintainers wasting more time reviewing
> the woefully incomplete patch that was posted earlier this week. Unlike
> that patch, this driver accurately represents the various PLLs, muxes,
> and dividers, allowing it to work correctly across all the chip variants.
> That said, this patch still needs some work, which is why I have not posted
> it sooner. Obvious shortcomings off the top of my head:
> - DT binding documentation is missing
> - Most clocks are mostly read-only
> - Some control register fields are ignored (lack of documentation)
As the author of the supposedly "woefully incomplete patch that was posted
earlier this week", thanks for having CCed me in the discussion...
Your driver comes in at 656 lines. Mine is 60 lines (give or take).
Having access to the (incomplete) documentation, the Verilog code,
and the HW engineer who wrote the clock generator, I have told you
that your driver was unnecessarily complex because it made use of
features that were either not used (such as the post-dividers) or
disabled because of a HW bug (like the sysclk_mux divider).
But somehow, you know better, and your driver handles everything
that my driver cannot...
Could you perhaps be more specific (this is a technical mailing list
after all) so that I may address your concerns one by one?
Regards.
prev parent reply other threads:[~2015-10-09 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 12:35 [PATCH] clk: add support for Sigma Designs SMP86xx/87xx clocks Mans Rullgard
2015-10-09 16:42 ` Marc Gonzalez [this message]
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=5617EE61.6080805@sigmadesigns.com \
--to=marc_gonzalez@sigmadesigns.com \
--cc=arnd@arndb.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=slash.tmp@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.