From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: gemini: hands off PCI OE bit
Date: Wed, 9 Aug 2017 10:23:08 -0700 [thread overview]
Message-ID: <20170809172308.GC2146@codeaurora.org> (raw)
In-Reply-To: <CACRpkda0cLMuiipEBX+mH6MJ3v6k=CY+q=Q6NUj=BM+6wnFO2A@mail.gmail.com>
On 08/09, Linus Walleij wrote:
> 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!
>
Alright. Thanks!
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-08-09 17:23 UTC|newest]
Thread overview: 6+ 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-09 1:43 ` Stephen Boyd
2017-08-09 8:11 ` Linus Walleij
2017-08-09 17:23 ` Stephen Boyd [this message]
2017-08-28 16:47 ` Linus Walleij
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=20170809172308.GC2146@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).