[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGCh1+=wYJbP4OS1W-2CJDRWNHStKNG1M8Y=iUM3rffO4JrqGA@mail.gmail.com>
Date: Sat, 5 Aug 2017 08:25:16 +0100
From: Graeme Gregory <graeme.gregory@...aro.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <lenb@...nel.org>, Loc Ho <lho@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jon Masters <jcm@...hat.com>
Subject: Re: [PATCH 0/2] Updated SPCR quirks for Moonshot/Mustang
On 4 August 2017 at 23:51, Rafael J. Wysocki <rafael@...nel.org> wrote:
> On Fri, Aug 4, 2017 at 11:49 PM, Graeme Gregory
> <graeme.gregory@...aro.org> wrote:
>> A couple of patches to build on the SPCR quirks support already upstreamed.
>>
>> 1 - Moonshot m400 cartridge has the same soc but ACPI tables have different
>> HPe specific headers so extend quirk to understand those too.
>>
>> 2 - Relevant vendors do not seem to be working on DBG2/SPCR update for
>> situation where the clock is unknown. We want these machines to boot with
>> console initialised from SPCR before I die of old age so use the previous
>> quirk handling to also handle the clock problem as well.
>
> It increasingly seems to me that spcr.c firmly belongs in
> drivers/acpi/arm64/. Any chance to move it in there and then mess up
> with it further?
>
Apparently x86 machines exist with SPCR table.
But if that is your wish I can certainly add that to series.
Graeme
Powered by blists - more mailing lists