Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Gareth Williams <gareth.williams.jx@renesas.com>
To:     Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
CC:     "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-renesas-soc@vger.kernel.org" 
        <linux-renesas-soc@vger.kernel.org>,
        Geert Uytterhoeven <geert+renesas@glider.be>,
        Phil Edworthy <phil.edworthy@renesas.com>,
        Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
        "laurent.pinchart@ideasonboard.com" 
        <laurent.pinchart@ideasonboard.com>,
        "kieran.bingham+renesas@ideasonboard.com" 
        <kieran.bingham+renesas@ideasonboard.com>
Subject: RE: DRM Driver implementation question
Thread-Topic: DRM Driver implementation question
Thread-Index: AdVslX1ZBzegHzojRVS64lgG04s8jgAenS2AABbmTEA=
Date:   Tue, 17 Sep 2019 15:27:34 +0000
Message-ID: <TY2PR01MB292423C617848A66F61B1027DF8F0@TY2PR01MB2924.jpnprd01.prod.outlook.com>
References: <TY2PR01MB29242CA3B8CBE834A5B0CC48DF8C0@TY2PR01MB2924.jpnprd01.prod.outlook.com>
 <TYAPR01MB4544D0B345C809CD3555A9EFD88F0@TYAPR01MB4544.jpnprd01.prod.outlook.com>
In-Reply-To: <TYAPR01MB4544D0B345C809CD3555A9EFD88F0@TYAPR01MB4544.jpnprd01.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: renesas.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f1b30422-70c5-4c9a-4721-08d73b83906b
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Sep 2019 15:27:34.2720
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 53d82571-da19-47e4-9cb4-625a166a4a2a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4bRpjsXLmE6KLuUyVI+6lL8LOPVfSnfU8r1eOFuCs/fWbb7nJl4LfvOQk6bPoxy7nX0UzjNy3O149UTYjame7Qb3rgyAh+5plfGlVGHuyz0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY2PR01MB3916
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Yoshihiro,

This looks like an elegant solution that I can implement.
Many thanks for pointing me in a good direction.

> From: Yoshihiro Shimoda, Sent: Tuesday, September 17, 2019 05:39 PM
>=20
> Hi Gareth,
>=20
> > From: Gareth Williams, Sent: Monday, September 16, 2019 10:56 PM
> >
> > 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 w=
ould
> 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?
>=20
> I think that an MFD driver can support such hardware. I checked
> Documentation/devicetree/bindings/mfd roughly, and then atmel-hlcdc.txt
> seems to have a display controller and a PWM device.
>=20
> Best regards,
> Yoshihiro Shimoda

Best Regards,

Gareth Williams