linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cbouatmailru@gmail.com (Anton Vorontsov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V7 1/5] AHCI Add the AHCI SATA feature on the MX53 platforms
Date: Thu, 22 Sep 2011 22:31:17 +0400	[thread overview]
Message-ID: <20110922183117.GA17600@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <CAJNCFVLm=bUMvXq7acke7Bd_tiV+b1=HjVp37KwtYyGsZHa+OQ@mail.gmail.com>

Hi Richard,

On Wed, Sep 21, 2011 at 03:05:44PM +0800, Richard Zhu wrote:
> Hi Sascha:
> One proposal about how to convert the ahci driver to devicetree in future.
> ahci driver system can make a reference to the evolution of the sdhc driver.

You don't need to "convert" ahci driver to devicetree. IIRC,
the current ahci_platform driver should work almost* out of
the box with OF-enabled architectures, as OF subsystem
automatically populates memory and interrupt resources for
platform devices.

Someday you might need to implement OF-specific bindings
(e.g. get some property from the device tree and translate
it into port flags). When/if you'll need it, you can just
add it into the driver.

* Almost: you have to add of_match_table into 'struct
  platform_driver ahci_driver'.

> * separate the ahci to ahci common codes, ahci-pci driver and
> ahci-platform driver.

Done. Long time ago, actually.

> * create kinds of ahci vendor's own ahci platform driver refer to the
> sdhci-xxx driver solutions.

I think that this is viable, but personally I would like to
see platforms to just pass port flags and all needed hooks
via platform_data. That is, I'd leave the hooks in the arch/
code. Usually these hooks are very arch-specific (i.e. enable
these and these clocks, etc), so arch/ seems like a perfect
place for such things.

Not a strong opinion though, and if you like to go your route,
I'm also fine with this. It has its own pros (and cons).

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru at gmail.com

  parent reply	other threads:[~2011-09-22 18:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31  3:50 [PATCH V7 0/5] imx53 ahci driver v7 Richard Zhu
2011-08-31  3:50 ` [PATCH V7 1/5] AHCI Add the AHCI SATA feature on the MX53 platforms Richard Zhu
2011-08-31 10:03   ` Arnaud Patard (Rtp)
2011-08-31 11:04     ` Eric Miao
2011-09-20 20:30   ` Sascha Hauer
2011-09-21  5:04     ` Richard Zhu
2011-09-21  7:02       ` Sascha Hauer
2011-09-21  7:32         ` Shawn Guo
2011-09-21  7:05       ` Richard Zhu
2011-09-22 18:12         ` Jeff Garzik
2011-09-22 18:31         ` Anton Vorontsov [this message]
2011-08-31  3:50 ` [PATCH V7 2/5] ahci_plt Add the board_ids and pi refer to different features Richard Zhu
2011-08-31  8:28   ` Eric Miao
2011-08-31  3:50 ` [PATCH V7 3/5] MX53 Enable the AHCI SATA on MX53 ARD board Richard Zhu
2011-08-31  3:50 ` [PATCH V7 4/5] MX53 Enable the AHCI SATA on MX53 LOCO board Richard Zhu
2011-08-31  3:50 ` [PATCH V7 5/5] MX53 Enable the AHCI SATA on MX53 SMD board Richard Zhu
2011-08-31  6:55 ` [PATCH V7 0/5] imx53 ahci driver v7 Arnaud Patard (Rtp)
2011-08-31  7:16   ` Richard Zhu
  -- strict thread matches above, loose matches on Subject: below --
2011-08-30  9:56 [PATCH V7 1/5] AHCI Add the AHCI SATA feature on the MX53 platforms Richard Zhu
2011-08-30 10:37 ` Wolfram Sang
2011-08-30 10:43 ` Hector Oron
2011-08-31  2:08   ` Richard Zhu
2011-08-31 12:57     ` Hector Oron
2011-09-01  3:09       ` Richard Zhu
2011-09-05 18:06         ` Eric Miao
2011-09-06  8:46         ` Hector Oron
2011-09-06 13:25           ` Eric Miao
2011-09-22  9:30             ` Hector Oron
2011-09-22 12:19               ` Eric Miao
2011-09-23  8:58                 ` Hector Oron
2011-09-05 19:25       ` Arnaud Patard (Rtp)

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=20110922183117.GA17600@oksana.dev.rtsoft.ru \
    --to=cbouatmailru@gmail.com \
    --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).