[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190221201346.wbyfhmtmgyoii3wt@pengutronix.de>
Date: Thu, 21 Feb 2019 21:13:46 +0100
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Claudiu.Beznea@...rochip.com
Cc: thierry.reding@...il.com, robh+dt@...nel.org, mark.rutland@....com,
Nicolas.Ferre@...rochip.com, alexandre.belloni@...tlin.com,
Ludovic.Desroches@...rochip.com,
linux-arm-kernel@...ts.infradead.org, linux-pwm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/4] pwm: atmel: add struct atmel_pwm_data
On Tue, Feb 19, 2019 at 10:08:53AM +0000, Claudiu.Beznea@...rochip.com wrote:
> From: Claudiu Beznea <claudiu.beznea@...rochip.com>
>
> Add struct atmel_pwm_data to embed different per controller information. At
> this stage, embed a member of type struct atmel_pwm_registers in it.
I'd write:
Introduce a new structure to describe per controller
information. For now it contains only a struct
atmel_pwm_registers member which up to now is enough to describe
the relevant differences and was used directly as driver data
before.
This prepares adding support for another similar controller that
needs additional information.
Other than that
Acked-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Powered by blists - more mailing lists