From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [patch 2.6.23-rc2-omap1] tsc210x cleanup
Date: Wed, 15 Aug 2007 03:54:44 -0700 [thread overview]
Message-ID: <20070815105444.GI19754@atomide.com> (raw)
In-Reply-To: <200708132238.13676.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [070813 23:11]:
> This is mostly cleanup of the tsc210x patch, but some bugs were fixed so now
> it works on tsc2101 too. Also, a few issues are now noted in the code:
>
> Tool-reported:
> - Address checkpatch.pl issues in the original patch
> - And also "sparse" issues
>
> Previously wrong:
> - Cope with CONFIG_SOUND_MODULE
> - Register accessor routines will now return error codes
> - ... many callers now abort cleanly after errors
> - Don't depend on seeing only a rev #1 tsc2102 chip!
> - Add missing EXPORT_SYMBOL declarations
>
> Style issues:
> - BUG_ON() is strongly to be avoided
> - So are macros that capture variables
> - And needless casting from void pointers
> - And type punning
> - Use dev_*() for messaging where practical
> - Use u16 not uint16_t, etc
> - Various other whitespace issues
> - Avoid __FUNCTION__
> - Single-lines for file-top comments; no whole paths
>
> Object code size and Other cleanup:
> - Compile most strings out unless -DDEBUG is configured (saving space)
> - Move some code into exit sections (then it may well vanish, saving space)
> - Add some header comments
>
> Open issues:
> - Hwmon needs to know VREF and the chip type, and to scale its values
> - Upstream push should exclude audio until some version is working
> - Audio will needs to export symbols to modules, too
> - Lots of the I/O calls (especially audio) still don't handle errors
> - How could board init code get board-specific temp calibration data?
>
> Also the Kconfig is more open-ended; tsc210x might in the future include the
> tsc2100 and tsc2111, it doesn't need to be limited to tsc2101 and tsc2102.
Pushing today.
Tony
next prev parent reply other threads:[~2007-08-15 10:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:44 Common code for TSC 2101 and 2102 andrzej zaborowski
2007-07-13 6:46 ` Trilok Soni
2007-07-13 7:10 ` Trilok Soni
2007-07-13 19:29 ` andrzej zaborowski
2007-07-13 20:04 ` David Brownell
2007-08-10 7:29 ` Tony Lindgren
2007-08-11 3:04 ` David Brownell
2007-08-13 7:05 ` Tony Lindgren
2007-08-14 5:34 ` David Brownell
2007-09-23 22:37 ` andrzej zaborowski
2007-08-14 5:38 ` [patch 2.6.23-rc2-omap1] tsc210x cleanup David Brownell
2007-08-15 10:54 ` Tony Lindgren [this message]
2007-08-14 5:40 ` [patch 2.6.23-rc2-omap1] H4 support for tsc210x David Brownell
2007-08-14 6:45 ` David Brownell
2007-08-15 10:54 ` Tony Lindgren
2007-07-13 18:38 ` Common code for TSC 2101 and 2102 David Brownell
2007-07-15 20:18 ` David Brownell
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=20070815105444.GI19754@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.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