From: Ansuel Smith <ansuelsmth@gmail.com>
To: devicetree@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Richard Zhu <hongxing.zhu@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Andrew Murray <amurray@thegoodpenguin.co.uk>,
Shawn Guo <shawnguo@kernel.org>,
Ansuel Smith <ansuelsmth@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Lucas Stach <l.stach@pengutronix.de>
Subject: [PATCH 0/4] Move tx-deempth and tx swing to pci.txt
Date: Fri, 10 Apr 2020 02:47:34 +0200 [thread overview]
Message-ID: <20200410004738.19668-1-ansuelsmth@gmail.com> (raw)
In pushing some fixes to pcie qcom driver, one of the patch had to make
some fixes to tx deempth and tx swing. It was suggested to propose this
to the generic pci.txt as they are actually standard parameter than can
be tuned per board. I also notice these property are already used in
imx6 driver so this would also help to generalize it.
Ansuel Smith (4):
devicetree: bindings: pci: document tx-deempth tx swing and rx-eq
property
drivers: pci: dwc: pci-imx6: update binding to generic name
arm: dts: imx6: update pci binding to generic name
devicetree: bindings: pci: fsl,imx6q-pcie: rename tx deemph and swing
.../devicetree/bindings/pci/fsl,imx6q-pcie.txt | 12 ++++++------
Documentation/devicetree/bindings/pci/pci.txt | 18 ++++++++++++++++++
arch/arm/boot/dts/imx6q-ba16.dtsi | 4 ++--
arch/arm/boot/dts/imx6qdl-var-dart.dtsi | 4 ++--
arch/arm/boot/dts/imx7d.dtsi | 2 +-
drivers/pci/controller/dwc/pci-imx6.c | 12 ++++++------
6 files changed, 35 insertions(+), 17 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-04-10 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 0:47 Ansuel Smith [this message]
2020-04-10 0:47 ` [PATCH 1/4] devicetree: bindings: pci: document tx-deempth tx swing and rx-eq property Ansuel Smith
2020-04-13 20:29 ` Florian Fainelli
2020-04-14 12:51 ` R: " ansuelsmth
2020-04-13 20:40 ` Bjorn Helgaas
2020-04-10 0:47 ` [PATCH 2/4] drivers: pci: dwc: pci-imx6: update binding to generic name Ansuel Smith
2020-04-10 2:24 ` Fabio Estevam
2020-04-10 11:07 ` R: " ansuelsmth
2020-04-10 12:31 ` Fabio Estevam
2020-04-10 12:40 ` R: " ansuelsmth
2020-04-10 12:57 ` Fabio Estevam
2020-04-13 20:25 ` Bjorn Helgaas
2020-04-10 0:47 ` [PATCH 3/4] arm: dts: imx6: update pci " Ansuel Smith
2020-04-10 0:47 ` [PATCH 4/4] devicetree: bindings: pci: fsl, imx6q-pcie: rename tx deemph and swing Ansuel Smith
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=20200410004738.19668-1-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).