From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754468AbcFIItG (ORCPT ); Thu, 9 Jun 2016 04:49:06 -0400 Received: from mgwkm02.jp.fujitsu.com ([202.219.69.169]:54360 "EHLO mgwkm02.jp.fujitsu.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751551AbcFIItC (ORCPT ); Thu, 9 Jun 2016 04:49:02 -0400 From: "Izumi, Taku" To: Gabriele Paoloni CC: Linuxarm , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "liudongdong (C)" , "davem@davemloft.net" Subject: RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in fjes seems like a bug, Thread-Topic: [bug discuss] fjes driver call trace warning, "PNP0C02" used in fjes seems like a bug, Thread-Index: AQHRvXvZjxo3Zl+VI0Wg7agQdZbEbp/XgWdwgASrzTCAAAddcIACqOqAgABMSOCAAbCy8A== Date: Thu, 9 Jun 2016 08:48:45 +0000 Message-ID: References: <57515004.1080301@huawei.com> In-Reply-To: Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-securitypolicycheck: OK by SHieldMailChecker v2.3.2 x-shieldmailcheckerpolicyversion: FJ-ISEC-20150624-1 x-shieldmailcheckermailid: 78e7eaa211904826b7e5707011e7b618 x-originating-ip: [10.33.110.210] Content-Type: text/plain; charset="iso-2022-jp" MIME-Version: 1.0 X-SecurityPolicyCheck-GC: OK by FENCE-Mail X-TM-AS-MML: disable Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Gao, > From a SW perspective it like an acpi driver that uses "PNP0C02" > as driver ids to perform the driver match in the ACPI table. > > From my understanding this is wrong in principle because that identifier > must be used to reserve motherboard resources (see par 4.1.2 of the PCI > Firmware Specifications v3.2) > > Therefore such identifier it is used from > http://lxr.free-electrons.com/source/drivers/pnp/system.c > to reserve such resources. > > Basically your driver is breaking any other device that > needs to reserve motherboard resources through system.c > driver. > > @David Miller, what is your opinion about this? > I think this driver should be reverted... I'm willing to revise my driver if it's something wrong. I can't reproduce this problem. Could you please show me how to reproduce problem ? Sincerely, Taku Izumi