From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] MIPS: BCM63XX: add and use clkdev lookup support
Date: Tue, 15 Aug 2017 09:20:00 -0700 [thread overview]
Message-ID: <b180fcb8-0282-3bad-aad0-4f1faaea73b0@gmail.com> (raw)
In-Reply-To: <20170802093429.12572-1-jonas.gorski@gmail.com>
On 08/02/2017 02:34 AM, Jonas Gorski wrote:
> This patchset adds and uses clckdev lookup support to name input clocks
> in various drivers more closely to their functions, or simplify their
> usage.
>
> Since most of these patches touch arch/mips, it probably makes most
> sense to go through the MIPS tree.
>
> The HSSPI driver was already updated previously to support a "pll"
> input with ff18e1ef04e2 ("spi/bcm63xx-hsspi: allow providing clock rate
> through a second clock"), so there is no need to touch it.
>
> This patch series is part of an effort to modernize BCM63XX and clean up
> its drivers to eventually make them usable with BMIPS and device tree.
For this entire series:
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Thanks!
>
> Jonas Gorski (8):
> MIPS: BCM63XX: add clkdev lookup support
> MIPS: BCM63XX: provide periph clock as refclk for uart
> tty/bcm63xx_uart: use refclk for the expected clock name
> tty/bcm63xx_uart: allow naming clock in device tree
> MIPS: BCM63XX: provide enet clocks as "enet" to the ethernet devices
> bcm63xx_enet: just use "enet" as the clock name
> MIPS: BCM63XX: move the HSSPI PLL HZ into its own clock
> MIPS: BMIPS: name the refclk clock for uart
>
> .../bindings/serial/brcm,bcm6345-uart.txt | 6 +
> arch/mips/Kconfig | 1 +
> arch/mips/bcm63xx/clk.c | 181 ++++++++++++++++-----
> arch/mips/boot/dts/brcm/bcm3368.dtsi | 2 +
> arch/mips/boot/dts/brcm/bcm63268.dtsi | 2 +
> arch/mips/boot/dts/brcm/bcm6328.dtsi | 2 +
> arch/mips/boot/dts/brcm/bcm6358.dtsi | 2 +
> arch/mips/boot/dts/brcm/bcm6362.dtsi | 2 +
> arch/mips/boot/dts/brcm/bcm6368.dtsi | 2 +
> drivers/net/ethernet/broadcom/bcm63xx_enet.c | 5 +-
> drivers/tty/serial/bcm63xx_uart.c | 6 +-
> 11 files changed, 168 insertions(+), 43 deletions(-)
>
--
Florian
prev parent reply other threads:[~2017-08-15 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 9:34 [PATCH 0/8] MIPS: BCM63XX: add and use clkdev lookup support Jonas Gorski
2017-08-02 9:34 ` [PATCH 1/8] MIPS: BCM63XX: add " Jonas Gorski
2017-08-02 9:34 ` [PATCH 2/8] MIPS: BCM63XX: provide periph clock as refclk for uart Jonas Gorski
2017-08-02 9:34 ` [PATCH 3/8] tty/bcm63xx_uart: use refclk for the expected clock name Jonas Gorski
2017-08-28 12:51 ` Greg Kroah-Hartman
2017-08-02 9:34 ` [PATCH 4/8] tty/bcm63xx_uart: allow naming clock in device tree Jonas Gorski
2017-08-10 16:25 ` Rob Herring
2017-09-06 11:01 ` Jonas Gorski
2017-09-06 12:17 ` Greg Kroah-Hartman
2017-09-06 12:37 ` Jonas Gorski
2017-08-02 9:34 ` [PATCH 5/8] MIPS: BCM63XX: provide enet clocks as "enet" to the ethernet devices Jonas Gorski
2017-08-02 9:34 ` [PATCH 6/8] bcm63xx_enet: just use "enet" as the clock name Jonas Gorski
2017-09-06 11:00 ` Jonas Gorski
2017-08-02 9:34 ` [PATCH 7/8] MIPS: BCM63XX: move the HSSPI PLL HZ into its own clock Jonas Gorski
2017-08-02 9:34 ` [PATCH 8/8] MIPS: BMIPS: name the refclk clock for uart Jonas Gorski
2017-08-15 16:20 ` Florian Fainelli [this message]
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=b180fcb8-0282-3bad-aad0-4f1faaea73b0@gmail.com \
--to=f.fainelli@gmail.com \
--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).