[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1490974657.12951.5.camel@baylibre.com>
Date: Fri, 31 Mar 2017 17:37:37 +0200
From: Jerome Brunet <jbrunet@...libre.com>
To: Kevin Hilman <khilman@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: Helmut Klein <hgkr.klein@...il.com>, mturquette@...libre.com,
sboyd@...eaurora.org, devicetree@...r.kernel.org,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org
Subject: Re: [PATCH v2,1/3] meson_uart: expose CLKID_UARTx
On Wed, 2017-03-29 at 13:21 -0700, Kevin Hilman wrote:
> Martin Blumenstingl <martin.blumenstingl@...glemail.com> writes:
>
> [...]
>
> > for Helmut this would mean that instead of dropping this patch (or
> > dropping CLKID_UART1 and CLKID_UART2 from this patch) he would rather
> > have to *add* another patch (for meson-gxbb.dtsi and meson-gxl.dtsi)
> > which passes the core clocks to the corresponding UART controllers
> > (similar to the CLKID_SD_EMMC_ clocks).
>
> Yes, this is what I would like to see.
>
> If a new CLKID is exposed, I want to see the users of it at the same
> time.
Helmut,
If you send another version of these patches, considering the feedback of Kevin
and Martin, could you please change the subject of this patch to:
dt-bindings: clock: gxbb: expose UART clocks
Thx
Jerome
>
> Kevin
Powered by blists - more mailing lists