lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZUtnCfAjv0P4oZvq@pc-70.home>
Date:   Wed, 8 Nov 2023 11:46:33 +0100
From:   Mehdi Djait <mehdi.djait@...tlin.com>
To:     Michael Riesch <michael.riesch@...fvision.net>
Cc:     mchehab@...nel.org, heiko@...ech.de, hverkuil-cisco@...all.nl,
        krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org,
        conor+dt@...nel.org, linux-media@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        thomas.petazzoni@...tlin.com, alexandre.belloni@...tlin.com,
        maxime.chevallier@...tlin.com, paul.kocialkowski@...tlin.com
Subject: Re: [PATCH v9 2/3] media: rockchip: Add a driver for Rockchip's
 camera interface

Hello Michael,

On Wed, Nov 08, 2023 at 09:50:25AM +0100, Michael Riesch wrote:
> Hi Mehdi,
> I applied your patches and added some modifications (= crude hacks) on
> top of them to bring up the RK3568 VICAP (note that I don't have any
> PX30 hardware). This setup is not yet able to capture the input stream
> (from a HDMI receiver chip), but I am on it.
> 
> One question popped up: to get the cif driver to probe with my device
> tree I had to request the IRQ with IRQF_SHARED. This is due to the
> approach that the CIF block has one IRQ but is represented by two
> drivers: the cif driver and the rockchip-iommu driver.

It was IRQF_SHARED when I submitted the v6 but changed it after reviews.

> 
> Subsequently I was surprised that you are not using the MMU at all,
> although the PX30 VIP features one. Is there any particular reason for that?

No particular reason. The IOMMU did not work and was not included when the 
patch series for this driver were submitted years ago. I focused on
fixing all the issues I found, complying with v4l2 guidelines and
getting an upstreamable driver: so I did not add the support.

> 
> Can we request the IRQ with IRQF_SHARED anyway?

Yes I will change it back to SHARED.

--
Kind Regards
Mehdi Djait

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ