From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Cc: Richard Woodruff <r-woodruff2@ti.com>
Subject: [PATCH 0/2] OMAP: I2C: reprogram OCP_SYSCONFIG after device reset
Date: Tue, 14 Oct 2008 06:19:21 -0600 [thread overview]
Message-ID: <20081014121031.1210.96214.stgit@localhost.localdomain> (raw)
Hello,
This patch set programs the I2C controller OCP_SYSCONFIG register
after the driver resets the device. It is derived from the changes
mentioned by Richard Woodruff <r-woodruff2@ti.com> at
http://git.omapzoom.org/?p=omapkernel;a=blob;f=drivers/i2c/busses/i2c-omap.c;hb=d0b4bad4926f9a147a73498f7a62a0ae1cf6f83a
however, the CLOCKACTIVITY change on clk_enable()/clk_disable() in that
code currently seems pointless, so it has been excluded until more
information is available from TI or until problems are encountered.
This patchset should only change behavior on OMAP2x30 and OMAP3xxx devices.
Boot-tested on 2430SDP and 3430SDP; compile-tested with the 5912OSK (OMAP1)
defconfig. Comments welcome,
- Paul
---
text data bss dec hex filename
3472584 160600 105760 3738944 390d40 vmlinux.3430sdp.orig
3472616 160600 105760 3738976 390d60 vmlinux.3430sdp
drivers/i2c/busses/i2c-omap.c | 65 ++++++++++++++++++++++++++++++++---------
1 files changed, 50 insertions(+), 15 deletions(-)
next reply other threads:[~2008-10-14 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 12:19 Paul Walmsley [this message]
2008-10-14 12:19 ` [PATCH 1/2] OMAP: I2C: convert 'rev1' flag to generic 'rev' u8 Paul Walmsley
2008-10-14 12:19 ` [PATCH 2/2] OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset Paul Walmsley
2008-10-19 13:12 ` Woodruff, Richard
2008-10-19 13:06 ` [PATCH 0/2] OMAP: I2C: reprogram OCP_SYSCONFIG after device reset Woodruff, Richard
2008-11-21 21:34 ` Tony Lindgren
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=20081014121031.1210.96214.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.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