From: Arnd Bergmann <arnd@arndb.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-pwm@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [PATCH v2 RESEND] pwm: Add CLPS711X PWM support
Date: Tue, 25 Feb 2014 16:50:32 +0100 [thread overview]
Message-ID: <5211076.9eDkSrDagS@wuerfel> (raw)
In-Reply-To: <1393343277.220396804@f361.i.mail.ru>
On Tuesday 25 February 2014 19:47:57 Alexander Shiyan wrote:
> Вторник, 25 февраля 2014, 16:33 +01:00 от Arnd Bergmann <arnd@arndb.de>:
> > On Tuesday 25 February 2014 19:27:47 Alexander Shiyan wrote:
=> >
> > We really want to avoid wildcards in compatible strings. Can you call this
> > "cirrus,cs89712-pwm" to match the first SoC that came with this hardware?
> > Obviously if there was some chip before that (I'm not familiar with the
> > model numbers), use that instead.
> >
> > You can either list all chips you know that have this in the driver,
> > or you use "cirrus,cs89712-pwm" as the fallback, and use the name of
> > the SoC you have as the more specific string.
>
> It seems that in this case we will need to modify the compatibility string
> for other drivers that are already available in the kernel...
Ah, right. I missed the binding for gpio and serial going in.
DT maintainers, any suggestion on how we should proceed here?
AFAICT, clps711x platform support is still work-in-progress, so we don't
have any upstream users to worry about yet, but changing them is still
going to be slightly messy.
Arnd
next prev parent reply other threads:[~2014-02-25 15: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 [this message]
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
-- 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=5211076.9eDkSrDagS@wuerfel \
--to=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=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shc_work@mail.ru \
--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