All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: Subject should be [PATCHSET libata-dev#upstream-fixes] libata: prefer hardreset, take #3
Date: Mon, 17 Mar 2008 18:36:20 +0900	[thread overview]
Message-ID: <47DE3B94.2090501@gmail.com> (raw)
In-Reply-To: <18398.10615.977550.334382@harpo.it.uu.se>

Mikael Pettersson wrote:
>  > > With this patch in place the hard reset conversion does seem to
>  > > work Ok on a SATA300 TX4 card.
>  > [--snip--]
>  > > +	for(i = 0; i < 4/*XXX: how to detect # ports?*/ && host->ports[i] != ap; ++i)
>  > 
>  > host->n_ports?
>  > 
>  > > +		;
>  > > +	if (i >= 4) {
>  > > +		printk(KERN_ERR "%s: unable to map ap to ata_no\n", __FUNCTION__);
>  > > +		return sata_std_hardreset(link, class, deadline);
>  > > +	}
>  > > +	ata_no = pdc_port_no_to_ata_no(i, is_sataii_tx4);
>  > > +
>  > > +	hotplug_status = readl(mmio_base + hotplug_offset);
>  > > +
>  > > +	/* clear hotplug flags, mask hotplug ints */
>  > > +	hotplug_status |= (0x11 << ata_no);
>  > > +	hotplug_status |= (0x11 << ata_no) << 16;
>  > > +	writel(hotplug_status, mmio_base + hotplug_offset);
>  > > +	readl(mmio_base + hotplug_offset); /* flush */
>  > 
>  > I think this belongs to ->freeze().
>  > 
>  > > +	ret = sata_std_hardreset(link, class, deadline);
>  > > +
>  > > +	/* clear hotplug flags, unmask hotplug ints */
>  > > +	hotplug_status &= ~((0x11 << ata_no) << 16);
>  > > +	writel(hotplug_status, mmio_base + hotplug_offset);
>  > > +	readl(mmio_base + hotplug_offset); /* flush */
>  > 
>  > And this to ->thaw().
> 
> Thanks, I'll try these suggestions. Expect a new patch in a couple of days.

I'll update the patchset such that promise won't use hardreset by
default so that cleanup-sht-ops patchset can go in.  I'll merge your
change when you're ready (shouldn't require too much massaging anyway).

Thanks.

-- 
tejun

      reply	other threads:[~2008-03-17  9:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11  4:27 [PATCHSET #upstream-fixes] block/libata: update and use block layer padding and draining, take 3 Tejun Heo
2008-03-11  4:27 ` [PATCH 1/5] libata: prefer hardreset Tejun Heo
2008-03-11  4:27 ` [PATCH 2/5] libata: kill ATA_LFLAG_HRST_TO_RESUME Tejun Heo
2008-03-11  4:27 ` [PATCH 3/5] libata: kill ATA_EHI_RESUME_LINK Tejun Heo
2008-03-11  4:27 ` [PATCH 4/5] libata: kill ATA_LFLAG_SKIP_D2H_BSY Tejun Heo
2008-03-11  4:27 ` [PATCH 5/5] libata: kill ata_ehi_schedule_probe() Tejun Heo
2008-03-11  4:29 ` Subject should be [PATCHSET libata-dev#upstream-fixes] libata: prefer hardreset, take #3 Tejun Heo
2008-03-16 22:07   ` Mikael Pettersson
2008-03-17  0:17     ` Tejun Heo
2008-03-17  8:19       ` Mikael Pettersson
2008-03-17  9:36         ` Tejun Heo [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=47DE3B94.2090501@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.