From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>
Cc: bcm-kernel-feedback-list@broadcom.com,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] phy: phy-brcm-sata: Allow configuration SATA AFE TX amplitude
Date: Tue, 10 Nov 2020 09:48:59 -0800 [thread overview]
Message-ID: <b90a9f8f-6469-a4cb-e17f-4db7e05a5d3b@gmail.com> (raw)
In-Reply-To: <20201022205056.233879-1-f.fainelli@gmail.com>
On 10/22/20 1:50 PM, Florian Fainelli wrote:
> Hi Vinod, Kishon,
>
> This patch series allows the configuration of the Broadcom SATA PHY TX
> amplitude which may be required in order to meet specific tests.
>
> Thanks!
>
> Changes in v2:
Vinod, Kishon, can this be applied if you are okay with the changes?
Thank you!
>
> - rebased against phy/next
> - added Rob's Acked-by to the dt-binding patch
>
> Florian Fainelli (2):
> dt-bindings: phy: Allow defining the SATA AFE TX amplitude
> phy: phy-brcm-sata: Allow configuration SATA AFE TX amplitude
>
> .../devicetree/bindings/phy/brcm-sata-phy.txt | 3 ++
> drivers/phy/broadcom/phy-brcm-sata.c | 32 +++++++++++++++++++
> 2 files changed, 35 insertions(+)
>
--
Florian
next prev parent reply other threads:[~2020-11-10 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 20:50 [PATCH v2 0/2] phy: phy-brcm-sata: Allow configuration SATA AFE TX amplitude Florian Fainelli
2020-10-22 20:50 ` [PATCH v2 1/2] dt-bindings: phy: Allow defining the " Florian Fainelli
2020-10-22 20:50 ` [PATCH v2 2/2] phy: phy-brcm-sata: Allow configuration " Florian Fainelli
2020-11-10 17:48 ` Florian Fainelli [this message]
2020-11-16 7:42 ` [PATCH v2 0/2] " Vinod Koul
2020-11-16 22:51 ` Florian Fainelli
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=b90a9f8f-6469-a4cb-e17f-4db7e05a5d3b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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).