From: Arnd Bergmann <arnd@arndb.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"DCG_UPD_stlinux_kernel@list.st.com"
<DCG_UPD_stlinux_kernel@list.st.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@st.com>
Subject: Re: [PATCH v2 1/3] ata: ahci_st: Provide DT bindings for ST's SATA implementation
Date: Wed, 12 Mar 2014 19:59:52 +0100 [thread overview]
Message-ID: <5284929.ZWl2X8pt1x@wuerfel> (raw)
In-Reply-To: <20140312171452.GE22450@lee--X1>
On Wednesday 12 March 2014 17:14:52 Lee Jones wrote:
> > > > > +This binding describes a SATA device.
> > > > > +
> > > > > +Required properties:
> > > > > + - compatible : Must be "st,ahci"
> > > >
> > > > Is there not a more specific name? This is awfully generic.
> > >
> > > There isn't one. ST only have one AHCI driver. The driver is named as
> > > generically.
> >
> > If it is this generic, can't you use the completely generic
> > ahci-platform driver and add a "generic-ahci" compatible string
> > to that?
>
> It pretty much does. The only 'special' functionality we handle in
> the driver are resets and configuring the OOB. However, both are
> required.
The reset handling should be easy to add to the generic driver
usign as an optional property if I'm not mistaken.
What is OOB?
Arnd
prev parent reply other threads:[~2014-03-12 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 11:41 [PATCH v2 1/3] ata: ahci_st: Provide DT bindings for ST's SATA implementation Lee Jones
2014-02-25 11:41 ` [PATCH v2 2/3] ARM: DT: STi: Add DT node for ST's SATA device Lee Jones
[not found] ` <1393328481-7251-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-03-12 11:42 ` [PATCH v2 1/3] ata: ahci_st: Provide DT bindings for ST's SATA implementation Mark Rutland
2014-03-12 12:48 ` Lee Jones
2014-03-12 16:06 ` Arnd Bergmann
2014-03-12 17:14 ` Lee Jones
2014-03-12 18:59 ` Arnd Bergmann [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=5284929.ZWl2X8pt1x@wuerfel \
--to=arnd@arndb.de \
--cc=DCG_UPD_stlinux_kernel@list.st.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=srinivas.kandagatla@st.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;
as well as URLs for NNTP newsgroup(s).