From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: "A.s. Dong" <aisheng.dong@nxp.com>
Cc: "dongas86@gmail.com" <dongas86@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Stefan Agner <stefan@agner.ch>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 4/8] gpio: vf610: add optional clock support
Date: Tue, 23 Oct 2018 13:04:02 +0100 [thread overview]
Message-ID: <20181023120401.GO30658@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1540295058-26090-5-git-send-email-aisheng.dong@nxp.com>
On Tue, Oct 23, 2018 at 11:49:17AM +0000, A.s. Dong wrote:
> + clk_gpio = devm_clk_get(&pdev->dev, "gpio");
> + clk_port = devm_clk_get(&pdev->dev, "port");
> + if ((PTR_ERR(clk_gpio) == -EPROBE_DEFER) ||
> + (PTR_ERR(clk_port) == -EPROBE_DEFER)) {
if (clk_gpio == ERR_PTR(-EPROBE_DEFER) ||
clk_port == ERR_PTR(-EPROBE_DEFER)) {
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2018-10-23 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1540295058-26090-1-git-send-email-aisheng.dong@nxp.com>
2018-10-23 11:49 ` [PATCH V2 3/8] dt-bindings: gpio: vf610: add optional clocks property A.s. Dong
2018-10-24 21:55 ` Rob Herring
2018-10-23 11:49 ` [PATCH V2 4/8] gpio: vf610: add optional clock support A.s. Dong
2018-10-23 12:04 ` Russell King - ARM Linux [this message]
2018-10-23 12:23 ` A.s. Dong
2018-10-23 12:41 ` Uwe Kleine-König
2018-10-23 13:39 ` A.s. Dong
2018-10-25 17:58 ` Stefan Agner
2018-10-26 3:49 ` A.s. Dong
2018-10-26 8:15 ` Stefan Agner
2018-10-30 15:34 ` A.s. Dong
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=20181023120401.GO30658@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=aisheng.dong@nxp.com \
--cc=dongas86@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).