1. 17 7月, 2008 7 次提交
    • B
      ISAPNP: handle independent options following dependent ones · bbe413b4
      Bjorn Helgaas 提交于
      The ISAPNP spec recommends that independent options precede
      dependent ones, but this is not actually required.  The current
      ISAPNP code incorrectly puts such trailing independent options
      at the end of the last dependent option list.
      
      This patch fixes that bug by resetting the current option list
      to the independent list when we see an "End Dependent Functions"
      tag.  PNPBIOS and PNPACPI handle this the same way.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Acked-by: NRene Herman <rene.herman@gmail.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      bbe413b4
    • B
      PNP: remove extra 0x100 bit from option priority · e2a1a6f1
      Bjorn Helgaas 提交于
      When building resource options, ISAPNP and PNPBIOS set the priority
      to something like "0x100 | PNP_RES_PRIORITY_ACCEPTABLE", but we
      immediately mask off the 0x100 again in pnp_build_option(), so that
      bit looks superfluous.
      
      Thanks to Rene Herman <rene.herman@gmail.com> for pointing this out.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Acked-by: NRene Herman <rene.herman@gmail.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      e2a1a6f1
    • B
      PNP: centralize resource option allocations · c227536b
      Bjorn Helgaas 提交于
      This patch moves all the option allocations (pnp_mem, pnp_port, etc)
      into the pnp_register_{mem,port,irq,dma}_resource() functions.  This
      will make it easier to rework the option data structures.
      
      The non-trivial part of this patch is the IRQ handling.  The backends
      have to allocate a local pnp_irq_mask_t bitmap, populate it, and pass
      a pointer to pnp_register_irq_resource().
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Acked-by: NRene Herman <rene.herman@gmail.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c227536b
    • B
      PNP: introduce pnp_irq_mask_t typedef · 7aefff51
      Bjorn Helgaas 提交于
      This adds a typedef for the IRQ bitmap, which should cause
      no functional change, but will make it easier to pass a
      pointer to a bitmap to pnp_register_irq_resource().
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Acked-by: NRene Herman <rene.herman@gmail.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      7aefff51
    • B
      PNP: define PNP-specific IORESOURCE_IO_* flags alongside IRQ, DMA, MEM · 08c9f262
      Bjorn Helgaas 提交于
      PNP previously defined PNP_PORT_FLAG_16BITADDR and PNP_PORT_FLAG_FIXED
      in a private header file, but put those flags in struct resource.flags
      fields.  Better to make them IORESOURCE_IO_* flags like the existing
      IRQ, DMA, and MEM flags.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Acked-by: NRene Herman <rene.herman@gmail.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      08c9f262
    • B
      PNP: replace pnp_resource_table with dynamically allocated resources · aee3ad81
      Bjorn Helgaas 提交于
      PNP used to have a fixed-size pnp_resource_table for tracking the
      resources used by a device.  This table often overflowed, so we've
      had to increase the table size, which wastes memory because most
      devices have very few resources.
      
      This patch replaces the table with a linked list of resources where
      the entries are allocated on demand.
      
      This removes messages like these:
      
          pnpacpi: exceeded the max number of IO resources
          00:01: too many I/O port resources
      
      References:
      
          http://bugzilla.kernel.org/show_bug.cgi?id=9535
          http://bugzilla.kernel.org/show_bug.cgi?id=9740
          http://lkml.org/lkml/2007/11/30/110
      
      This patch also changes the way PNP uses the IORESOURCE_UNSET,
      IORESOURCE_AUTO, and IORESOURCE_DISABLED flags.
      
      Prior to this patch, the pnp_resource_table entries used the flags
      like this:
      
          IORESOURCE_UNSET
      	This table entry is unused and available for use.  When this flag
      	is set, we shouldn't look at anything else in the resource structure.
      	This flag is set when a resource table entry is initialized.
      
          IORESOURCE_AUTO
      	This resource was assigned automatically by pnp_assign_{io,mem,etc}().
      
      	This flag is set when a resource table entry is initialized and
      	cleared whenever we discover a resource setting by reading an ISAPNP
      	config register, parsing a PNPBIOS resource data stream, parsing an
      	ACPI _CRS list, or interpreting a sysfs "set" command.
      
      	Resources marked IORESOURCE_AUTO are reinitialized and marked as
      	IORESOURCE_UNSET by pnp_clean_resource_table() in these cases:
      
      	    - before we attempt to assign resources automatically,
      	    - if we fail to assign resources automatically,
      	    - after disabling a device
      
          IORESOURCE_DISABLED
      	Set by pnp_assign_{io,mem,etc}() when automatic assignment fails.
      	Also set by PNPBIOS and PNPACPI for:
      
      	    - invalid IRQs or GSI registration failures
      	    - invalid DMA channels
      	    - I/O ports above 0x10000
      	    - mem ranges with negative length
      
      After this patch, there is no pnp_resource_table, and the resource list
      entries use the flags like this:
      
          IORESOURCE_UNSET
      	This flag is no longer used in PNP.  Instead of keeping
      	IORESOURCE_UNSET entries in the resource list, we remove
      	entries from the list and free them.
      
          IORESOURCE_AUTO
      	No change in meaning: it still means the resource was assigned
      	automatically by pnp_assign_{port,mem,etc}(), but these functions
      	now set the bit explicitly.
      
      	We still "clean" a device's resource list in the same places,
      	but rather than reinitializing IORESOURCE_AUTO entries, we
      	just remove them from the list.
      
      	Note that IORESOURCE_AUTO entries are always at the end of the
      	list, so removing them doesn't reorder other list entries.
      	This is because non-IORESOURCE_AUTO entries are added by the
      	ISAPNP, PNPBIOS, or PNPACPI "get resources" methods and by the
      	sysfs "set" command.  In each of these cases, we completely free
      	the resource list first.
      
          IORESOURCE_DISABLED
      	In addition to the cases where we used to set this flag, ISAPNP now
      	adds an IORESOURCE_DISABLED resource when it reads a configuration
      	register with a "disabled" value.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      aee3ad81
    • B
      PNP: remove pnp_resource.index · 87e4acf3
      Bjorn Helgaas 提交于
      We used pnp_resource.index to keep track of which ISAPNP configuration
      register a resource should be written to.  We needed this only to
      handle the case where a register is disabled but a subsequent register
      in the same set is enabled.
      
      Rather than explicitly maintaining the pnp_resource.index, this patch
      adds a resource every time we read an ISAPNP configuration register
      and marks the resource as IORESOURCE_DISABLED when appropriate.  This
      makes the position in the pnp_resource_table always correspond to the
      config register index.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      87e4acf3
  2. 29 4月, 2008 22 次提交
  3. 23 3月, 2008 1 次提交
    • B
      ISAPNP: fix limits of logical device register set · 245073f0
      Bjorn Helgaas 提交于
      PNP_MAX_MEM and PNP_MAX_PORT are mainly used to size tables of PNP
      device resources.  In 2.6.24, we increased their values to accomodate
      ACPI devices that have many resources:
      
                       2.6.23    2.6.24
                       ------    ------
        PNP_MAX_MEM       4         12
        PNP_MAX_PORT      8         40
      
      However, ISAPNP also used these constants as the size of parts of the
      logical device register set.  This register set is fixed by hardware,
      so increasing the constants meant that we were reading and writing
      unintended parts of the register set.
      
      This patch changes ISAPNP to use the correct register set sizes (the
      same values we used prior to 2.6.24).
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      245073f0
  4. 16 10月, 2007 1 次提交
  5. 24 8月, 2007 3 次提交
  6. 27 7月, 2007 2 次提交
  7. 17 7月, 2007 1 次提交
  8. 14 12月, 2006 1 次提交
  9. 02 10月, 2006 1 次提交
  10. 01 7月, 2006 1 次提交