From: Jonathan Bakker <xc-racer2@live.ca>
To: kyungmin.park@samsung.com, s.nawrocki@samsung.com,
mchehab@kernel.org, kgene@kernel.org, krzk@kernel.org,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jonathan Bakker <xc-racer2@live.ca>
Subject: [PATCH 00/11] media: exynos4-is: Improve support for s5pv210 and parallel ports
Date: Sat, 25 Apr 2020 19:26:39 -0700 [thread overview]
Message-ID: <BN6PR04MB06602E7221CC7455F3142540A3AE0@BN6PR04MB0660.namprd04.prod.outlook.com> (raw)
This patchset improves support in the exynos4-is driver for s5pv210
platforms as well as for sensors connected to the parallel ports
and not using the CSIS device.
Fixes range from nullptr exceptions to probe fixes to JPEG fixes.
Notably, it also changes the fwnode probing of parallel port sensors
to match the binding doc. The binding doc said port A = reg 0 and
port B = reg 1 but the driver implemented A=1 and B=2. The only in-tree
user of parallel ports is currently Goni, which notes that it uses port
A but has reg = 1. Also note that the sensor driver is not mainlined
despite being present. I have left the DTS as-is.
Some patches cleaning up non-DT support are also included.
The patches have been tested on a first-gen Galaxy S GT-i900M device based
on S5PV210. Two sensors (CE147 and S5KA3DFX, both with non-mainline
drivers), both attached to port A, were succesfully used.
Jonathan Bakker (10):
media: exynos4-is: Remove static driver data for S5PV210 FIMC variants
media: exynos4-is: Fix nullptr when no CSIS device present
media: exynos4-is: Correct missing entity function initialization
media: exynos4-is: Improve support for sensors with multiple pads
media: exynos4-is: Properly set JPEG options when not using CSIS
media: exynos4-is: Add support for multiple sensors on one port
media: exynos4-is: Remove inh_sensor_ctrls
media: exynos4-is: Remove unused struct member input_index
media: exynos4-is: Prevent duplicate call to media_pipeline_stop
media: exynos4-is: Correct parallel port probing
Tomasz Figa (1):
media: exynos4-is: Request syscon only if ISP writeback is present
.../media/platform/exynos4-is/fimc-capture.c | 22 ++----
drivers/media/platform/exynos4-is/fimc-core.c | 67 ++----------------
drivers/media/platform/exynos4-is/fimc-core.h | 5 --
drivers/media/platform/exynos4-is/fimc-reg.c | 7 ++
drivers/media/platform/exynos4-is/media-dev.c | 68 ++++++++++++++-----
drivers/media/platform/exynos4-is/media-dev.h | 1 +
include/media/drv-intf/exynos-fimc.h | 2 +-
7 files changed, 72 insertions(+), 100 deletions(-)
--
2.20.1
next reply other threads:[~2020-04-26 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 2:26 Jonathan Bakker [this message]
2020-06-24 11:39 ` [PATCH 00/11] media: exynos4-is: Improve support for s5pv210 and parallel ports Hans Verkuil
2020-06-24 11:54 ` Krzysztof Kozlowski
2020-06-24 11:58 ` Tomasz Figa
2020-06-24 21:14 ` Jonathan Bakker
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=BN6PR04MB06602E7221CC7455F3142540A3AE0@BN6PR04MB0660.namprd04.prod.outlook.com \
--to=xc-racer2@live.ca \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=s.nawrocki@samsung.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;
as well as URLs for NNTP newsgroup(s).