Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964913AbbEMSHa (ORCPT ); Wed, 13 May 2015 14:07:30 -0400 Received: from mail-bn1bon0073.outbound.protection.outlook.com ([157.56.111.73]:25600 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932186AbbEMSH0 (ORCPT ); Wed, 13 May 2015 14:07:26 -0400 X-Greylist: delayed 108327 seconds by postgrey-1.27 at vger.kernel.org; Wed, 13 May 2015 14:07:25 EDT Authentication-Results: kernel.org; dkim=none (message not signed) header.d=none; Date: Wed, 13 May 2015 20:07:05 +0200 From: Robert Richter To: Tejun Heo CC: Robert Richter , Catalin Marinas , Will Deacon , Sunil Goutham , Jiang Liu , , , , Alexander Gordeev Subject: Re: [PATCH v2] AHCI: Add generic MSI-X interrupt support to SATA PCI driver Message-ID: <20150513180705.GZ10428@rric.localhost> References: <20150513143353.GU11388@htj.duckdns.org> <20150513143906.GV11388@htj.duckdns.org> <20150513172828.GA8449@rric.localhost> <20150513174640.GZ11388@htj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20150513174640.GZ11388@htj.duckdns.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Originating-IP: [92.224.195.80] X-ClientProxiedBy: AM2PR02CA0038.eurprd02.prod.outlook.com (25.160.28.176) To DM2PR0701MB811.namprd07.prod.outlook.com (10.242.127.25) X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0701MB811; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5005006)(3002001);SRVR:DM2PR0701MB811;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0701MB811; X-Forefront-PRVS: 0575F81B58 X-Forefront-Antispam-Report: SFV:NSPM;SFS:(10009020)(6069001)(6009001)(24454002)(51704005)(164054003)(83506001)(110136002)(76176999)(54356999)(47776003)(189998001)(50466002)(46102003)(87976001)(92566002)(86362001)(62966003)(2950100001)(77156002)(5001960100002)(50986999)(122386002)(40100003)(97756001)(33656002)(4001350100001)(23726002)(66066001)(76506005)(46406003)(93886004)(77096005)(42186005)(217873001);DIR:OUT;SFP:1101;SCL:1;SRVR:DM2PR0701MB811;H:rric.localhost;FPR:;SPF:None;MLV:sfv;LANG:en; X-OriginatorOrg: caviumnetworks.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 May 2015 18:07:18.0520 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0701MB811 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1952 Lines: 49 On 13.05.15 13:46:40, Tejun Heo wrote: > Hello, Robert. > > On Wed, May 13, 2015 at 07:28:28PM +0200, Robert Richter wrote: > > > > This looks not very useful to do. Since irq is used only a single > > > > time, there is no reason to store it in the host's data structure. It > > > > > > Doesn't really matter tho. > > > > Since ahci_host_activate() is EXPORT_SYMBOL_GPL I really have concerns > > changing the i/f. But I will send you a patch for this. > > It doesn't matter. Please go ahead and change it. Ok, np. > > > Let's start with why we're doing this in the first place. > > > > Right, the sata controller is connected to a pci ecam controller, both > > are on an SoC together with the processor. There are no external pci > > ports for the connection of external devices. Since all pci devices on > > the chip support msi-x, the controller is only capable to handle this > > and not INTx nor MSI. So for enabling of the sata hc we need msix > > support. > > I see. If you can get hold of an ahci controller which actually can > do multi-irq msix, it'd be the best. If not, let's make it super > clear that this is a special case and use it as the last resort (which > also clers up the warning issue). This sounds good. The device actually supports multi-irq msix, a single mode interrupt + additional interrupts for error or hotplug handling. But I don't have hardware for a per-port msix host controller. So I will move msix after msi then and mark it as a special case if msi is not supported. I don't want to move it after intx since this is the fallback if nothing else works, there is no explicit check for intx, I even don't know if that is possible at all. Thanks, -Robert -- 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/