From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ryan Mallon <rmallon@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Bill Gatliff <bgat@billgatliff.com>,
linux-kernel@vger.kernel.org, Ryan Mallon <ryan@bluewatersys.com>,
Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] PWM: add pwm framework support
Date: Mon, 4 Jul 2011 16:19:24 +0200 [thread overview]
Message-ID: <20110704141924.GF316@e-circ.dyndns.org> (raw)
In-Reply-To: <201107041553.07643.arnd@arndb.de>
On Mon, Jul 04, 2011 at 03:53:07PM +0200, Arnd Bergmann wrote:
> On Monday 04 July 2011, Kurt Van Dijck wrote:
> > With socketCAN, we encountered a similar problem. Every chip maker
> > tries to create added value by means of special options. You can't
> > support them all in the framework. Therefore, sysfs can be added
> > to configure special things.
>
> I would expect that pwm is much simpler than CAN,
ack
> so the amount
> of creativity there is also limited.
That is true for a single PWM channel.
With multiple PWM channels, hardware design tends to be creative in coupling
several channels together somehow in order to create some diesel engine
control signal ...
>
> Arnd
Anyway, I explained my concern. It's just _an_ opinion.
Kurt
next prev parent reply other threads:[~2011-07-04 14:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 10:41 [PATCH v3] implement a generic PWM framework Sascha Hauer
2011-06-30 10:41 ` [PATCH 1/3] PWM: add pwm framework support Sascha Hauer
2011-06-30 11:07 ` Bill Gatliff
2011-06-30 12:41 ` Arnd Bergmann
2011-06-30 16:17 ` Bill Gatliff
2011-06-30 17:02 ` Sascha Hauer
2011-06-30 19:45 ` Bill Gatliff
2011-06-30 23:24 ` Ryan Mallon
2011-07-01 0:33 ` H Hartley Sweeten
2011-07-01 0:55 ` Mike Frysinger
2011-07-01 7:37 ` Sascha Hauer
2011-07-01 8:28 ` Ryan Mallon
2011-07-01 8:54 ` Sascha Hauer
2011-07-02 0:40 ` Ryan Mallon
2011-07-04 7:55 ` Sascha Hauer
2011-07-04 10:43 ` Ryan Mallon
2011-07-04 11:05 ` Kurt Van Dijck
2011-07-04 13:53 ` Arnd Bergmann
2011-07-04 14:19 ` Kurt Van Dijck [this message]
2011-07-04 12:43 ` Sascha Hauer
2011-07-04 14:07 ` Arnd Bergmann
2011-12-07 8:53 ` Thierry Reding
2011-12-07 9:07 ` Sascha Hauer
2011-12-14 10:03 ` Thierry Reding
2011-12-14 11:37 ` Sascha Hauer
2011-07-01 9:49 ` Dmitry Eremin-Solenikov
2011-06-30 10:41 ` [PATCH 2/3] ARM mxs: adjust pwm resources to what the driver expects Sascha Hauer
2011-06-30 11:30 ` Arnd Bergmann
2011-06-30 10:41 ` [PATCH 3/3] pwm: Add a i.MX23/28 pwm driver Sascha Hauer
2011-06-30 11:42 ` Arnd Bergmann
2011-06-30 15:11 ` Sascha Hauer
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=20110704141924.GF316@e-circ.dyndns.org \
--to=kurt.van.dijck@eia.be \
--cc=arnd@arndb.de \
--cc=bgat@billgatliff.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmallon@gmail.com \
--cc=ryan@bluewatersys.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.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
all inboxes | Powered by JetHome®