Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1444611

Re: Memory and IO space Enabling different in x86 and ARM64

Show all headers | View raw

On Fri, Jul 15, 2016 at 08:29:49AM +0000, Bharat Kumar Gogada wrote:
> Hi,
> 
> I observe that memory and IO space are enabled by BIOS in x86.
> 
> In ARM64 we need to call pci_enable_device form End Point to enable these resources.
> 
> Why the resource enablement is different in x86 and ARM64 ?

A portable driver should call pci_enable_device() if it needs access
to any BARs.  As you've observed, the command register enable bits may
be set differently on different architectures, and the PCI core
doesn't set them automatically for you, so the driver can't rely on
their initial settings.

One reason why Linux doesn't enable them automatically before calling
the driver's probe method is that it may not be possible to allocate
space for all the BARs (e.g., if the platform doesn't support I/O port
space, or if we just run out of space), but the driver may be able to
operate the device even without all the BARs.

Bjorn

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Memory and IO space Enabling different in x86 and ARM64 Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com> - 2016-07-15 10:40 +0200
  Re: Memory and IO space Enabling different in x86 and ARM64 Arnd Bergmann <arnd@arndb.de> - 2016-07-15 10:40 +0200
  Re: Memory and IO space Enabling different in x86 and ARM64 Bjorn Helgaas <helgaas@kernel.org> - 2016-07-15 23:50 +0200
    RE: Memory and IO space Enabling different in x86 and ARM64 Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com> - 2016-07-16 05:30 +0200

csiph-web