From: Mikko Perttunen <mikko.perttunen@kapsi.fi>
To: Stephen Warren <swarren@wwwdotorg.org>,
Jon Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Andrew Bresticker <abrestic@chromium.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [RFC PATCH] dt: Tegra XUSB padctl: per-lane PHYs and USB lane map
Date: Thu, 22 Oct 2015 16:03:01 +0300 [thread overview]
Message-ID: <5628DE85.3010808@kapsi.fi> (raw)
In-Reply-To: <5626641C.8040009@wwwdotorg.org>
On 10/20/2015 06:56 PM, Stephen Warren wrote:
> ...
>
> In drivers/pci/host/pci-tegra.c tegra_pcie_get_resources() I see a call
> to devm_phy_optional_get().
>
> The SATA driver doesn't seem to do anything with phys at the moment,
> although tegra124.dtsi does put phy-related properties into the SATA DT
> node.
FWIW, the SATA driver does use the PHY - just through the
ahci_platform_{get,enable,...}_resources API. (so is life..)
Mikko
>
> So, we can either:
> a) Just ignore DT ABI for these cases claiming the DT binding is not yet
> declared stable.
>
> b) Continue to support those specifier values for ABI reasons, which
> needs the "_LEGACY" values shown above.
>
> (a) is certainly simpler.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-22 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 23:30 [RFC PATCH] dt: Tegra XUSB padctl: per-lane PHYs and USB lane map Stephen Warren
2015-10-20 10:10 ` Jon Hunter
2015-10-20 15:56 ` Stephen Warren
2015-10-22 13:03 ` Mikko Perttunen [this message]
2015-10-21 12:15 ` Thierry Reding
2015-10-21 17:40 ` Stephen Warren
2015-10-21 20:10 ` Kishon Vijay Abraham I
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=5628DE85.3010808@kapsi.fi \
--to=mikko.perttunen@kapsi.fi \
--cc=abrestic@chromium.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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).