linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: fabrice.gasnier@st.com (Fabrice Gasnier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v1 1/3] PCI: designware: Add ARM64 support
Date: Mon, 25 May 2015 17:51:55 +0200	[thread overview]
Message-ID: <5563451B.4050609@st.com> (raw)
In-Reply-To: <000001d096f1$93dca4e0$bb95eea0$@com>

Hi Zhou,

On 05/25/2015 03:48 PM, Jingoo Han wrote:
>> >so how about we set 0 as default value of pp->root_bus_nr, then use
>> >pci_create_root_bus(pp->dev, pp->root_bus_nr, &dw_pcie_ops, pp, &res);
>> >to create root bus?
> I agree with your opinion. However, I still want to wait for other
> people's opinions. They will give good comments.
> Thank you.
>
> Best regards,
> Jingoo Han
>
I did a quick test with your patch in the context of another driver on 
arm32.
Just to confirm I added as well pp->root_bus_nr = 0;

Then, I needed to add dummy pci_sys_data as suggested by Arnd in the 
first review :
http://www.spinics.net/lists/linux-pci/msg40445.html

  struct pcie_port {
+#ifdef CONFIG_ARM
+	/*
+	 * this is a temporary hack to let the driver work on
+	 * both arm32 and arm64. it can be removed after the
+	 * arm32 cleanup is complete and bios32.c has stopped
+	 * referencing host->pci_sys_data.
+	 */
+	struct pci_sys_data	dummy;
+#endif
  	struct device		*dev;


This looks like necessary as bios32 is dereferencing sysdata:
struct pci_sys_data *sysdata = dev->bus->sysdata;

Best Regards,
Fabrice

  reply	other threads:[~2015-05-25 15:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000001d096a9$27bf43f0$773dcbd0$@com>
2015-05-25  9:52 ` [RFC PATCH v1 1/3] PCI: designware: Add ARM64 support Zhou Wang
2015-05-25 13:48   ` Jingoo Han
2015-05-25 15:51     ` Fabrice Gasnier [this message]
2015-05-26  2:49       ` Zhou Wang
2015-05-26  8:02         ` Arnd Bergmann
2015-05-27 13:56           ` Zhou Wang
2015-05-27 15:31             ` Arnd Bergmann
2015-05-27 15:43               ` Arnd Bergmann
2015-05-27 16:19                 ` Fabrice Gasnier
2015-05-27 19:51                   ` Arnd Bergmann
2015-05-28 11:48                     ` Zhou Wang
2015-05-28 12:25                       ` Arnd Bergmann
2015-05-28 11:40                   ` Zhou Wang
2015-05-28 11:34                 ` Zhou Wang
2015-05-28 12:30                   ` Arnd Bergmann
2015-05-26  8:03         ` Fabrice Gasnier
2015-05-27 13:24           ` Zhou Wang
2015-05-27 13:52             ` Fabrice Gasnier
2015-05-26  2:04     ` Zhou Wang
2015-05-26  8:09 ` Arnd Bergmann
2015-05-27 13:28   ` Zhou Wang
2015-05-20  6:21 [RFC PATCH v1 0/3] PCI: hisi: Add PCIe host support for Hisilicon Soc Hip05 Zhou Wang
2015-05-20  6:21 ` [RFC PATCH v1 1/3] PCI: designware: Add ARM64 support Zhou Wang
2015-05-25  1:33   ` Zhou Wang

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=5563451B.4050609@st.com \
    --to=fabrice.gasnier@st.com \
    --cc=linux-arm-kernel@lists.infradead.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).