From: <Lewis.Hanly@microchip.com>
To: <linux-riscv@lists.infradead.org>,
<christophe.jaillet@wanadoo.fr>, <brgl@bgdev.pl>,
<linux-gpio@vger.kernel.org>, <linus.walleij@linaro.org>,
<linux-kernel@vger.kernel.org>, <maz@kernel.org>,
<palmer@dabbelt.com>
Cc: <Conor.Dooley@microchip.com>, <Daire.McNamara@microchip.com>
Subject: Re: [PATCH v5 1/1] gpio: mpfs: add polarfire soc gpio support
Date: Mon, 15 Aug 2022 12:04:58 +0000 [thread overview]
Message-ID: <22cfe2a9dc4e4a9f2ddf34474c685a5fb87313e7.camel@microchip.com> (raw)
In-Reply-To: <271c00a5-fb5d-ff9e-3c4d-ec2732b991ba@wanadoo.fr>
On Mon, 2022-08-15 at 09:38 +0200, Christophe JAILLET wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> Le 15/08/2022 à 09:06, lewis.hanly@microchip.com a écrit :
> > From: Lewis Hanly <lewis.hanly@microchip.com>
> >
> > Add a driver to support the Polarfire SoC gpio controller
> >
> > Signed-off-by: Lewis Hanly <lewis.hanly@microchip.com>
> > ---
> > drivers/gpio/Kconfig | 7 +
> > drivers/gpio/Makefile | 1 +
> > drivers/gpio/gpio-mpfs.c | 318
> > +++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 326 insertions(+)
> > create mode 100644 drivers/gpio/gpio-mpfs.c
> >
> > +static int mpfs_gpio_probe(struct platform_device *pdev)
> > +{
> > + struct clk *clk;
> > + struct device *dev = &pdev->dev;
> > + struct device_node *node = pdev->dev.of_node;
> > + struct mpfs_gpio_chip *mpfs_gpio;
> > + struct gpio_irq_chip *girq;
> > + int i, ret, ngpios, nirqs;
> > +
> > + mpfs_gpio = devm_kzalloc(dev, sizeof(*mpfs_gpio),
> > GFP_KERNEL);
> > + if (!mpfs_gpio)
> > + return -ENOMEM;
> > +
> > + mpfs_gpio->base = devm_platform_ioremap_resource(pdev, 0);
> > + if (IS_ERR(mpfs_gpio->base))
> > + return dev_err_probe(dev, PTR_ERR(mpfs_gpio->clk),
> > "input clock not found.\n");
>
> PTR_ERR(mpfs_gpio->base)?
> "input clock not found" also looks odd after a
> devm_platform_ioremap_resource() call.
Yes, thank you, have fixed in a v6 which is on way.
>
> > +
> > + clk = devm_clk_get(dev, NULL);
> > + if (IS_ERR(clk))
> > + return dev_err_probe(dev, PTR_ERR(clk), "devm_clk_get
> > failed\n");
> > +
next prev parent reply other threads:[~2022-08-15 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 7:06 [PATCH v5 0/1] Add Polarfire SoC GPIO support lewis.hanly
2022-08-15 7:06 ` [PATCH v5 1/1] gpio: mpfs: add polarfire soc gpio support lewis.hanly
2022-08-15 7:38 ` Christophe JAILLET
2022-08-15 12:04 ` Lewis.Hanly [this message]
2022-08-15 11:39 ` kernel test robot
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=22cfe2a9dc4e4a9f2ddf34474c685a5fb87313e7.camel@microchip.com \
--to=lewis.hanly@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=brgl@bgdev.pl \
--cc=christophe.jaillet@wanadoo.fr \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.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;
as well as URLs for NNTP newsgroup(s).