All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic <linux-amlogic@lists.infradead.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: meson: Switch simple-mfd and syscon order
Date: Thu, 13 Sep 2018 09:04:45 +0200	[thread overview]
Message-ID: <fa3fd18a-88a0-7dbf-c5dd-441cfad5459a@baylibre.com> (raw)
In-Reply-To: <CAOi56cVESykxXg4zcdLh89Rpyiyg587XCkvFG55FnMSro4vH2w@mail.gmail.com>

Hi Kevin,

On 13/09/2018 06:20, Kevin Hilman wrote:
> On Wed, Sep 12, 2018 at 8:59 PM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Neil Armstrong <narmstrong@baylibre.com> writes:
>>
>>> The order between "syscon" and "simple-mfd" is important because in these
>>> particular cases, the node needs to be first a "simple-mfd" to expose
>>> it's sub-nodes, and later on a "syscon" to permit other nodes to access
>>> this register space through the "syscon" mechanism.
>>>
>>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>>
>> Applied to v4.20/dt64,
>>
> 
> I spoke too soon, this doesn't apply cleanly on top of Jeromes
> reorder/cleanup.  Please respin/resend.

I'll respin.

Neil

> 
> Kevin
> 


WARNING: multiple messages have this Message-ID (diff)
From: narmstrong@baylibre.com (Neil Armstrong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: meson: Switch simple-mfd and syscon order
Date: Thu, 13 Sep 2018 09:04:45 +0200	[thread overview]
Message-ID: <fa3fd18a-88a0-7dbf-c5dd-441cfad5459a@baylibre.com> (raw)
In-Reply-To: <CAOi56cVESykxXg4zcdLh89Rpyiyg587XCkvFG55FnMSro4vH2w@mail.gmail.com>

Hi Kevin,

On 13/09/2018 06:20, Kevin Hilman wrote:
> On Wed, Sep 12, 2018 at 8:59 PM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Neil Armstrong <narmstrong@baylibre.com> writes:
>>
>>> The order between "syscon" and "simple-mfd" is important because in these
>>> particular cases, the node needs to be first a "simple-mfd" to expose
>>> it's sub-nodes, and later on a "syscon" to permit other nodes to access
>>> this register space through the "syscon" mechanism.
>>>
>>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>>
>> Applied to v4.20/dt64,
>>
> 
> I spoke too soon, this doesn't apply cleanly on top of Jeromes
> reorder/cleanup.  Please respin/resend.

I'll respin.

Neil

> 
> Kevin
> 

WARNING: multiple messages have this Message-ID (diff)
From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] arm64: dts: meson: Switch simple-mfd and syscon order
Date: Thu, 13 Sep 2018 09:04:45 +0200	[thread overview]
Message-ID: <fa3fd18a-88a0-7dbf-c5dd-441cfad5459a@baylibre.com> (raw)
In-Reply-To: <CAOi56cVESykxXg4zcdLh89Rpyiyg587XCkvFG55FnMSro4vH2w@mail.gmail.com>

Hi Kevin,

On 13/09/2018 06:20, Kevin Hilman wrote:
> On Wed, Sep 12, 2018 at 8:59 PM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Neil Armstrong <narmstrong@baylibre.com> writes:
>>
>>> The order between "syscon" and "simple-mfd" is important because in these
>>> particular cases, the node needs to be first a "simple-mfd" to expose
>>> it's sub-nodes, and later on a "syscon" to permit other nodes to access
>>> this register space through the "syscon" mechanism.
>>>
>>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>>
>> Applied to v4.20/dt64,
>>
> 
> I spoke too soon, this doesn't apply cleanly on top of Jeromes
> reorder/cleanup.  Please respin/resend.

I'll respin.

Neil

> 
> Kevin
> 

  reply	other threads:[~2018-09-13  7:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 14:13 [PATCH] arm64: dts: meson: Switch simple-mfd and syscon order Neil Armstrong
2018-07-26 14:13 ` Neil Armstrong
2018-07-26 14:13 ` Neil Armstrong
2018-07-26 14:41 ` Yixun Lan
2018-07-26 14:41   ` Yixun Lan
2018-07-26 14:41   ` Yixun Lan
2018-07-26 14:50   ` Neil Armstrong
2018-07-26 14:50     ` Neil Armstrong
2018-07-26 14:50     ` Neil Armstrong
2018-09-13  4:07     ` Chen-Yu Tsai
2018-09-13  4:07       ` Chen-Yu Tsai
2018-09-13  4:07       ` Chen-Yu Tsai
2018-07-27  6:03 ` Lee Jones
2018-07-27  6:03   ` Lee Jones
2018-07-27  6:03   ` Lee Jones
2018-09-13  3:59 ` Kevin Hilman
2018-09-13  3:59   ` Kevin Hilman
2018-09-13  3:59   ` Kevin Hilman
2018-09-13  4:20   ` Kevin Hilman
2018-09-13  4:20     ` Kevin Hilman
2018-09-13  4:20     ` Kevin Hilman
2018-09-13  7:04     ` Neil Armstrong [this message]
2018-09-13  7:04       ` Neil Armstrong
2018-09-13  7:04       ` Neil Armstrong

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=fa3fd18a-88a0-7dbf-c5dd-441cfad5459a@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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 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.