From: Greg KH <greg@kroah.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: PCI devices with no PCI_CACHE_LINE_SIZE implemented
Date: Wed, 5 May 2004 15:31:02 -0700 [thread overview]
Message-ID: <20040505223102.GF30003@kroah.com> (raw)
In-Reply-To: <20040429195301.GB15106@lists.us.dell.com>
On Thu, Apr 29, 2004 at 02:53:01PM -0500, Matt Domsch wrote:
> 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().
Yes, we should make that KERN_DEBUG. I don't have a problem with that.
Care to make a patch?
> 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.
I think we need to stick with 1, unless we get more info on what the
"proper" value should be.
thanks,
greg k-h
next prev parent reply other threads:[~2004-05-05 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 19:53 PCI devices with no PCI_CACHE_LINE_SIZE implemented Matt Domsch
2004-05-05 22:31 ` Greg KH [this message]
2004-05-05 22:48 ` Matt Domsch
2004-05-05 23:42 ` Greg KH
2004-05-05 22:50 ` Matt Domsch
-- strict thread matches above, loose matches on Subject: below --
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=20040505223102.GF30003@kroah.com \
--to=greg@kroah.com \
--cc=Matt_Domsch@dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.