linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: rdunlap@xenotime.net, htejun@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/3]ACPI support for SATA/PATA
Date: Mon, 26 Jun 2006 03:26:14 -0400	[thread overview]
Message-ID: <449F8C16.70308@pobox.com> (raw)
In-Reply-To: <1151044759.7132.153.camel@forrest26.sh.intel.com>

zhao, forrest wrote:
> Hello, all
> 
> In ACPI spec 3.0, section 9.9 defines 4 objects for PATA/SATA:
> 
> _GTM and _STM are PATA-only objects, which are used to get/set PATA
> timing information(i.e. PIO and DMA speed);
> _SDD is SATA-only object, which is used to inform the platform of the
> type of device attached to a port;
> _GTF is for both PATA and SATA, which is used to return ATA task file
> needed to re-init the drive
> 
> In this patch set, 
> ata_acpi_get_timing() is for getting PATA timing information;
> ata_acpi_push_timing() is for setting PATA timing information;
> ata_acpi_push_id() is for operating on _SDD;
> ata_acpi_exec_tfs() is for getting ATA task file from _GTF and executing
> them for a given drive
> 
> NOTE: ata_acpi_get_timing() and ata_acpi_push_timing() are channel
> (port)-level operations, which have more suitable invocation place in
> Tejun's upcoming PM patch. So I would not bother to reference(invoke)
> them in this version of patches and will send out updated patches after
> Tejun's PM patch is merged into #upstream.

This is a great starting point for rejuvinating the SATA ACPI support, 
thanks!

I would request that you create two patches for this support:

Patch #1:  Adds everything needed to make SATA ACPI work...  Makefile, 
noacpi flag, core code, etc.

Patch #2:  Dependent on patch #1.  Adds everything needed to make PATA 
ACPI work.

And overall, I want to reinforce a principle used for Linux patches: 
applying 1-N patches for any given patchset should always produce a 
compileable (and _hopefully_ working) piece of code.  Patches are 
separated into _logical_ changes, much like the steps in a calculus proof.

Regards,

	Jeff




      reply	other threads:[~2006-06-26  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23  6:39 [PATCH 0/3]ACPI support for SATA/PATA zhao, forrest
2006-06-26  7:26 ` Jeff Garzik [this message]

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=449F8C16.70308@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=forrest.zhao@intel.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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).