From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <20170809014312.GZ2146@codeaurora.org> References: <20170808190818.11740-1-linus.walleij@linaro.org> <20170809014312.GZ2146@codeaurora.org> From: Linus Walleij Date: Wed, 9 Aug 2017 10:11:13 +0200 Message-ID: Subject: Re: [PATCH] clk: gemini: hands off PCI OE bit To: Stephen Boyd Cc: Michael Turquette , Philipp Zabel , linux-clk , Janos Laube , Paulius Zaleckas , "linux-arm-kernel@lists.infradead.org" , Hans Ulli Kroll , Florian Fainelli Content-Type: text/plain; charset="UTF-8" List-ID: On Wed, Aug 9, 2017 at 3:43 AM, Stephen Boyd wrote: > On 08/08, Linus Walleij wrote: >> This bit is pin control, and needs to be carefully managed by the >> new pin control driver. >> >> Signed-off-by: Linus Walleij > > Fixes tag? It's not a fix, it'd just that we move the responsibility of managing the pin from the clock driver to the pin control driver. I initially thought the Gemini would not need a separate pin control driver because it was "simple" ... so these bits could be handled here and there among the peripherals. Little did I know. Mea culpa. > Does this need to be merged now as a critical fix? Or we can wait > on it for next release? Just put it in for the next release, thanks! Yours, Linus Walleij From mboxrd@z Thu Jan 1 00:00:00 1970 From: linus.walleij@linaro.org (Linus Walleij) Date: Wed, 9 Aug 2017 10:11:13 +0200 Subject: [PATCH] clk: gemini: hands off PCI OE bit In-Reply-To: <20170809014312.GZ2146@codeaurora.org> References: <20170808190818.11740-1-linus.walleij@linaro.org> <20170809014312.GZ2146@codeaurora.org> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Aug 9, 2017 at 3:43 AM, Stephen Boyd wrote: > On 08/08, Linus Walleij wrote: >> This bit is pin control, and needs to be carefully managed by the >> new pin control driver. >> >> Signed-off-by: Linus Walleij > > Fixes tag? It's not a fix, it'd just that we move the responsibility of managing the pin from the clock driver to the pin control driver. I initially thought the Gemini would not need a separate pin control driver because it was "simple" ... so these bits could be handled here and there among the peripherals. Little did I know. Mea culpa. > Does this need to be merged now as a critical fix? Or we can wait > on it for next release? Just put it in for the next release, thanks! Yours, Linus Walleij