linux-toradex.git/arch/x86/kernel/quirks.c, branch v3.0.45

x86: HPET force enable for CX700 / VIA Epia LT

2010-09-15T14:27:04+00:00

Allow using HPET with the hpet=force command line option on VIA EPIA
CX700 systems.

Signed-off-by: Udo van den Heuvel 
Cc: Robert Hancock 
LKML-Reference:  <4C8F04DC.5060303@xs4all.nl>
Signed-off-by: Thomas Gleixner

x86: Force HPET readback_cmp for all ATI chipsets

2010-07-15T15:10:02+00:00

commit 30a564be (x86, hpet: Restrict read back to affected ATI
chipset) restricted the workaround for the HPET bug to SMX00
chipsets. This was reasonable as those were the only ones against
which we ever got a bug report.

Stephan Wolf reported now that this patch breaks his IXP400 based
machine. Though it's confirmed to work on other IXP400 based systems.

To error out on the safe side, we force the HPET readback workaround
for all ATI SMbus class chipsets.

Reported-by: Stephan Wolf 
LKML-Reference: 
Signed-off-by: Thomas Gleixner 
Tested-by: Stephan Wolf 
Acked-by: Borislav Petkov

x86, hpet: Add reference to chipset erratum documentation for disable-hpet-msi-quirk

2010-05-17T17:04:43+00:00

(At the moment the "SB700 Family Product Errata" document is available
at http://support.amd.com/us/Embedded_TechDocs/46837.pdf)

Signed-off-by: Andreas Herrmann 
LKML-Reference: <20100517164324.GB10254@alberich.amd.com>
Signed-off-by: H. Peter Anvin

x86, hpet: Restrict read back to affected ATI chipsets

2010-04-29T01:14:29+00:00

After programming the HPET, we do a readback as a workaround for
ATI/SBx00 chipsets as a synchronization.  Unfortunately this triggers
an erratum in newer ICH chipsets (ICH9+) where reading the comparator
immediately after the write returns the old value.  Furthermore, as
always, I/O reads are bad for performance.

Therefore, restrict the readback to the chipsets that need it, or, for
debugging purposes, when we are running with hpet=verbose.

Signed-off-by: Thomas Gleixner 
Acked-by: Venkatesh Pallipadi 
LKML-Reference: <20100225185348.GA9674@linux-os.sc.intel.com>
Signed-off-by: H. Peter Anvin

x86: Disable HPET MSI on ATI SB700/SB800

2010-01-23T05:21:58+00:00

HPET MSI on platforms with ATI SB700/SB800 as they seem to have some
side-effects on floppy DMA. Do not use HPET MSI on such platforms.

Original problem report from Mark Hounschell
http://lkml.indiana.edu/hypermail/linux/kernel/0912.2/01118.html

[ This patch needs to go to stable as well. But, there are some
  conflicts that prevents the patch from going as is. I can
  rebase/resubmit to stable once the patch goes upstream.
  hpa: still Cc:'ing stable@ as an FYI. ]

Tested-by: Mark Hounschell 
Signed-off-by: Venkatesh Pallipadi 
Cc: 
LKML-Reference: <20100121190952.GA32523@linux-os.sc.intel.com>
Signed-off-by: H. Peter Anvin

x86: AMD Northbridge: Verify NB's node is online

2009-11-16T14:43:05+00:00

Fix panic seen on some IBM and HP systems on 2.6.32-rc6:

 BUG: unable to handle kernel NULL pointer dereference at (null)
 IP: [] find_next_bit+0x77/0x9c
  [...]
  [] cpumask_next_and+0x2e/0x3b
  [] pci_device_probe+0x8e/0xf5
  [] ? driver_sysfs_add+0x47/0x6c
  [] driver_probe_device+0xd9/0x1f9
  [] __driver_attach+0x58/0x7c
  [] ? __driver_attach+0x0/0x7c
  [] bus_for_each_dev+0x54/0x89
  [] driver_attach+0x19/0x1b
  [] bus_add_driver+0xd3/0x23d
  [] driver_register+0x98/0x109
  [] __pci_register_driver+0x63/0xd3
  [] ? up_read+0x26/0x2a
  [] ? k8temp_init+0x0/0x20 [k8temp]
  [] k8temp_init+0x1e/0x20 [k8temp]
  [] do_one_initcall+0x6d/0x185
  [] sys_init_module+0xd3/0x236
  [] system_call_fastpath+0x16/0x1b

I put in a printk and commented out the set_dev_node()
call when and got this output:

 quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x0
 quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x1
 quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x2
 quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x3

I.e. the issue appears to be that the HW has set val to a valid
value, however, the system is only configured for a single
node -- 0, the others are offline.

Check to see if the node is actually online before setting
the numa node for an AMD northbridge in quirk_amd_nb_node().

Signed-off-by: Prarit Bhargava 
Cc: bhavna.sarathy@amd.com
Cc: jbarnes@virtuousgeek.org
Cc: andreas.herrmann3@amd.com
LKML-Reference: <20091112180933.12532.98685.sendpatchset@prarit.bos.redhat.com>
[ v2: clean up the code and add comments ]
Signed-off-by: Ingo Molnar

x86/PCI: pci quirks, fix pci refcounting

2009-09-09T21:11:02+00:00

Stanse found a pci reference leak in quirk_amd_nb_node.
Instead of putting nb_ht, there is a put of dev passed as
an argument.

http://stanse.fi.muni.cz/

Signed-off-by: Jiri Slaby 
Signed-off-by: Jesse Barnes

Merge branch 'linus' into x86/cpu

2009-06-07T10:22:15+00:00

x86, hpet: Stop soliciting hpet=force users on ICH4M

2009-04-24T06:41:39+00:00

The HPET in the ICH4M is not documented in the data sheet
because it was not officially validated.

While it is fine for hackers to continue to use "hpet=force"
to enable the hardware that they have, it is not prudent to
solicit additional "hpet=force" users on this hardware.

[ Impact: remove hpet=force syslog message on old-ICH systems ]

Signed-off-by: Len Brown 
Acked-by: Venkatesh Pallipadi 
LKML-Reference: 
Signed-off-by: Ingo Molnar

x86: fixup numa_node information for AMD CPU northbridge functions

2009-04-17T16:12:36+00:00

Currently the numa_node attribute for these PCI devices is 0 (it
corresponds to the numa_node for PCI bus 0). This is not a big issue
but incorrect.

This inconsistency can be fixed by reading the node number from CPU
NB function 0.

[ Impact: fill in dev->numa_node information, to optimize DMA allocations ]

Signed-off-by: Andreas Herrmann 
Cc: jbarnes@virtuousgeek.org
LKML-Reference: <20090417100746.GG16198@alberich.amd.com>
Signed-off-by: Ingo Molnar