public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Jeff Garzik <jeff@garzik.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc7-git1: AHCI not seeing devices on ICH8 mobo (DG965RY)
Date: Mon, 18 Sep 2006 12:34:44 +0900	[thread overview]
Message-ID: <450E13D4.10200@gmail.com> (raw)
In-Reply-To: <20060918034826.GA10116@curie-int.orbis-terrarum.net>

Robin H. Johnson wrote:
> Yes your patch fixes it perfectly - it's a better version of an almost
> working fix I hacked up after my previous email.
> 
> Some patch review comments below as well.
> 
> Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
> 
>> @@ -186,9 +187,11 @@ struct ahci_host_priv {
>>  	unsigned long		flags;
>>  	u32			cap;	/* cache of HOST_CAP register */
>>  	u32			port_map; /* cache of HOST_PORTS_IMPL reg */
>> +	int			port_tbl[AHCI_MAX_PORTS];
>>  };
> maybe u8 instead of int?

Yeah, I like that.

> also a comment - /* mapping of port_idx to the implemented port */

Okay.

>> +	if (n_ports == 0) {
>> +		dev_printk(KERN_ERR, &pdev->dev, "0 port implemented\n");
>> +		return -EINVAL;
>> +	}
> Use plural form (0 ports), or negative (No ports) instead.

And, okay.

Jeff, we've been ignoring PI in ahci_host_init()...

	for (i = 0; i < probe_ent->n_ports; i++) {
#if 0 /* BIOSen initialize this incorrectly */
		if (!(hpriv->port_map & (1 << i)))
			continue;
#endif

The comment suggests that some BIOSen initialize PI incorrectly which 
will probably result in undetected ports.  Is this true?  Would it be 
dangerous to honor PI on some controllers?  If so, PI should be used 
only for controllers which does non-linear port mapping.

Thanks.

-- 
tejun

  reply	other threads:[~2006-09-18  3:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 20:05 2.6.18-rc7-git1: AHCI not seeing devices on ICH8 mobo (DG965RY) Robin H. Johnson
2006-09-14 19:19 ` Jeff Garzik
2006-09-14 20:50   ` Robin H. Johnson
2006-09-16 20:38     ` Robin H. Johnson
2006-09-16 21:08       ` Robin H. Johnson
2006-09-17  7:49         ` Tejun Heo
2006-09-18  3:48           ` Robin H. Johnson
2006-09-18  3:34             ` Tejun Heo [this message]
2006-09-19  3:53               ` Jeff Garzik
2006-09-19  4:49                 ` Robin H. Johnson
2006-09-19  6:06           ` Jeff Garzik
2006-09-19  6:24             ` Tejun Heo
2006-09-25 21:39               ` Robin H. Johnson
2006-09-19  7:03             ` Robin H. Johnson
2006-12-05  6:21           ` Kurtis D. Rader

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=450E13D4.10200@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robbat2@gentoo.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