From: "Andreas Färber" <afaerber@suse.de>
To: "Guido Günther" <agx@sigxcpu.org>,
"Robert Chiras" <robert.chiras@nxp.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Thierry Reding <treding@nvidia.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Heiko Stuebner <heiko@sntech.de>, Johan Hovold <johan@kernel.org>,
Lucas Stach <l.stach@pengutronix.de>,
Abel Vesa <abel.vesa@nxp.com>, Li Jun <jun.li@nxp.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, Sam Ravnborg <sam@ravnborg.org>,
Maxime Ripard <maxime.ripard@bootlin.com>
Subject: Re: [PATCH v9 2/2] phy: Add driver for mixel mipi dphy found on NXP's i.MX8 SoCs
Date: Thu, 2 May 2019 17:36:25 +0200 [thread overview]
Message-ID: <4ce62b78-64ac-ca84-733f-bc4d10a67c54@suse.de> (raw)
In-Reply-To: <b999b07673e59c676d2e43a786b635beb056e9bf.1556633413.git.agx@sigxcpu.org>
Am 30.04.19 um 16:40 schrieb Guido Günther:
> This adds support for the Mixel DPHY as found on i.MX8 CPUs but since
> this is an IP core it will likely be found on others in the future. So
> instead of adding this to the nwl host driver make it a generic PHY
> driver.
>
> The driver supports the i.MX8MQ. Support for i.MX8QM and i.MX8QXP can be
> added once the necessary system controller bits are in via
> mixel_dphy_devdata.
>
> Co-authored-by: Robert Chiras <robert.chiras@nxp.com>
This should be Co-developed-by and is lacking a Signed-off-by from that
author. Robert, can you please provide one?
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
> Signed-off-by: Guido Günther <agx@sigxcpu.org>
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-05-02 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 14:40 [PATCH v9 0/2] Mixel MIPI DPHY support for NXPs i.MX8 SOCs Guido Günther
2019-04-30 14:40 ` [PATCH v9 1/2] dt-bindings: phy: Add documentation for mixel dphy Guido Günther
2019-04-30 14:40 ` [PATCH v9 2/2] phy: Add driver for mixel mipi dphy found on NXP's i.MX8 SoCs Guido Günther
2019-04-30 16:24 ` Fabio Estevam
2019-04-30 16:58 ` Guido Günther
2019-04-30 20:31 ` Sam Ravnborg
2019-05-02 15:11 ` Guido Günther
2019-05-02 15:36 ` Andreas Färber [this message]
2019-05-06 6:54 ` [EXT] " Robert Chiras
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=4ce62b78-64ac-ca84-733f-bc4d10a67c54@suse.de \
--to=afaerber@suse.de \
--cc=abel.vesa@nxp.com \
--cc=agx@sigxcpu.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=heiko@sntech.de \
--cc=johan@kernel.org \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=maxime.ripard@bootlin.com \
--cc=robert.chiras@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=shawnguo@kernel.org \
--cc=treding@nvidia.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