From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-clk <linux-clk@vger.kernel.org>,
Janos Laube <janos.dev@gmail.com>,
Paulius Zaleckas <paulius.zaleckas@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH] clk: gemini: hands off PCI OE bit
Date: Wed, 9 Aug 2017 10:11:13 +0200 [thread overview]
Message-ID: <CACRpkda0cLMuiipEBX+mH6MJ3v6k=CY+q=Q6NUj=BM+6wnFO2A@mail.gmail.com> (raw)
In-Reply-To: <20170809014312.GZ2146@codeaurora.org>
On Wed, Aug 9, 2017 at 3:43 AM, Stephen Boyd <sboyd@codeaurora.org> 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 <linus.walleij@linaro.org>
>
> 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
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: gemini: hands off PCI OE bit
Date: Wed, 9 Aug 2017 10:11:13 +0200 [thread overview]
Message-ID: <CACRpkda0cLMuiipEBX+mH6MJ3v6k=CY+q=Q6NUj=BM+6wnFO2A@mail.gmail.com> (raw)
In-Reply-To: <20170809014312.GZ2146@codeaurora.org>
On Wed, Aug 9, 2017 at 3:43 AM, Stephen Boyd <sboyd@codeaurora.org> 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 <linus.walleij@linaro.org>
>
> 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
next prev parent reply other threads:[~2017-08-09 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 19:08 [PATCH] clk: gemini: hands off PCI OE bit Linus Walleij
2017-08-08 19:08 ` Linus Walleij
2017-08-09 1:43 ` Stephen Boyd
2017-08-09 1:43 ` Stephen Boyd
2017-08-09 8:11 ` Linus Walleij [this message]
2017-08-09 8:11 ` Linus Walleij
2017-08-09 17:23 ` Stephen Boyd
2017-08-09 17:23 ` Stephen Boyd
2017-08-28 16:47 ` Linus Walleij
2017-08-28 16:47 ` Linus Walleij
2017-08-31 5:29 ` Stephen Boyd
2017-08-31 5:29 ` Stephen Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACRpkda0cLMuiipEBX+mH6MJ3v6k=CY+q=Q6NUj=BM+6wnFO2A@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=janos.dev@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=paulius.zaleckas@gmail.com \
--cc=sboyd@codeaurora.org \
--cc=ulli.kroll@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.