From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <Pawel.Moll@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>
Subject: Re: [PATCH v2 RESEND] pwm: Add CLPS711X PWM support
Date: Sat, 01 Mar 2014 17:56:35 +0400 [thread overview]
Message-ID: <1393682195.224091960@f280.i.mail.ru> (raw)
In-Reply-To: <201403011240.09137.arnd@arndb.de>
Суббота, 1 марта 2014, 12:40 +01:00 от Arnd Bergmann <arnd@arndb.de>:
> On Saturday 01 March 2014, Alexander Shiyan wrote:
> > I want to elaborate on the current CLPS711X lineup:
> > PS7110 - EOL October 30, 2001
> > PS7111 - EOL October 30, 2001
> > EP7209 - EOL April 25, 2003
> > EP7211 - EOL April 25, 2003
> > EP7212 - EOL April 25, 2003
> > CS89712 - EOL August 15, 2005
> > EP7309 - Production
> > EP7311 - Production
> > EP7312 - Production
>
> Thanks for the list. I wonder if there is a good place to keep this in the
> kernel source for reference.
>
> > So at the moment, and long enough, produced only three models of CPUs.
> > I am sure that the hardware with old CPUs will not be able to use the
> > new kernel due to memory limitations, low CPU frequency, etc.
> >
> > My suggestion is to always use a compatibility string for platform entirely,
> > ie "cirrus,clps711x-$UNIT", otherwise it may result in misleading.
>
> From your list, it's pretty clear that there won't be any new chips named
> PS711x for x > 1, so using that string is not ambiguous. That is good
> to know. It's also the oldest chip in the family, so naming things after that
> is consistent.
>
> > In any case, I would like to hear the final decision on this issue,
> > since there are several drivers already using this scheme and some drivers
> > awaiting applying into the kernel.
> > I do not insist on its position, but just want to clarify to make changes
> > to existing drivers and use the approved compatibility string in the future.
> > At the current stage, these changes will not lead to anything terrible.
>
> How about we keep using the cirrus,clps711x as the string that drivers
> match against, but change the DT representation to always list the specific
> model in addition? That way we are prepared to handle quirks if we need to,
> but you don't have to change the binding in incompatible ways.
>
> This means you should list e.g.
>
> compatible = "cirrus,ep7309-pwm", "cirrus,clps711x-pwm";
>
> or
>
> compatible = "cirrus,clps7110-pwm", "cirrus,clps711x-pwm";
>
> depending on the model. For units that were introduced in a later
> model, I would recommend to use the first model that had it rather
> than the original clps711x that didn't, like
>
> compatible = "cirrus,ep7311-kitchensink", "cirrus-ep7211-kitchensink";
>
> For bindings that are already reviewed and merged, I wouldn't change
> them any more even if they inaccurately list clps711x for units that
> were not present in clps7111, but for new ones I'd prefer to follow
> the common practice to your best knowledge.
Excellent, let's do so. I will prepare a patch that will change compatibility
strings for examples in the current bindings documents.
For this driver (PWM), I just send a third version.
---
next prev parent reply other threads:[~2014-03-01 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 15:27 [PATCH v2 RESEND] pwm: Add CLPS711X PWM support Alexander Shiyan
[not found] ` <1393342067-9086-1-git-send-email-shc_work-JGs/UdohzUI@public.gmane.org>
2014-02-25 15:33 ` Arnd Bergmann
2014-02-25 15:47 ` Alexander Shiyan
2014-02-25 15:50 ` Arnd Bergmann
2014-02-26 16:00 ` Mark Rutland
2014-02-26 16:50 ` Alexander Shiyan
2014-02-27 10:27 ` Mark Rutland
2014-03-01 6:06 ` Alexander Shiyan
2014-03-01 11:40 ` Arnd Bergmann
2014-03-01 13:56 ` Alexander Shiyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-05 15:22 Alexander Shiyan
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=1393682195.224091960@f280.i.mail.ru \
--to=shc_work@mail.ru \
--cc=Pawel.Moll@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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