[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2y3vn6dhk.fsf@baylibre.com>
Date: Wed, 29 Mar 2017 13:21:11 -0700
From: Kevin Hilman <khilman@...libre.com>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: Jerome Brunet <jbrunet@...libre.com>,
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
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.
Kevin
Powered by blists - more mailing lists