mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: PCI devices with no PCI_CACHE_LINE_SIZE implemented
Date: Thu, 29 Apr 2004 14:53:01 -0500	[thread overview]
Message-ID: <20040429195301.GB15106@lists.us.dell.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

Greg,

Some PCI device functions, such as the EHCI portion of Intel ICH5 and
ICH6 chips, do not implement the PCI_CACHE_LINE_SIZE register (which
is legal to not implement per PCI spec as it is a busmaster that
cannot issue a MWI).  However, for each of these, the kernel tries to
set the value, fails, and prints a KERN_WARNING message about it.

a) need this be a warning, wouldn't KERN_DEBUG suffice, if a message
is needed at all?  This is printed in pci_generic_prep_mwi().

b) How might you prefer to handle such devices?

Per the PCI 2.3 spec, reading a value of 0 may mean several things:
1) setting the register at all isn't supported
   - this is what pci.c assumes now and returns -EINVAL.
2) setting the register to the value you tried isn't supported, but
   you can try again with another value until you find the right one.
   - but there are no hints as to what the right value for a device
     might be.

Personally, I'd be happy if the printk were gone completely, but
that's your call.  With the prints there, our support organization is
concerned it can cause tech support calls for (in this case) a non-issue. 

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-04-29 19:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 19:53 Matt Domsch [this message]
2004-05-05 22:31 ` Greg KH
2004-05-05 22:48   ` Matt Domsch
2004-05-05 23:42     ` Greg KH
2004-05-05 22:50   ` Matt Domsch
2004-05-06 13:28 Matt Domsch
2004-05-06 15:45 ` Jeff Garzik
2004-05-10 10:49   ` Martin Mares

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040429195301.GB15106@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®