From: Joel Stanley <joel@jms.id.au>
To: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Jeffery <andrew@aj.id.au>, Cyril Bur <cyrilbur@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Lei YU <mine260309@gmail.com>
Subject: [PATCH 0/3] misc: aspeed-lpc-ctrl fixes
Date: Mon, 12 Feb 2018 17:38:44 +1030 [thread overview]
Message-ID: <20180212070847.32387-1-joel@jms.id.au> (raw)
These patches were developed when testing upstream Linux with OpenBMC on
Romulus. We need to ensure the LPC clock is enabled, now that the clock
driver turns off any unused clocks. We also need to enable the LPC
firmware cycles bit as we do not intend to upstream any mach-aspeed
hacks.
There was no existing binding document for the LPC host interface
controller, so I wrote one that includes the required clock description.
Joel Stanley (3):
dt-bindings: aspeed-lpc: Document LPC Host Interface Controller
misc: aspeed-lpc: Request and enable LPC clock
misc: aspeed-lpc-ctrl: Enable FWH and A2H bridge cycles
.../devicetree/bindings/mfd/aspeed-lpc.txt | 40 ++++++++++++++++++++
drivers/misc/aspeed-lpc-ctrl.c | 44 +++++++++++++++++++---
2 files changed, 79 insertions(+), 5 deletions(-)
--
2.15.1
next reply other threads:[~2018-02-12 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 7:08 Joel Stanley [this message]
2018-02-12 7:08 ` [PATCH 1/3] dt-bindings: aspeed-lpc: Document LPC Host Interface Controller Joel Stanley
2018-02-16 5:04 ` Andrew Jeffery
2018-02-19 0:10 ` Rob Herring
2018-02-12 7:08 ` [PATCH 2/3] misc: aspeed-lpc: Request and enable LPC clock Joel Stanley
2018-02-12 7:08 ` [PATCH 3/3] misc: aspeed-lpc-ctrl: Enable FWH and A2H bridge cycles Joel Stanley
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=20180212070847.32387-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=cyrilbur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mine260309@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryan_chen@aspeedtech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®