linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@codeaurora.org>
To: 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>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.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: Wed, 22 Mar 2017 15:49:21 -0400	[thread overview]
Message-ID: <704b8b8c-e607-29b3-e101-bbecd90073bb@codeaurora.org> (raw)
In-Reply-To: <CAKv+Gu8Uw-X3AR6aQYevPdRfcgPNnqL4O3sRoKxsZAiW29sbqg@mail.gmail.com>

On 3/22/2017 3:41 PM, Ard Biesheuvel wrote:
>> As far as I know, kernel honors resource assignments done by the UEFI BIOS if
>> they are correct. Kernel will reassign the resources only if something is wrong.
>>
> No, the kernel always reassigns all BARs on arm64.

I think this is where the problem is.

I'm not seeing this happen on QDF2400 which supports ACPI + UEFI BIOS
combination only. 

I see that kernel honored the resources assigned by UEFI BIOS if I compare
the BAR addresses.

I see reassignment only when something is horribly broken. Then, there would
be a bridge configuration invalid message in the boot log to confirm this.

> 
>> Will this code break other platforms/architectures?
>>
> Which platforms/architectures are you referring to? EFIFB on a PCI
> device is currently broken on arm64. 

In general or on your particular platform?

> On x86, it works, given that BARs
> are usually not reassigned, and so the patch should be a no-op in that
> case (although I'd argue it is still an improvement to check whether
> the device that owns the BAR actually has memory decoding enabled
> before we attach the framebuffer driver to it)
> 

I'm fine as long as it doesn't break anything. That's why, I'm asking.

-- 
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

  reply	other threads:[~2017-03-22 19:49 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
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 [this message]
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=704b8b8c-e607-29b3-e101-bbecd90073bb@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).