From: Mason <slash.tmp@free.fr>
To: Andy Gross <andy.gross@linaro.org>
Cc: Mans Rullgard <mans@mansr.com>,
linux-ide@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Christian Lamparter <chunkeey@gmail.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Kishon Vijay Abraham <kishon@ti.com>,
Sebastian Frias <sf84@laposte.net>
Subject: Re: sata_dwc_460ex driver
Date: Fri, 27 May 2016 20:41:31 +0200 [thread overview]
Message-ID: <574894DB.4090706@free.fr> (raw)
In-Reply-To: <CAPBZ5Qd5MFP+7fyRaGgnmLNu3--J=+ogs0nCD4pfoU27gPE+cg@mail.gmail.com>
On 27/05/2016 20:15, Andy Gross wrote:
> On 27 May 2016 at 11:56, Mason wrote:
>
>> How come there are so few phy drivers in drivers/phy if most
>> devices would typically require one?
>
> Short answer is that the generic phy framework is fairly recent
> (~3 years old). A lot of phys are stuck off in other places like
> drivers/usb/phy. At least that's my take on it.
<confused> Where did the SATA phy drivers use to live?
$ find -name phy
./drivers/usb/phy
./drivers/phy
./drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy
./drivers/net/phy
./drivers/gpu/drm/msm/dsi/phy
./include/linux/phy
./include/dt-bindings/phy
./Documentation/devicetree/bindings/phy
./Documentation/phy
drivers/ata/ahci.h mentions SATA phy registers.
Is AHCI standardized to the point that platform-specific PHYs
are not required?
Regards.
next prev parent reply other threads:[~2016-05-27 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:54 sata_dwc_460ex driver Mason
2016-05-27 16:20 ` Måns Rullgård
2016-05-27 16:56 ` Mason
2016-05-27 18:15 ` Andy Gross
2016-05-27 18:41 ` Mason [this message]
2016-05-27 18:46 ` Måns Rullgård
[not found] ` <CAAd0S9BQoLsz1226seRW697rzNC9=SJDRC=JR2s4242tyg1+4g@mail.gmail.com>
2016-05-27 17:33 ` Mason
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=574894DB.4090706@free.fr \
--to=slash.tmp@free.fr \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.gross@linaro.org \
--cc=chunkeey@gmail.com \
--cc=hdegoede@redhat.com \
--cc=kishon@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=mans@mansr.com \
--cc=sf84@laposte.net \
--cc=srinivas.kandagatla@linaro.org \
--cc=tj@kernel.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