RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in fjes seems like a bug,

From	"Izumi, Taku" <izumi.taku@jp.fujitsu.com>
Newsgroups	linux.kernel
Subject	RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in fjes seems like a bug,
Date	2016-06-09 10:50 +0200
Message-ID	<rI3P3-3Y6-3@gated-at.bofh.it> (permalink)
References	(1 earlier) <rHFWq-5tG-29@gated-at.bofh.it> <rHFWq-5tG-31@gated-at.bofh.it> <rHFWq-5tG-33@gated-at.bofh.it> <rHFWq-5tG-35@gated-at.bofh.it> <rHFWp-5tG-25@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in  fjes seems like a bug, Gabriele Paoloni <gabriele.paoloni@huawei.com> - 2016-06-08 09:20 +0200
  RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in  fjes seems like a bug, "Izumi, Taku" <izumi.taku@jp.fujitsu.com> - 2016-06-09 10:50 +0200

csiph-web