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] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 15 Oct 2021 10:19:13 +0200
From:   nicolas saenz julienne <>
To:     Mwesigwa Guma <>,
Cc:     Greg Kroah-Hartman <>,
        Stefan Wahren <>,
        Ojaswin Mujoo <>,
        Dan Carpenter <>,
        Amarjargal Gundjalam <>,
        Phil Elwell <>,,,,,,
        Joel Savitz <>,
        Chukpozohn Toe <>,
        Clark Williams <>
Subject: Re: [PATCH] staging: vchiq_arm: Add 36-bit address support

Hi Mwesigwa,

On Thu, 2021-10-14 at 18:32 -0400, Mwesigwa Guma wrote:
> Cc: Nicolas Saenz Julienne <>
> Cc: Greg Kroah-Hartman <>
> Cc: Stefan Wahren <>
> Cc: Ojaswin Mujoo <>
> Cc: Dan Carpenter <>
> Cc: Amarjargal Gundjalam <>
> Cc: Phil Elwell <>
> Cc:
> Cc: 
> Cc: 
> Cc: 
> Cc:
> Cc: Joel Savitz <>
> Cc: Chukpozohn Toe <>
> Cc: Clark Williams <>
> This is a forward port of Phil Elwell's commit from the Raspberry Pi
> Linux fork described as follows [1]:
>     Conditional on a new compatible string, change the pagelist encoding
>     such that the top 24 bits are the pfn, leaving 8 bits for run length
>     (-1), giving a 36-bit address range.
>     Manage the split between addresses for the VPU and addresses for the
>     40-bit DMA controller with a dedicated DMA device pointer that on non-
>     BCM2711 platforms is the same as the main VCHIQ device. This allows
>     the VCHIQ node to stay in the usual place in the DT.
> This commit enables VCHIQ device access on a Raspberry Pi 4B running the 
> mainline Linux kernel.
> Tested on Fedora Linux running on a Raspberry Pi 4B.
> [1]:
> Signed-off-by: Mwesigwa Guma <>

I see a lot happening on this patch. You're:

 - Registering a number of child devices that don't seem to exist upstream
   ('vcsm-cma', 'bcm2835-codec', and 'bcm2825-isp').
 - Updating vchiq_register_child(). 
 - Adding brcm,bcm2711-vchiq's compatible string (no dt bindings? see
 - Looking for 'brcm,bcm2711-dma' in the devicetree.
 - Using 'brcm,bcm2711-dma's' device node to re-generate the page lists.

Each one of these should at least be a separate patch, which proper
justification[1]. You can't just take downstream fixes, rebase them and send
them upstream. You really have to own them, undestand what's happening and
repurpose everything so it's up to standard even if it means diverging from
what downstream is doing.


[1] Have a look at Documentation/process/submitting-patches.rst.

Powered by blists - more mailing lists