linux-kernel - Re: [PATCH 1/4] drm: bridge: dw_mipi_dsi: access registers via a regmap

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: <3b3bbf68-a19e-77ea-7e7c-770f75a81a21@baylibre.com>
Date:   Mon, 4 Nov 2019 16:46:44 +0100
From:   Neil Armstrong <narmstrong@...libre.com>
To:     Adrian Ratiu <adrian.ratiu@...labora.com>,
        linux-arm-kernel@...ts.infradead.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-rockchip@...ts.infradead.org
Cc:     kernel@...labora.com, linux-kernel@...r.kernel.org,
        dri-devel@...ts.freedesktop.org,
        Boris Brezillon <boris.brezillon@...labora.com>
Subject: Re: [PATCH 1/4] drm: bridge: dw_mipi_dsi: access registers via a
 regmap

Hi Adrian,

On 04/11/2019 13:03, Adrian Ratiu wrote:
> On Mon, 04 Nov 2019, Neil Armstrong <narmstrong@...libre.com> wrote:
>> On 31/10/2019 15:26, Adrian Ratiu wrote:
>>
>> OK for the dw-mipi-dsi changes, but why should the dw_mipi_dsi-stm be changed aswell ?
>> AFAIK these are independent.
> 
> I don't understand how they are independent. Isn't the stm driver also using the same dw-mipi-dsi bridge as rockchip and now imx since it was first added in commit
> c1c026dbc183 ("drm/stm: Add STM32 DSI controller driver") ?
> 
> I don't have the hardware to test the stm driver on a live boot, but compilation certainly fails if I don't modify it :)

Ignore my comment, this patch is fine, please keep:
Reviewed-by: Neil Armstrong <narmstrong@...libre.com>

when resending.

Neil

> 
>>
>> Neil