linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jfs@keytradebank.com, 0602@eq.cz, linux-ide@vger.kernel.org,
	Jason Gaston <jason.d.gaston@intel.com>
Subject: Re: [PATCHSET] ata_piix: improve combined mode handling
Date: Fri, 03 Mar 2006 15:53:24 -0500	[thread overview]
Message-ID: <4408ACC4.2070907@pobox.com> (raw)
In-Reply-To: <11411439383398-git-send-email-htejun@gmail.com>

Tejun Heo wrote:
> I couldn't find datasheets for ESB2 and ICH8, so I assumed ESB2 is
> similar to ICH6, ICH8 to ICH6 and ICH8M to ICH6M.  Is this correct?

That would be my guess.  Best bet would be to email Jason Gaston (CC'd), 
as he's the person who has been submitted PCI ID patches from Intel.


> Jeff, I'm trying to implement SCR access on ICH6/7's on top of these
> changes and have a question about libata-bmdma.c::ata_pci_init_one().
> ata_piix needs its own version of this function as it should try to
> map ABAR for SCR (and fall back if it fails), so I'm trying to factor
> functions out of ata_pci_init_one() and call them from ata_piix.
> 
> ata_pci_init_one() currently uses two separate probe_ent for each port
> if the controller is in legacy mode, which makes the ports use
> separate host_set and thus separate spin locks.  Do they need to use
> separate spinlocks?  Or are there other reasons legacy initialization
> is done this way?

They are two totally independent ports and irqs, when in legacy mode.  I 
would turn that question around on you:  why do you feel the need to 
serialize two independent irqs with a single spinlock?  ;-)

On a side note, if you are poking in this area, also consider a related 
problem:  PATA ports on SATA controllers.  Promise, SiS, ULi and VIA all 
need some way to support programming the PATA port, but right now the 
probe_ent/port_info stuff makes it difficult to have two separate 
classes of ports, with two vastly different capabilities.


> Oh.. Another question.  When you were talking about getting PCS bits
> wrong before [3], were you talking about port map (like port 1 and 3
> map to primary master/slave) or is there something else PCS + MAP
> doesn't cover?

In the ICH6 and ICH7 docs, both PCS and MAP registers are peppered with 
"(mobile only)" and "(desktop only)" comments.

	Jeff



  parent reply	other threads:[~2006-03-03 20:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 16:25 [PATCHSET] ata_piix: improve combined mode handling Tejun Heo
2006-02-28 16:25 ` [PATCH 1/6] libata: seperate out ata_class_present() Tejun Heo
2006-03-03 20:40   ` Jeff Garzik
2006-02-28 16:25 ` [PATCH 4/6] ata_piix: implement proper port map Tejun Heo
2006-02-28 16:25 ` [PATCH 6/6] ata_piix: don't scan non-existent device Tejun Heo
2006-03-03 20:43   ` Jeff Garzik
2006-02-28 16:25 ` [PATCH 5/6] ata_piix: reimplement piix_sata_probe() Tejun Heo
2006-02-28 16:25 ` [PATCH 3/6] ata_piix: add a couple of flags Tejun Heo
2006-03-03 20:33   ` Jeff Garzik
2006-03-05  5:28     ` [PATCH] ata_piix: rename PIIX_FLAG_IGN_PRESENT to PIIX_FLAG_IGNORE_PCS Tejun Heo
2006-03-05  5:36       ` Jeff Garzik
2006-02-28 16:25 ` [PATCH 2/6] ata_piix: finer-grained port_info Tejun Heo
2006-02-28 18:17 ` [PATCHSET] ata_piix: improve combined mode handling Jeff Garzik
2006-03-01  5:16   ` Tejun Heo
2006-03-03 17:37 ` Jeff Garzik
2006-03-03 20:53 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-02  7:09 Tejun Heo

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=4408ACC4.2070907@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=0602@eq.cz \
    --cc=htejun@gmail.com \
    --cc=jason.d.gaston@intel.com \
    --cc=jfs@keytradebank.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).