Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933062Ab1DMVdK (ORCPT ); Wed, 13 Apr 2011 17:33:10 -0400 Received: from mail-qy0-f174.google.com ([209.85.216.174]:65473 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932883Ab1DMVdI convert rfc822-to-8bit (ORCPT ); Wed, 13 Apr 2011 17:33:08 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=HTr1L+pyrQJbLCLMCjq2yhSFrkOpiMpefu4NYRJ7bU97cPzj7KpjRgkawMYMchyBfn py47347Hn/wH9TiYYg+VGrPHwCwpTbKBZWq6P4ZwDUhaM8Kp+Hp9ik+rJ5dwBNXNzIW5 tZYttn2l3Mf4382OUBEAc8epF193HHDSq8KC8= MIME-Version: 1.0 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> Date: Wed, 13 Apr 2011 23:33:07 +0200 Message-ID: Subject: Re: [RFC][PATCH V4] axi: add AXI bus driver From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: George Kashperko Cc: Greg KH , linux-wireless@vger.kernel.org, "John W. Linville" , b43-dev@lists.infradead.org, =?UTF-8?Q?Michael_B=C3=BCsch?= , Larry Finger , Arend van Spriel , linux-arm-kernel@lists.infradead.org, Russell King , Arnd Bergmann , Andy Botting , linuxdriverproject , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 973 Lines: 23 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Ƃ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/