From mboxrd@z Thu Jan 1 00:00:00 1970 From: zajec5@gmail.com (=?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?=) Date: Wed, 13 Apr 2011 23:33:07 +0200 Subject: [RFC][PATCH V4] axi: add AXI bus driver In-Reply-To: <1302729850.8479.7.camel@dev.znau.edu.ua> References: <1302634375-2378-1-git-send-email-zajec5@gmail.com> <20110413163113.GA24015@kroah.com> <1302726703.8015.1.camel@dev.znau.edu.ua> <1302727516.8015.9.camel@dev.znau.edu.ua> <1302729243.8479.1.camel@dev.znau.edu.ua> <1302729850.8479.7.camel@dev.znau.edu.ua> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 2011/4/13 George Kashperko : >> 2011/4/13 George Kashperko : >> >> I had no idea what you were referring to. We do not dig into PCIe >> >> functions yet, so I believe for now we need this "if". >> > You are already deep inside. Your host code drives pci function. >> >> But I don't use multiple PCIe functions, do not focus on that at all. >> > Don't see anything in the host driver code preventing it to be bound to > functions other than 0. But anyways if you sure your host will be used > by several cores then why don't you spinlock window accesses ? I should, it was discussed, please let's leave it for now. Lets first focus on how to correctly implement this driver. -- Rafa?