From: Sinan Kaya <okaya@codeaurora.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
linux-pci <linux-pci@vger.kernel.org>,
Peter Jones <pjones@redhat.com>, Heyi Guo <heyi.guo@linaro.org>,
Lukas Wunner <lukas@wunner.de>,
Hanjun Guo <hanjun.guo@linaro.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] efifb: avoid reconfiguration of BAR that covers the framebuffer
Date: Mon, 10 Apr 2017 13:06:40 -0400 [thread overview]
Message-ID: <a92d4d6a-0d94-350e-a0dd-55516fbc8ab7@codeaurora.org> (raw)
In-Reply-To: <20170410165328.GA5248@red-moon>
On 4/10/2017 12:53 PM, Lorenzo Pieralisi wrote:
> Do we want to enforce it on ARM ? I do not know to be honest (and it
> still would not solve the DT firmware case).
>
Yes for ACPI on ARM. Probably no for DT.
> Whatever we do, it is not going to be clean cut IMO. I think that
> what x86 does is sensible (well, minus the link ordering dependency we
> discovered), I can do it for ARM64 but get ready for regressions and
> I still think we have no real FW binding support that would make this
> behaviour robust.
Is it possible to move the code from arch/x86 into drivers/acpi directory
so that the code is shared across multiple ACPI based archs. We get more
coverage this way.
Can we fallback to the allocate everything behavior if we can't use the
stuff from FW or would it be too late to recover?
We can prevent regressions this way and issue a lot of warnings. We can
sit down and fix those warnings over time whether the issue is in
UEFI BIOS or the code itself.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-04-10 17:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 15:30 [PATCH v3] efifb: avoid reconfiguration of BAR that covers the framebuffer Ard Biesheuvel
2017-03-22 19:31 ` Lukas Wunner
2017-03-22 19:32 ` Ard Biesheuvel
2017-03-23 8:48 ` Lukas Wunner
2017-03-23 9:04 ` Ard Biesheuvel
2017-03-23 10:57 ` Lorenzo Pieralisi
2017-03-23 12:25 ` Ard Biesheuvel
2017-03-23 14:31 ` Lorenzo Pieralisi
2017-03-23 15:15 ` Ard Biesheuvel
2017-03-27 15:37 ` Ard Biesheuvel
2017-03-28 21:27 ` Sinan Kaya
2017-03-28 21:39 ` Ard Biesheuvel
2017-03-28 21:49 ` Sinan Kaya
2017-03-30 8:46 ` Ard Biesheuvel
2017-03-30 10:05 ` Lorenzo Pieralisi
2017-03-30 10:09 ` Ard Biesheuvel
2017-03-30 11:42 ` okaya
2017-03-30 13:38 ` Ard Biesheuvel
2017-03-30 13:50 ` Sinan Kaya
2017-04-02 15:16 ` Ard Biesheuvel
2017-04-10 15:28 ` Ard Biesheuvel
2017-04-10 16:53 ` Lorenzo Pieralisi
2017-04-10 17:06 ` Sinan Kaya [this message]
2017-04-10 17:13 ` Ard Biesheuvel
2017-04-10 17:29 ` Ard Biesheuvel
2017-04-11 13:16 ` Lorenzo Pieralisi
2017-04-11 16:06 ` Ard Biesheuvel
2017-04-23 1:45 ` Yinghai Lu
2017-04-27 13:55 ` Ard Biesheuvel
2017-04-28 20:51 ` Yinghai Lu
2017-03-22 19:36 ` Sinan Kaya
2017-03-22 19:41 ` Ard Biesheuvel
2017-03-22 19:49 ` Sinan Kaya
2017-03-22 19:52 ` Ard Biesheuvel
2017-03-22 19:57 ` Sinan Kaya
2017-03-22 20:00 ` Ard Biesheuvel
2017-05-03 3:09 ` Heyi Guo
2017-05-18 14:01 ` Bjorn Helgaas
2017-05-20 8:19 ` Heyi Guo
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=a92d4d6a-0d94-350e-a0dd-55516fbc8ab7@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--cc=hanjun.guo@linaro.org \
--cc=heyi.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukas@wunner.de \
--cc=matt@codeblueprint.co.uk \
--cc=pjones@redhat.com \
--cc=yinghai@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).