Re: [PATCH v3 06/10] pwm: Add NVIDIA Tegra SoC support |
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v3 06/10] pwm: Add NVIDIA Tegra SoC support
- From: Thierry Reding <thierry.reding@xxxxxxxxxxxxxxxxx>
- Date: Fri, 24 Feb 2012 07:48:51 +0100
- Cc: devicetree-discuss@xxxxxxxxxxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, linux-tegra@xxxxxxxxxxxxxxx, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, Matthias Kaehlcke <matthias@xxxxxxxxxxxx>, Kurt Van Dijck <kurt.van.dijck@xxxxxx>, Rob Herring <rob.herring@xxxxxxxxxxx>, Grant Likely <grant.likely@xxxxxxxxxxxx>, Colin Cross <ccross@xxxxxxxxxxx>, Olof Johansson <olof@xxxxxxxxx>, Richard Purdie <rpurdie@xxxxxxxxx>, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, Mitch Bradley <wmb@xxxxxxxxxxxxx>, Mike Frysinger <vapier@xxxxxxxxxx>, Eric Miao <eric.y.miao@xxxxxxxxx>, Lars-Peter Clausen <lars@xxxxxxxxxx>
- In-reply-to: <4F460616.3080400@gmail.com>
- User-agent: Mutt/1.5.21 (2010-09-15)
* Ryan Mallon wrote:
> On 23/02/12 19:14, Thierry Reding wrote:
> > * Ryan Mallon wrote:
[...]
> >> pwmchip_add should probably verify that the initialisation of the
> >> pwm_chip structure is sane to avoid problems like this.
> >
> > Absolutely. What would be the best response to an invalid struct pwm_chip? I
> > suppose at least returning -EINVAL, perhaps complemented with WARN_ON?
>
> Just returning -EINVAL should be okay. I don't think you need a WARN_ON,
> since failing to register the hardware should be enough of a reason for
> a user to report a problem.
Okay, will do.
Thierry
Attachment:
pgpvhvKTyPbi6.pgp
Description: PGP signature
[ARM Kernel]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]