Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754535Ab3GBQlF (ORCPT ); Tue, 2 Jul 2013 12:41:05 -0400 Received: from mail-oa0-f49.google.com ([209.85.219.49]:37926 "EHLO mail-oa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753877Ab3GBQlB (ORCPT ); Tue, 2 Jul 2013 12:41:01 -0400 MIME-Version: 1.0 In-Reply-To: <3216917.m2IEX2IHod@vostro.rjw.lan> References: <1372177330-28013-1-git-send-email-mika.westerberg@linux.intel.com> <1530651.ees8hXMYoR@vostro.rjw.lan> <20130701183612.GJ9294@intel.com> <3216917.m2IEX2IHod@vostro.rjw.lan> From: Bjorn Helgaas Date: Tue, 2 Jul 2013 10:40:39 -0600 Message-ID: Subject: Re: [PATCH 1/6] PCI: acpiphp: do not check for SLOT_ENABLED in enable_device() To: "Rafael J. Wysocki" Cc: Mika Westerberg , "Kirill A. Shutemov" , Greg Kroah-Hartman , "Rafael J. Wysocki" , Jesse Barnes , Yinghai Lu , "Ronciak, John" , "Penner, Miles J" , Bruce Allan , Heikki Krogerus , "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" , "x86@kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1420 Lines: 30 On Mon, Jul 1, 2013 at 7:29 PM, Rafael J. Wysocki wrote: > On Monday, July 01, 2013 09:36:13 PM Mika Westerberg wrote: >> On Mon, Jul 01, 2013 at 04:01:37PM +0200, Rafael J. Wysocki wrote: >> > > Given the fact that SLOT_ENABLED is only checked in acpiphp_enable_slot() >> > > (after this patch) and that /sys/bus/pci/slots/*/power uses SLOT_POWEREDON >> > > anyway, should we remove the whole flag? >> > >> > Sure, if it is not necessary any more, we should remove it. >> >> Well, there is one thing that changes due that. Once the flag is gone >> userspace can do 'echo 1 > /sys/bus/pci/slots/*/power' several times and >> the slot is always re-enumerated. >> >> If that is not acceptable we should probably move the SLOT_ENABLED check >> closer to acpiphp_core:enable_device() and drop it from here, so that we >> always re-enumerate on Bus Check event but userspace can only do enable >> once (we still re-enumerate on Bus Check). > > Yes, that sounds like the right thing to do. Is it actually a problem if we re-enumerate every time userspace does 'echo 1 > /sys/bus/pci/slots/*/power'? I assume re-enumeration is a no-op if nothing has changed. Bjorn -- 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/