[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151022184622.GD21237@localhost>
Date: Thu, 22 Oct 2015 13:46:22 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Zhou Wang <wangzhou1@...ilicon.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, jingoohan1@...il.com,
pratyush.anand@...il.com, Arnd Bergmann <arnd@...db.de>,
linux@....linux.org.uk, thomas.petazzoni@...e-electrons.com,
gabriele.paoloni@...wei.com, lorenzo.pieralisi@....com,
james.morse@....com, Liviu.Dudau@....com, jason@...edaemon.net,
robh@...nel.org, gabriel.fernandez@...aro.org,
Minghuan.Lian@...escale.com, linux-pci@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, zhangjukuo@...wei.com,
qiuzhenfa@...ilicon.com, liudongdong3@...wei.com,
qiujiang@...wei.com, xuwei5@...ilicon.com, liguozhu@...ilicon.com
Subject: Re: [PATCH v11 4/6] PCI: hisi: Add PCIe host support for HiSilicon
SoC Hip05
Hi Zhou,
This looks pretty good to me; just a mask question and add a printk.
On Fri, Oct 16, 2015 at 06:23:39PM +0800, Zhou Wang wrote:
> This patch adds PCIe host support for HiSilicon SoC Hip05.
> ...
> +#define PCIE_SUBCTRL_SYS_STATE4_REG 0x6818
> +#define PCIE_LTSSM_LINKUP_STATE 0x11
> +#define PCIE_LTSSM_STATE_MASK 0x3F
Fabio unified some of this; see
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci/host-designware&id=4788fe6ebf4594c9a95b620cbff05147c8504823
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci/host-designware&id=b09464f77dd252a782da1f4e9925c1dbce4540ac
So the question is, why do you use a 6-bit (0x3f) LTSSM_STATE_MASK?
We think we can use a 5-bit mask (0x1f) for all the other
DesignWare-based systems.
> +/* Hip05 PCIe host only supports 32-bit config access */
Thanks for the comment asserting that Hip05 only supports 32-bit
config access. I assume you confirmed that with the hardware
designers. As far as I can tell, this *is* a hardware defect, and at
the minimum, I want a printk at driver probe-time so a dmesg log will
have a clue that read/modify/write on config space might do the wrong
thing.
> +static int hisi_pcie_cfg_read(struct pcie_port *pp, int where, int size,
> + u32 *val)
> ...
Bjorn
--
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