From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
"Gregory Clement" <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] clk: mvebu: Expand mv98dx3236-core-clock support
Date: Wed, 8 Feb 2017 20:00:15 +0000 [thread overview]
Message-ID: <aabc6853d7934507a4507b0ad4354b72@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: 9294933.cXSW0amFbE@wuerfel
On 08/02/17 23:53, Arnd Bergmann wrote:
> On Tuesday, February 7, 2017 3:07:37 AM CET Chris Packham wrote:
>>>
>>> Actually I wonder if I can try a bit harder to keep a system booting.
>>> The following might work
>>> 1) add the compatible strings to the existing armada clock drivers.
>>> 2) update the dts to use the new compatible strings.
>>> 3) add the new driver and remove the compatible strings from the armada
>>> drivers.
>>>
>>> #1 would still upset checkpatch.pl because the documentation would only
>>> arrive in #2.
>>
>> Actually upon testing #1 is unnecessary. I lose some of the gated clocks
>> but nothing that prevents booting.
>
> Just to be sure: this means we can merge 2) and 3) independently and
> having just one of them will not cause regressions over what we have
> today?
>
Correct. And that's what I sent out as v2.
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486467.html
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486471.html
WARNING: multiple messages have this Message-ID (diff)
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
Jason Cooper <jason@lakedaemon.net>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Russell King <linux@armlinux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Gregory Clement <gregory.clement@free-electrons.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 4/4] clk: mvebu: Expand mv98dx3236-core-clock support
Date: Wed, 8 Feb 2017 20:00:15 +0000 [thread overview]
Message-ID: <aabc6853d7934507a4507b0ad4354b72@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: 9294933.cXSW0amFbE@wuerfel
On 08/02/17 23:53, Arnd Bergmann wrote:
> On Tuesday, February 7, 2017 3:07:37 AM CET Chris Packham wrote:
>>>
>>> Actually I wonder if I can try a bit harder to keep a system booting.
>>> The following might work
>>> 1) add the compatible strings to the existing armada clock drivers.
>>> 2) update the dts to use the new compatible strings.
>>> 3) add the new driver and remove the compatible strings from the armada
>>> drivers.
>>>
>>> #1 would still upset checkpatch.pl because the documentation would only
>>> arrive in #2.
>>
>> Actually upon testing #1 is unnecessary. I lose some of the gated clocks
>> but nothing that prevents booting.
>
> Just to be sure: this means we can merge 2) and 3) independently and
> having just one of them will not cause regressions over what we have
> today?
>
Correct. And that's what I sent out as v2.
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486467.html
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486471.html
WARNING: multiple messages have this Message-ID (diff)
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Jason Cooper" <jason@lakedaemon.net>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] clk: mvebu: Expand mv98dx3236-core-clock support
Date: Wed, 8 Feb 2017 20:00:15 +0000 [thread overview]
Message-ID: <aabc6853d7934507a4507b0ad4354b72@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: 9294933.cXSW0amFbE@wuerfel
On 08/02/17 23:53, Arnd Bergmann wrote:=0A=
> On Tuesday, February 7, 2017 3:07:37 AM CET Chris Packham wrote:=0A=
>>>=0A=
>>> Actually I wonder if I can try a bit harder to keep a system booting.=
=0A=
>>> The following might work=0A=
>>> 1) add the compatible strings to the existing armada clock drivers.=0A=
>>> 2) update the dts to use the new compatible strings.=0A=
>>> 3) add the new driver and remove the compatible strings from the armada=
=0A=
>>> drivers.=0A=
>>>=0A=
>>> #1 would still upset checkpatch.pl because the documentation would only=
=0A=
>>> arrive in #2.=0A=
>>=0A=
>> Actually upon testing #1 is unnecessary. I lose some of the gated clocks=
=0A=
>> but nothing that prevents booting.=0A=
>=0A=
> Just to be sure: this means we can merge 2) and 3) independently and=0A=
> having just one of them will not cause regressions over what we have=0A=
> today?=0A=
>=0A=
=0A=
Correct. And that's what I sent out as v2.=0A=
=0A=
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486467.=
html=0A=
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486471.=
html=0A=
=0A=
WARNING: multiple messages have this Message-ID (diff)
From: Chris.Packham@alliedtelesis.co.nz (Chris Packham)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] clk: mvebu: Expand mv98dx3236-core-clock support
Date: Wed, 8 Feb 2017 20:00:15 +0000 [thread overview]
Message-ID: <aabc6853d7934507a4507b0ad4354b72@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: 9294933.cXSW0amFbE@wuerfel
On 08/02/17 23:53, Arnd Bergmann wrote:
> On Tuesday, February 7, 2017 3:07:37 AM CET Chris Packham wrote:
>>>
>>> Actually I wonder if I can try a bit harder to keep a system booting.
>>> The following might work
>>> 1) add the compatible strings to the existing armada clock drivers.
>>> 2) update the dts to use the new compatible strings.
>>> 3) add the new driver and remove the compatible strings from the armada
>>> drivers.
>>>
>>> #1 would still upset checkpatch.pl because the documentation would only
>>> arrive in #2.
>>
>> Actually upon testing #1 is unnecessary. I lose some of the gated clocks
>> but nothing that prevents booting.
>
> Just to be sure: this means we can merge 2) and 3) independently and
> having just one of them will not cause regressions over what we have
> today?
>
Correct. And that's what I sent out as v2.
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486467.html
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/486471.html
next prev parent reply other threads:[~2017-02-08 20:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 3:40 [PATCH 0/4] Updates for Marvell Switch SoCs Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-03 3:40 ` [PATCH 1/4] ARM: dts: armada-xp-98dx3236: combine dfx server nodes Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-03 3:40 ` [PATCH 2/4] ARM: dts: Use armada-370-xp as a base for armada-xp-98dx3236 Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-03 3:40 ` [PATCH 3/4] ARM: mvebu: Add mv98dx3236-soc-id Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-03 3:40 ` [PATCH 4/4] clk: mvebu: Expand mv98dx3236-core-clock support Chris Packham
2017-02-03 3:40 ` Chris Packham
2017-02-06 23:14 ` Stephen Boyd
2017-02-06 23:14 ` Stephen Boyd
2017-02-06 23:14 ` Stephen Boyd
2017-02-06 23:25 ` Chris Packham
2017-02-06 23:25 ` Chris Packham
2017-02-06 23:25 ` Chris Packham
2017-02-06 23:25 ` Chris Packham
2017-02-07 1:03 ` Stephen Boyd
2017-02-07 1:03 ` Stephen Boyd
2017-02-07 1:03 ` Stephen Boyd
2017-02-07 1:03 ` Stephen Boyd
2017-02-07 1:13 ` Chris Packham
2017-02-07 1:13 ` Chris Packham
2017-02-07 1:13 ` Chris Packham
2017-02-07 1:13 ` Chris Packham
2017-02-07 1:25 ` Chris Packham
2017-02-07 1:25 ` Chris Packham
2017-02-07 1:25 ` Chris Packham
2017-02-07 1:25 ` Chris Packham
2017-02-07 3:07 ` Chris Packham
2017-02-07 3:07 ` Chris Packham
2017-02-07 3:07 ` Chris Packham
2017-02-07 3:07 ` Chris Packham
2017-02-08 10:52 ` Arnd Bergmann
2017-02-08 10:52 ` Arnd Bergmann
2017-02-08 10:52 ` Arnd Bergmann
2017-02-08 20:00 ` Chris Packham [this message]
2017-02-08 20:00 ` Chris Packham
2017-02-08 20:00 ` Chris Packham
2017-02-08 20:00 ` Chris Packham
2017-02-10 17:21 ` Stephen Boyd
2017-02-10 17:21 ` Stephen Boyd
2017-02-10 17:21 ` 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=aabc6853d7934507a4507b0ad4354b72@svr-chch-ex1.atlnz.lc \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sebastian.hesselbarth@gmail.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.