From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id D5A072C00D1 for ; Sat, 28 Sep 2013 08:00:16 +1000 (EST) Message-ID: <1380319203.27811.44.camel@pasglop> Subject: Re: Please revert 928bea964827d7824b548c1f8e06eccbbc4d0d7d From: Benjamin Herrenschmidt To: Yinghai Lu Date: Sat, 28 Sep 2013 08:00:03 +1000 In-Reply-To: References: <1380270519.27811.10.camel@pasglop> <1380318405.27811.37.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: Bjorn Helgaas , "linux-pci@vger.kernel.org" , Linus Torvalds , linuxppc-dev , Linux Kernel list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2013-09-27 at 14:54 -0700, Yinghai Lu wrote: > On Fri, Sep 27, 2013 at 2:46 PM, Benjamin Herrenschmidt > wrote: > > > Wouldn't it be better to simply have pci_enable_device() always set bus > > master on a bridge? I don't see any case where it makes sense to have > > an enabled bridge without the master bit set on it... > > Do you mean attached? That's an option. I was thinking making pci_enable_device() itself enable bus master on a bridge but yes, you approach should work. I'm digging a bit more to figure out what went wrong in the pcie port driver since that's interesting in its own right and I'll then test your patch which I think is a more robust approach. Cheers, Ben.