On Tue, Feb 09, 2016 at 05:29:15AM +0800, kbuild test robot wrote:
> Hi Joao,
>
> [auto build test ERROR on arc/for-next]
> [cannot apply to pci/next v4.5-rc3 next-20160208]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improving th
This patch set has the goal to add suppport for DesignWare PCIe RC in ARC
AXS10x. It includes the necessary tweaks to:
- the ARC architecture (PCI support)
- the PCI subsystem (ARC CPU support)
- to pcie-designware (Centralisation of wait for link routine)
- to dra7xx, exynos, imx6 and spear13x
This patch adds PCI support to ARC and updates drivers/pci Makefile
enabling the ARC arch to use the generic PCI setup functions.
Signed-off-by: Joao Pinto
---
Change v8 -> v9:
- Nothing changed (just to keep up with patch set version).
Change v7 -> v8:
- Nothing changed (just to keep up with pat
The "wait for link" routine was centralised and so all drivers using it
(dra7xx, exynos, imx6 and spear13xx) were updated to include the new
function. The keystone driver was not updated because it had some custom
opreations in the link waiting loop.
A simple module (pcie-designware-plat) was cre
On 02/06/2016 05:16 PM, Noam Camus wrote:
From: Noam Camus
Add internal tick generator which is shared by all cores.
Each cluster of cores view it through dedicated address.
This is used for SMP system where all CPUs synced by same
clock source.
Signed-off-by: Noam Camus
Cc: Daniel Lezcano
C
Hello there,
[linux-4.5-rc3/arch/arc/kernel/unwind.c:629]: (warning) Invalid test for
overflow 'ptr+len end)
return -1;
Suggest code rework.
Regards
David Binderman
___
linux-snps-arc mailing l
Hi Bjorn and Arnd,
I agree with you in adding the platform register mechanism to the
pcie-designware core driver. This feature is excellent for who wants to quickly
have a taste of a pcie-designware platform drive for their Synopsys PCIe RC
controller.
Do you have some example for me to check in
On Friday 05 February 2016 17:32:48 Bjorn Helgaas wrote:
> On Fri, Feb 05, 2016 at 03:39:05PM +0100, Arnd Bergmann wrote:
> > On Friday 05 February 2016 10:44:29 Joao Pinto wrote:
> > I think in this case, we should do this completely differently:
> >
> > How about putting all the new code into d
On Monday 08 February 2016 05:40 PM, Daniel Lezcano wrote:
> On 02/02/2016 11:58 AM, Vineet Gupta wrote:
>> - Remove explicit clocksource setup and let it be done by OF framework
>>by defining CLOCKSOURCE_OF_DECLARE() for various timers
>>
>> - This allows multiple clocksources to be potentiall
On 02/02/2016 11:58 AM, Vineet Gupta wrote:
- Remove explicit clocksource setup and let it be done by OF framework
by defining CLOCKSOURCE_OF_DECLARE() for various timers
- This allows multiple clocksources to be potentially registered
simultaneouly: previously we could only do one - as al
10 matches
Mail list logo
