linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4 v2] ARM: dts: add Gemini PATA/SATA support
Date: Sat, 20 May 2017 10:27:41 +0200	[thread overview]
Message-ID: <CACRpkdbubStWj+K0eORLXRfZCWAVHs4aC5yDaUzPCPkWLcenoA@mail.gmail.com> (raw)
In-Reply-To: <20170519230600.16782-4-linus.walleij@linaro.org>

On Sat, May 20, 2017 at 1:06 AM, Linus Walleij <linus.walleij@linaro.org> wrote:

> The NAS4229B and SQ201 Gemini systems have a PATA controller
> which is linked to a SATA bridge in the SoC. Enable both
> platforms to use the PATA/SATA devices.
>
> Cc: John Feng-Hsin Chiang <john453@faraday-tech.com>
> Cc: Greentime Hu <green.hu@gmail.com>
> Acked-by: Hans Ulli Kroll <ulli.kroll@googlemail.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Cut the timings

(...)

> +               ata at 63400000 {
(...)
> +                       /* PIO timings assume 33 MHz bus speed */
> +                       faraday,pio-active-time = <10>, <10>, <10>, <3>, <3>;
> +                       faraday,pio-recovery-time = <10>, <3>, <1>, <3>, <1>;
(...)

OK I forgot to cut the timings on the second instance, sorry.
I have removed them now so they are not there when I send this
to the ARM SoC tree.

Yours,
Linus Walleij

      reply	other threads:[~2017-05-20  8:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 23:05 [PATCH 1/4 v2] ata: Add DT bindings for Faraday Technology FTIDE010 Linus Walleij
2017-05-19 23:05 ` [PATCH 2/4 v2] ata: Add DT bindings for the Gemini SATA bridge Linus Walleij
2017-05-19 23:05 ` [PATCH 3/4 v2] ata: Add driver for Faraday Technology FTIDE010 Linus Walleij
2017-05-23 21:25   ` Tejun Heo
2017-05-30 11:28     ` Linus Walleij
2017-05-19 23:06 ` [PATCH 4/4 v2] ARM: dts: add Gemini PATA/SATA support Linus Walleij
2017-05-20  8:27   ` Linus Walleij [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=CACRpkdbubStWj+K0eORLXRfZCWAVHs4aC5yDaUzPCPkWLcenoA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).