From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Subject: [PATCH 0/7] smiapp, omap3isp: Cleanups and fixes
Date: Thu, 13 Feb 2020 11:49:27 +0200 [thread overview]
Message-ID: <20200213094934.18595-1-sakari.ailus@linux.intel.com> (raw)
Hi all,
This set contains a small fix for the omap3isp crashing the system, as
well as cleanups for the smiapp driver.
Sakari Ailus (7):
omap3isp: Prevent enabling CCDC when stopping streaming
smiapp: Simplify condition for choosing 8-bit access
smiapp: Use unaligned get and put functions
smiapp: Turn limit lookup into a function
smiapp: Move SMIA limit reading up
smiapp: Refactor reading SMIA limits
smiapp: Move definitions under driver directory
drivers/media/i2c/smiapp/smiapp-core.c | 259 +++++++++++-----------
drivers/media/i2c/smiapp/smiapp-reg.h | 4 +
drivers/media/i2c/smiapp/smiapp-regs.c | 71 ++----
drivers/media/i2c/smiapp/smiapp.h | 44 +++-
drivers/media/platform/omap3isp/ispccdc.c | 4 +
include/media/i2c/smiapp.h | 63 ------
6 files changed, 200 insertions(+), 245 deletions(-)
delete mode 100644 include/media/i2c/smiapp.h
--
2.20.1
next reply other threads:[~2020-02-13 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 9:49 Sakari Ailus [this message]
2020-02-13 9:49 ` [PATCH 1/7] omap3isp: Prevent enabling CCDC when stopping streaming Sakari Ailus
2020-02-13 9:49 ` [PATCH 2/7] smiapp: Simplify condition for choosing 8-bit access Sakari Ailus
2020-02-13 9:49 ` [PATCH 3/7] smiapp: Use unaligned get and put functions Sakari Ailus
2020-02-13 9:49 ` [PATCH 4/7] smiapp: Turn limit lookup into a function Sakari Ailus
2020-02-13 9:49 ` [PATCH 5/7] smiapp: Move SMIA limit reading up Sakari Ailus
2020-02-13 9:49 ` [PATCH 6/7] smiapp: Refactor reading SMIA limits Sakari Ailus
2020-02-13 9:49 ` [PATCH 7/7] smiapp: Move definitions under driver directory Sakari Ailus
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=20200213094934.18595-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).