From: <kostap@marvell.com>
To: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <lkundrak@v3.sk>, <linux@armlinux.org.uk>,
<sebastian.hesselbarth@gmail.com>, <gregory.clement@bootlin.com>,
<andrew@lunn.ch>, <robh+dt@kernel.org>, <vkoul@kernel.org>,
<kishon@ti.com>, <miquel.raynal@bootlin.com>, <mw@semihalf.com>,
<jaz@semihalf.com>, <nadavh@marvell.com>, <stefanc@marvell.com>,
<bpeled@marvell.com>,
"Konstantin Porotchkin" <kostap@marvell.com>
Subject: [PATCH v2 0/4] Add support for CP110 UTMI PHY
Date: Sun, 14 Feb 2021 18:01:04 +0200 [thread overview]
Message-ID: <20210214160108.3879-1-kostap@marvell.com> (raw)
From: Konstantin Porotchkin <kostap@marvell.com>
This series of patches adds a new PHY driver for supporting CP110 UTMI
PHY in Linux. Currently the functionality of USB ports connected to
this PHY depends on boot loader setup.
The new driver eliminates kernel configuration dependency from the boot
loader.
v2:
- extend the comment about reference clock
- fix driver probe function, add some prints
- move to usage of dr_mode from connected USB controller instead of
dedicated device tree property
Konstantin Porotchkin (4):
drivers: phy: add support for Armada CP110 UTMI PHY
devicetree/bindings: add support for CP110 UTMI driver
arch/arm64: dts: add support for Marvell CP110 UTMI driver
arch/arm64: dts: enable CP110 UTMI driver
.../bindings/phy/phy-mvebu-utmi.txt | 78 +++-
.../arm64/boot/dts/marvell/armada-7040-db.dts | 14 +-
.../arm64/boot/dts/marvell/armada-8040-db.dts | 21 +-
.../boot/dts/marvell/armada-8040-mcbin.dtsi | 19 +-
arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 19 +
arch/arm64/boot/dts/marvell/cn9130-db.dts | 12 +-
arch/arm64/boot/dts/marvell/cn9131-db.dts | 9 +-
arch/arm64/boot/dts/marvell/cn9132-db.dts | 11 +-
drivers/phy/marvell/Kconfig | 8 +
drivers/phy/marvell/Makefile | 1 +
drivers/phy/marvell/phy-mvebu-cp110-utmi.c | 384 ++++++++++++++++++
11 files changed, 556 insertions(+), 20 deletions(-)
create mode 100644 drivers/phy/marvell/phy-mvebu-cp110-utmi.c
--
2.17.1
next reply other threads:[~2021-02-14 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 16:01 kostap [this message]
2021-02-14 16:01 ` [PATCH v2 1/4] drivers: phy: add support for Armada CP110 UTMI PHY kostap
2021-02-21 13:12 ` kernel test robot
2021-02-21 13:23 ` kernel test robot
2021-02-14 16:01 ` [PATCH v2 2/4] devicetree/bindings: add support for CP110 UTMI driver kostap
2021-03-05 21:34 ` Rob Herring
2021-02-14 16:01 ` [PATCH v2 3/4] arch/arm64: dts: add support for Marvell " kostap
2021-02-14 16:01 ` [PATCH v2 4/4] arch/arm64: dts: enable " kostap
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=20210214160108.3879-1-kostap@marvell.com \
--to=kostap@marvell.com \
--cc=andrew@lunn.ch \
--cc=bpeled@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jaz@semihalf.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkundrak@v3.sk \
--cc=miquel.raynal@bootlin.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stefanc@marvell.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).