From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: From: Kevin Hilman To: Martin Blumenstingl Cc: Jerome Brunet , Helmut Klein , mturquette@baylibre.com, sboyd@codeaurora.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org Subject: Re: [PATCH v2,1/3] meson_uart: expose CLKID_UARTx References: <20170328092545.4644-1-hgkr.klein@gmail.com> <20170328092545.4644-2-hgkr.klein@gmail.com> <1490716277.20764.6.camel@baylibre.com> <71489b62-78c8-7082-587e-8598dc43ca59@gmail.com> <1490728490.20764.8.camel@baylibre.com> Date: Wed, 29 Mar 2017 13:21:11 -0700 In-Reply-To: (Martin Blumenstingl's message of "Tue, 28 Mar 2017 23:24:15 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain List-ID: Martin Blumenstingl 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