linux-kernel - DRM Driver implementation question

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-next>] [day] [month] [year] [list]

Date:   Mon, 16 Sep 2019 13:55:45 +0000
From:   Gareth Williams <gareth.williams.jx@...esas.com>
To:     "laurent.pinchart@...asonboard.com" 
        <laurent.pinchart@...asonboard.com>,
        "kieran.bingham+renesas@...asonboard.com" 
        <kieran.bingham+renesas@...asonboard.com>
CC:     "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-renesas-soc@...r.kernel.org" 
        <linux-renesas-soc@...r.kernel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Phil Edworthy <phil.edworthy@...esas.com>,
        Fabrizio Castro <fabrizio.castro@...renesas.com>
Subject: DRM Driver implementation question

Hi Laurent/Kieran,

I need to upstream a driver for a display controller that within its registers memory region contains registers related to a PWM device. The PWM device is for controlling the backlight of the display.
Ideally, I would like to create a separated driver for the PWM, so that I can re-use "pwm-backlight", but since the registers for the PWM are right in the middle of the registers for the display controller I would need to ioremap the memory region for the PWM registers region twice, once from the display controller driver, and once from the PWM driver.
Do you think that the double ioremap would be acceptable upstream?

Kind Regards,

Gareth