Re: [PATCH] ata: ahci: power off unused ports

[Kristen Carlson Accardi]

On Mon, 02 Jun 2008 13:45:15 -0400
Jeff Garzik <jeff@xxxxxxxxxx> wrote:

> Kristen Carlson Accardi wrote:
> > Can you tell me what part of this patch is vendor specific?  Maybe
> > I am misunderstanding what you are saying.  Here's that patch again
> > in case you need to look at it again.
> 
> 
> It's specific to AHCI, and does not cover other controllers.
> 
> Certainly PORT_CMD_HPCP must be, but the concept itself is not at all 
> AHCI-specific.
> 
> 	Jeff
> 
> 


@@ -5627,6 +5643,14 @@ int ata_host_register(struct ata_host *h

                        /* wait for EH to finish */
                        ata_port_wait_eh(ap);
+                       ata_link_for_each_dev(dev, &ap->link)
+                               if (ata_dev_enabled(dev))
+                                       device_attached++;
+                       if (!device_attached &&
+                           (ap->flags & ATA_FLAG_NO_HOTPLUG)) {
+                               /* no device present, disable port */
+                               ata_port_disable(ap);
+                       }
                } else {

Here you can see that it would be very easy for another driver
to just add code to set the NO_HOTPLUG flag and then this code
will work for them as well, since we power off the phy using
DET which is specified by SATA.

here's that code:
+static void ata_phy_offline(struct ata_link *link)
+{
+       u32 scontrol;
+       int rc;
+
+       /* set DET to 4 */
+       rc = sata_scr_read(link, SCR_CONTROL, &scontrol);
+       if (rc)
+               return;
+       scontrol &= ~0xf;
+       scontrol |= (1 << 2);
+       sata_scr_write(link, SCR_CONTROL, scontrol);
+}

while it's true that I only modified ahci.c to set
the flag, any other driver writer can do that for the
other drivers based on whatever they want to use to
determine whether to set the NO_HOTPLUG flag.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/