From: Florian Fainelli <f.fainelli@gmail.com>
To: kishon@ti.com
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Jens Axboe <axboe@kernel.dk>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Al Cooper <alcooperx@gmail.com>, Ray Jui <ray.jui@broadcom.com>,
Tejun Heo <tj@kernel.org>, Fengguang Wu <fengguang.wu@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-ide@vger.kernel.org (open list:LIBATA SUBSYSTEM (Serial
and Parallel ATA drivers)),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list),
bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH 0/2] phy: brcm-sata: Support for 7216
Date: Tue, 10 Dec 2019 12:08:50 -0800 [thread overview]
Message-ID: <20191210200852.24945-1-f.fainelli@gmail.com> (raw)
Hi Kishon,
This patch series adds support for our latest 7216 class of devices
which are taped out in a 16nm process and use a different SATA PHY AFE
that requires a custom initialization sequence.
Thanks!
Florian Fainelli (2):
dt-bindings: phy: Document BCM7216 SATA PHY compatible string
phy: brcm-sata: Implement 7216 initialization sequence
.../devicetree/bindings/phy/brcm-sata-phy.txt | 1 +
drivers/phy/broadcom/phy-brcm-sata.c | 120 ++++++++++++++++++
2 files changed, 121 insertions(+)
--
2.17.1
next reply other threads:[~2019-12-10 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 20:08 Florian Fainelli [this message]
2019-12-10 20:08 ` [PATCH 1/2] dt-bindings: phy: Document BCM7216 SATA PHY compatible string Florian Fainelli
2019-12-19 20:40 ` Rob Herring
2019-12-10 20:08 ` [PATCH 2/2] phy: brcm-sata: Implement 7216 initialization sequence Florian Fainelli
2019-12-27 3:36 ` [PATCH 0/2] phy: brcm-sata: Support for 7216 Florian Fainelli
2019-12-30 11:51 ` 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=20191210200852.24945-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alcooperx@gmail.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=kishon@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ray.jui@broadcom.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).