From: Kishon Vijay Abraham I <kishon@ti.com>
To: <linux-kernel@vger.kernel.org>, <kishon@ti.com>
Cc: <rogerq@ti.com>, <devicetree@vger.kernel.org>,
<robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <tony@atomide.com>, <nsekhar@ti.com>
Subject: [PATCH v2 0/9] phy: use syscon framework APIs to set ctrl mod reg
Date: Tue, 15 Sep 2015 18:34:22 +0530 [thread overview]
Message-ID: <1442322271-26230-1-git-send-email-kishon@ti.com> (raw)
This series is basically to deprecate using phy-omap-control and use
syscon APIs to program the control module registers.
Changes from v1:
*) cleanup ti_pipe3_probe in multiple steps
*) other minor cleanups
Changes from [1] in PHY patches include
*) cleanup ti_pipe3_probe
*) have mask, power_on and power_off values in usb_phy_data for
omap-usb2 phy
Did basic enumeration testing to make sure the patch series doesn't
cause any regressions.
All the testing was done both before applying the dt patches and after
applying the dt patches (dt patches will be posted shortly).
[1] -> https://lkml.org/lkml/2015/6/23/189
Kishon Vijay Abraham I (9):
phy: ti-pipe3: introduce local struct device* in probe
phy: ti-pipe3: move clk initialization to a separate function
phy: ti-pipe3: move sysctrl initialization to a separate function
phy: ti-pipe3: move mem resource initialization to a separate
function
phy: ti-pipe3: use ti_pipe3_power_off to power off the PHY during
probe
phy: ti-pipe3: use *syscon* framework API to power on/off the PHY
phy: ti-pipe3: use *syscon* framework API to set PCS value of the PHY
phy: omap-usb2: use omap_usb_power_off to power off the PHY during
probe
phy: omap-usb2: use *syscon* framework API to power on/off the PHY
Documentation/devicetree/bindings/phy/ti-phy.txt | 20 +-
drivers/phy/phy-omap-usb2.c | 96 +++++--
drivers/phy/phy-ti-pipe3.c | 304 ++++++++++++++++------
include/linux/phy/omap_usb.h | 23 ++
4 files changed, 340 insertions(+), 103 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-09-15 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 13:04 Kishon Vijay Abraham I [this message]
2015-09-15 13:04 ` [PATCH v2 1/9] phy: ti-pipe3: introduce local struct device* in probe Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 2/9] phy: ti-pipe3: move clk initialization to a separate function Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 3/9] phy: ti-pipe3: move sysctrl " Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 4/9] phy: ti-pipe3: move mem resource " Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 5/9] phy: ti-pipe3: use ti_pipe3_power_off to power off the PHY during probe Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 6/9] phy: ti-pipe3: use *syscon* framework API to power on/off the PHY Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 7/9] phy: ti-pipe3: use *syscon* framework API to set PCS value of " Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 8/9] phy: omap-usb2: use omap_usb_power_off to power off the PHY during probe Kishon Vijay Abraham I
2015-09-15 13:04 ` [PATCH v2 9/9] phy: omap-usb2: use *syscon* framework API to power on/off the PHY 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=1442322271-26230-1-git-send-email-kishon@ti.com \
--to=kishon@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=tony@atomide.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
Powered by JetHome