[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo6xRdwzTuPPqnmvmHSp7awnV7=Z85eWFfktb_hm9Aad_A@mail.gmail.com>
Date: Thu, 6 Dec 2012 14:27:06 -0700
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Michal Simek <michal.simek@...inx.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
linux-arm <linux-arm-kernel@...ts.infradead.org>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
linux-arch@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
Grant Likely <grant.likely@...retlab.ca>,
John Linn <John.Linn@...inx.com>,
John Williams <jwilliams@...inx.com>, linux-pci@...r.kernel.org
Subject: Re: Sharing PCIE driver between Microblaze and Arm zynq
[+cc linux-pci]
On Thu, Dec 6, 2012 at 7:23 AM, Michal Simek <michal.simek@...inx.com> wrote:
> Hi guys,
>
> I have a question regarding to sharing generic OF pcie driver between
> two architectures MB and ARM Zynq.
> Is drivers/pci/pcie location good for it?
> Make no sense to have the same driver in two locations.
I think you're talking about a PCI host bridge driver. It would
definitely be nice to move toward a generic, shared driver. Host
bridge drivers are responsible for enumerating the PCI hierarchy below
the bridge. Enumeration is not really PCIe-specific, so I wouldn't
put it in drivers/pci/pcie.
> Is using readl/writel IO functions in this driver the best option
> which we can have?
> Or is there any other recommendation?
I'm not really a driver person, but if you're writing a new driver,
wouldn't you use the iomap interfaces (ioremap(), ioread32(), etc)
rather than readl()?
> Also just want to check if it is correct to use pcie device_type.
I don't know what you're asking here. Can you elaborate or give a
specific example?
> The rest should be the same with pci description:
> (http://devicetree.org/MPC5200:PCI#PCI_Address_Translation).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists