From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: mchehab@redhat.com
Cc: linux-media@vger.kernel.org,
"Frank Schäfer" <fschaefer.oss@googlemail.com>
Subject: [PATCH 0/4] em28xx: GPIO registers: extend definitions and remove the caching
Date: Mon, 3 Jun 2013 20:12:01 +0200 [thread overview]
Message-ID: <1370283125-2231-1-git-send-email-fschaefer.oss@googlemail.com> (raw)
The first two patches add some missing GPIO register definitions,
while the third patch is a minor code movement to clean up things.
The fourth patch finally removes the GPIO register caching.
Frank Schäfer (4):
em28xx: extend GPIO register definitions for the em25xx,
em276x/7x/8x, em2874/174/84
em28xx: improve em2820-em2873/83 GPIO port register definitions and
descriptions
em28xx: move snapshot button bit definition for reg 0x0C from
em28xx-input.c to em28xx.h
em28xx: remove GPIO register caching
drivers/media/usb/em28xx/em28xx-cards.c | 220 +++++++++++++++----------------
drivers/media/usb/em28xx/em28xx-core.c | 27 +---
drivers/media/usb/em28xx/em28xx-dvb.c | 68 +++++-----
drivers/media/usb/em28xx/em28xx-input.c | 1 -
drivers/media/usb/em28xx/em28xx-reg.h | 23 +++-
drivers/media/usb/em28xx/em28xx.h | 6 -
6 Dateien geändert, 159 Zeilen hinzugefügt(+), 186 Zeilen entfernt(-)
--
1.7.10.4
next reply other threads:[~2013-06-03 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 18:12 Frank Schäfer [this message]
2013-06-03 18:12 ` [PATCH 1/4] em28xx: extend GPIO register definitions for the em25xx, em276x/7x/8x, em2874/174/84 Frank Schäfer
2013-06-03 18:12 ` [PATCH 2/4] em28xx: improve em2820-em2873/83 GPIO port register definitions and descriptions Frank Schäfer
2013-06-03 18:12 ` [PATCH 3/4] em28xx: move snapshot button bit definition for reg 0x0C from em28xx-input.c to em28xx.h Frank Schäfer
2013-06-03 18:12 ` [PATCH 4/4] em28xx: remove GPIO register caching Frank Schäfer
2013-06-03 18:13 ` [PATCH 0/4] em28xx: GPIO registers: extend definitions and remove the caching Frank Schäfer
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=1370283125-2231-1-git-send-email-fschaefer.oss@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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