public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/4] pata: imx: set timings for PIO modes up to PIO4
Date: Wed, 9 Nov 2016 11:49:51 -0500	[thread overview]
Message-ID: <20161109164951.GB14630@htj.duckdns.org> (raw)
In-Reply-To: <20161109005638.17691-1-vz@mleia.com>

On Wed, Nov 09, 2016 at 02:56:34AM +0200, Vladimir Zapolskiy wrote:
> The changeset adds support of PIO modes up to PIO4 by setting
> necessary timings in the driver, before the change it is assumed
> that the timings are always set by a bootloader once and thus
> only one possible PIO mode has been supported (PIO0). With
> this change the driver can be used on boards without ATA controller
> configuration done by a bootloader.
> 
> The change is tested on a legacy i.MX31 board with an HDD connected
> by a 40-pin flat cable.

Applied to libata/for-4.10.

Thanks.

-- 
tejun

      parent reply	other threads:[~2016-11-09 16:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  0:56 [PATCH 0/4] pata: imx: set timings for PIO modes up to PIO4 Vladimir Zapolskiy
2016-11-09  0:56 ` [PATCH 1/4] pata: imx: sort headers out Vladimir Zapolskiy
2016-11-09  0:56 ` [PATCH 2/4] pata: imx: set controller PIO mode with .set_piomode callback Vladimir Zapolskiy
2016-11-09  0:56 ` [PATCH 3/4] pata: imx: add support of setting timings for PIO modes Vladimir Zapolskiy
2016-11-09  9:39   ` Sergei Shtylyov
2016-11-10  1:33     ` Vladimir Zapolskiy
2016-11-10 16:10       ` Tejun Heo
2016-11-14 14:22   ` Bartlomiej Zolnierkiewicz
2016-11-09  0:56 ` [PATCH 4/4] pata: imx: support controller modes up to PIO4 Vladimir Zapolskiy
2016-11-09 16:49 ` 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=20161109164951.GB14630@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=vz@mleia.com \
    /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