From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Ben Whitten <ben.whitten@gmail.com>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
nicolas.ferre@microchip.com,
Ben Whitten <ben.whitten@lairdtech.com>
Subject: Re: [PATCH v2 4/6] arm: dts: add support for Laird WB50N cpu module and DVK
Date: Thu, 12 Jul 2018 23:54:35 +0200 [thread overview]
Message-ID: <20180712215435.GL16084@piout.net> (raw)
In-Reply-To: <1529070055-18701-4-git-send-email-ben.whitten@lairdtech.com>
Hi,
I've now applied the whole series after fixing two small whitespace
issues.
On 15/06/2018 14:40:53+0100, Ben Whitten wrote:
> +&usart1_clk {
> + atmel,clk-output-range = <0 132000000>;
> +};
> +
But this is not actually allowed by the hardware (well, it is but it
will lead to issues) and will be removed once the clock binding is
reworked.
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-12 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 13:40 [PATCH v2 1/6] dt-bindings: add laird and giantec vendor prefix Ben Whitten
2018-06-15 13:40 ` [PATCH v2 2/6] arm: dts: at91: add labels to soc dtsi for derivative boards Ben Whitten
2018-06-15 13:40 ` [PATCH v2 3/6] arm: dts: add support for Laird WB45N cpu module and DVK Ben Whitten
2018-06-15 13:40 ` [PATCH v2 4/6] arm: dts: add support for Laird WB50N " Ben Whitten
2018-06-27 8:42 ` Ben Whitten
2018-06-27 8:48 ` Alexandre Belloni
2018-07-12 21:54 ` Alexandre Belloni [this message]
2018-07-13 8:37 ` Ben Whitten
2018-06-15 13:40 ` [PATCH v2 5/6] arm: dts: add support for Gatwick board based on WB50N Ben Whitten
2018-06-15 13:40 ` [PATCH v2 6/6] arm: dts: add support for Laird SOM60 module and DVK boards Ben Whitten
2018-06-20 19:35 ` [PATCH v2 1/6] dt-bindings: add laird and giantec vendor prefix Rob Herring
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=20180712215435.GL16084@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=ben.whitten@gmail.com \
--cc=ben.whitten@lairdtech.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.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).