From: Jay Cliburn <jacliburn@bellsouth.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: jeff@garzik.org, shemminger@osdl.org, csnook@redhat.com,
hch@infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, atl1-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/4] atl1: Main C file for Attansic L1 driver
Date: Mon, 22 Jan 2007 10:48:19 -0600 [thread overview]
Message-ID: <45B4EAD3.6030404@bellsouth.net> (raw)
In-Reply-To: <1169454156.3055.1256.camel@laptopd505.fenrus.org>
Arjan, thank you very much for reviewing the driver.
Arjan van de Ven wrote:
> On Sun, 2007-01-21 at 15:06 -0600, Jay Cliburn wrote:
[snip]
>> +void atl1_irq_disable(struct atl1_adapter *adapter)
>> +{
>> + atomic_inc(&adapter->irq_sem);
>> + iowrite32(0, adapter->hw.hw_addr + REG_IMR);
>> + synchronize_irq(adapter->pdev->irq);
>> +}
>
> doesn't this want a PCI posting flush?
> I'm also a bit sceptical about irq_sem ...
PCI posting flush will be added. Would you mind elaborating on your
skepticism about irq_sem?
>> +/**
>> + * When ACPI resume on some VIA MotherBoard, the Interrupt Disable bit/0x400
>> + * on PCI Command register is disable.
>> + * The function enable this bit.
>> + * Brackett, 2006/03/15
>> + */
>> +static void atl1_via_workaround(struct atl1_adapter *adapter)
>> +{
>> + unsigned long value;
>> +
>> + value = ioread16(adapter->hw.hw_addr + PCI_COMMAND);
>> + if (value & PCI_COMMAND_INTX_DISABLE)
>> + value &= ~PCI_COMMAND_INTX_DISABLE;
>> + iowrite32(value, adapter->hw.hw_addr + PCI_COMMAND);
>> +}
>
> hmm I wonder if this shouldn't be a more generic PCI level quirk, not so
> much a driver level quirk...
The vendor put this code here, and we're loathe to remove it unless
absolutely necessary. Is it okay with you if we leave it?
Thanks,
Jay
next prev parent reply other threads:[~2007-01-22 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 21:06 [PATCH 3/4] atl1: Main C file for Attansic L1 driver Jay Cliburn
2007-01-22 8:22 ` Arjan van de Ven
2007-01-22 16:48 ` Jay Cliburn [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-11 0:42 Jay Cliburn
2007-01-11 9:33 ` Christoph Hellwig
2006-11-19 20:30 Jay Cliburn
2006-11-19 21:46 ` Jan Engelhardt
2006-11-19 23:57 ` Arnd Bergmann
2006-11-20 6:12 ` Chris Snook
2006-11-20 12:21 ` Arnd Bergmann
2006-11-20 18:02 ` Stephen Hemminger
2006-11-20 19:35 ` Jeff Garzik
2006-11-20 20:15 ` Stephen Hemminger
2006-11-20 21:36 ` Jeff Garzik
2006-11-20 21:59 ` Stephen Hemminger
2006-11-20 22:04 ` Jeff Garzik
2006-11-20 23:17 ` Stephen Hemminger
2006-11-20 12:39 ` Chris Snook
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=45B4EAD3.6030404@bellsouth.net \
--to=jacliburn@bellsouth.net \
--cc=arjan@infradead.org \
--cc=atl1-devel@lists.sourceforge.net \
--cc=csnook@redhat.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).