archive mirror
 help / color / mirror / Atom feed
From: Jonathan Bakker <>
To: Tomasz Figa <>, Krzysztof Kozlowski <>
Cc: linux-samsung-soc <>,
	" DRIVERS" <>,
	Linux Kernel Mailing List <>,
	Hans Verkuil <>,
	Kyungmin Park <>,, Sylwester Nawrocki <>,
	Mauro Carvalho Chehab <>,,
	Linux Media Mailing List <>
Subject: Re: [PATCH 00/11] media: exynos4-is: Improve support for s5pv210 and parallel ports
Date: Wed, 24 Jun 2020 14:14:16 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Tomasz,

On 2020-06-24 4:58 a.m., Tomasz Figa wrote:
> On Wed, Jun 24, 2020 at 1:54 PM Krzysztof Kozlowski <> wrote:
>> On Wed, Jun 24, 2020 at 01:39:50PM +0200, Hans Verkuil wrote:
>>> Can someone from Samsung or someone who knows this SoC take a look at this series?
>>> This series looks sane to me, so I'll probably merge this if nobody replies
>>> in the next two weeks or so.
>> Unfortunately I don't know the media part on S5Pv210 at all so I cannot
>> provide any feedback. There are not many active users of these SoCs
>> nowadays. One of hem is Jonathan, so if he wants to change something he will
>> mostly break/affect his own setup. :) Therefore I think it is safe to merge.
> I think this driver is also used on Exynos4210 and on some setups with
> 4412 where the ISP is not used.

Yes, this driver is also used by Exynos4210 and Exynos4412, notably by the Galaxy S3 series.
They don't use the parallel ports, but rather the CSIS.  I don't believe I've broken support
for that, but I don't have the hardware to test.

My other remaining concern is whether to adjust the camera port A/camera port B to match the
device tree documentation or to update the documentation to match the driver.  I decided to
update the driver in these patches, but it is much simpler to simply update the binding doc.
The only mainline user of the parallel ports is the Goni dev board which appears to be setup
for the driver way of numbering as opposed to the binding doc.  I have no strong preference
on which way to actually go.

> I can't promise anything, but I'll try to do a high level review.
> Hopefully I still have some memory from the time I used to play with
> this hardware.

Thanks, that would be appreciated,

> Best regards,
> Tomasz
iommu mailing list

           reply	other threads:[~2020-06-25  8:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).