From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anup Patel <anup.patel@linaro.org>,
patches@linaro.org, patches@apm.com, xen-devel@lists.xen.org,
stefano.stabellini@citrix.com,
Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Subject: Re: [PATCH V6] xen: arm: platforms: Adding reset support for xgene arm64 platform.
Date: Mon, 27 Jan 2014 12:07:21 +0000 [thread overview]
Message-ID: <52E64BF9.8080608@eu.citrix.com> (raw)
In-Reply-To: <1390824259.12230.26.camel@kazak.uk.xensource.com>
On 01/27/2014 12:04 PM, Ian Campbell wrote:
> On Mon, 2014-01-27 at 12:01 +0000, George Dunlap wrote:
>> On 01/27/2014 11:38 AM, Ian Campbell wrote:
>>> On Mon, 2014-01-27 at 17:04 +0530, Pranavkumar Sawargaonkar wrote:
>>>> This patch adds a reset support for xgene arm64 platform.
>>>>
>>>> V6:
>>>> - Incorporating comments received on V5 patch.
>>>> V5:
>>>> - Incorporating comments received on V4 patch.
>>>> V4:
>>>> - Removing TODO comment about retriving reset base address from dts
>>>> as that is done now.
>>>> V3:
>>>> - Retriving reset base address and reset mask from device tree.
>>>> - Removed unnecssary header files included earlier.
>>>> V2:
>>>> - Removed unnecssary mdelay in code.
>>>> - Adding iounmap of the base address.
>>>> V1:
>>>> -Initial patch.
>>>>
>>>> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
>>>> Signed-off-by: Anup Patel <anup.patel@linaro.org>
>>> Looks good, thanks:
>>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>>>
>>> George, I'd like to put this in 4.4. The impact on non-xgene is non
>>> existent and I think reset is basic functionality which we should
>>> enable.
>> So without this patch, support for xgene would be considered
>> "experimental" (missing basic functionality)?
> I don't think I would go so far as to say "experimental", we could
> probably live with it, but having to go find the board and press the
> tiny little button to reboot it is certainly not "complete".
Yes, "can't reboot via software" is a pretty big lack of functionality;
it weighs in pretty heavily against whatever potential regressions might
be introduced.
Release-acked-by: George Dunlap <george.dunlap@eu.citrix.com>
next prev parent reply other threads:[~2014-01-27 12:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 11:34 [PATCH V6] xen: arm: platforms: Adding reset support for xgene arm64 platform Pranavkumar Sawargaonkar
2014-01-27 11:38 ` Ian Campbell
2014-01-27 12:01 ` George Dunlap
2014-01-27 12:04 ` Ian Campbell
2014-01-27 12:07 ` George Dunlap [this message]
2014-01-28 11:49 ` Ian Campbell
2014-01-27 13:36 ` Julien Grall
2014-01-27 14:13 ` Ian Campbell
2014-01-27 14:24 ` Julien Grall
2014-01-27 14:27 ` Ian Campbell
2014-01-27 14:36 ` Julien Grall
2014-01-27 14:39 ` Ian Campbell
2014-01-28 15:47 ` Ian Campbell
2014-01-28 17:35 ` Pranavkumar Sawargaonkar
2014-01-28 17:43 ` Ian Campbell
2014-01-28 17:57 ` Pranavkumar Sawargaonkar
2014-01-29 12:38 ` Ian Campbell
2014-01-30 6:08 ` Pranavkumar Sawargaonkar
2014-02-03 17:04 ` Ian Campbell
2014-02-03 17:25 ` Pranavkumar Sawargaonkar
2014-02-05 14:48 ` George Dunlap
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=52E64BF9.8080608@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=anup.patel@linaro.org \
--cc=patches@apm.com \
--cc=patches@linaro.org \
--cc=pranavkumar@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.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).