devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Y Vo <yvo@apm.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>, Phong Vo <pvo@apm.com>,
	Toan Le <toanle@apm.com>, patches <patches@apm.com>
Subject: Re: [PATCH v2 RESEND 1/3] gpio: Add APM X-Gene standby GPIO controller driver
Date: Wed, 14 Jan 2015 15:27:55 +0700	[thread overview]
Message-ID: <CAL4ahLfGNc1sL-hr7bZi_pcxjz7CNHjPRSPnJf_TUCGsbweaDA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZe7Huiruu-iSNU4MWaiLo_qL=QAab1crummuuVOEJ0zQ@mail.gmail.com>

On Tue, Jan 13, 2015 at 4:40 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Wed, Dec 17, 2014 at 6:10 AM, Y Vo <yvo@apm.com> wrote:
>
>> Add APM X-Gene standby GPIO controller driver.
>
> Write something about what platform an arch this is and so
> on, this is too terse commit message for a new driver.
>
>> Signed-off-by: Y Vo <yvo@apm.com>
> (...)
>
>> +config GPIO_XGENE_SB
>> +       tristate "APM X-Gene GPIO standby controller support"
>> +       depends on ARCH_XGENE && OF_GPIO
>
> select GPIO_GENERIC
Why ?
> see below on why.
>
>> +       help
>> +         This driver supports the GPIO block within the APM X-Gene
>> +         Standby Domain. Say yes here to enable the GPIO functionality.
>> +
>>  config GPIO_XILINX
>>         bool "Xilinx GPIO support"
>>         depends on PPC_OF || MICROBLAZE || ARCH_ZYNQ
>> diff --git a/drivers/gpio/gpio-xgene-sb.c b/drivers/gpio/gpio-xgene-sb.c
>> new file mode 100644
>> index 0000000..1248448
>
> (...)
>> +++ b/drivers/gpio/gpio-xgene-sb.c
>> +#include <linux/module.h>
>> +#include <linux/io.h>
>> +#include <linux/platform_device.h>
>> +#include <linux/of_gpio.h>
>> +#include <linux/gpio.h>
>
> #include <linux/gpio/driver.h>
>
> instead.
>
>> +#include <linux/of_irq.h>
>> +#include <linux/acpi.h>
OK.

> OK, why?
>
>> +#include <linux/efi.h>
I will remove.

> Why?
>
>> +#include <linux/string.h>
>> +#include <linux/of_address.h>

I will remove.

> #include <linux/basic_mmio_gpio.h>
> when you start using GENERIC_GPIO
>
>> +
>> +#define XGENE_MAX_GPIO_DS              22
>> +#define XGENE_MAX_GPIO_DS_IRQ          6
>> +
>> +#define GPIO_MASK(x)                   (1U << ((x) % 32))
>> +#define GPIO_DIR_IN                    0
>> +#define GPIO_DIR_OUT                   1
>> +
>> +#define MPA_GPIO_INT_LVL               0x0290
>> +#define MPA_GPIO_OE_ADDR               0x029c
>> +#define MPA_GPIO_OUT_ADDR              0x02a0
>> +#define MPA_GPIO_IN_ADDR               0x02a4
>> +#define MPA_GPIO_SEL_LO                        0x0294
>> +#define MPA_GPIO_SEL_HIGH              0x029c
>> +
>> +struct xgene_gpio_sb {
>> +       struct of_mm_gpio_chip mm;
>> +       u32 *irq;
>> +       u32 nirq;
>> +       spinlock_t lock; /* mutual exclusion */
>> +};
>
> Add kerneldoc to this struct.
>
>> +static void xgene_gpio_set_bit(void __iomem *reg, u32 gpio, int val)
> (...)
>> +static int xgene_gpio_sb_get(struct gpio_chip *gc, u32 gpio)
>
> This looks very much like a memory-mapped standard GPIO controller,
> use drivers/gpio/gpio-generic.c with some IRQ add-on, compare
> to any other driver selecting GPIO_GENERIC for guidance:
> drivers/gpio/gpio-74xx-mmio.c, gpio-dwapb.c etc.
You mean I must rewrite to use GPIO_GENERIC follow gpio-74xx-mmio.c,
gpio-dwapb.c ?

>> +static int apm_gpio_sb_to_irq(struct gpio_chip *gc, u32 gpio)
>> +{
>> +       struct of_mm_gpio_chip *mm_gc = to_of_mm_gpio_chip(gc);
>> +       struct xgene_gpio_sb *chip = to_xgene_gpio_sb(mm_gc);
>> +
>> +       if (chip->irq[gpio])
>> +               return chip->irq[gpio];
>> +
>> +       return -ENXIO;
>> +}
>> +
>> +static int xgene_gpio_sb_probe(struct platform_device *pdev)
>> +{
>> +       struct of_mm_gpio_chip *mm;
>> +       struct xgene_gpio_sb *apm_gc;
>> +       u32 ret, i;
>> +       u32 default_pins[] = {0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D};
>
> Um, pins... call these "lines" instead to avoid confusion with the pin
> control subsystem.

I will change.

>> +       struct resource *res;
>> +
>> +       apm_gc = devm_kzalloc(&pdev->dev, sizeof(*apm_gc), GFP_KERNEL);
>> +       if (!apm_gc)
>> +               return -ENOMEM;
>> +
>> +       mm = &apm_gc->mm;
>> +       mm->gc.direction_input = xgene_gpio_sb_dir_in;
>> +       mm->gc.direction_output = xgene_gpio_sb_dir_out;
>> +       mm->gc.get = xgene_gpio_sb_get;
>> +       mm->gc.set = xgene_gpio_sb_set;
>> +       mm->gc.to_irq = apm_gpio_sb_to_irq;
>> +       mm->gc.base = -1;
>> +       mm->gc.label = dev_name(&pdev->dev);
>
> gc has a device tree .np node and a .dev struct device *
> pointer, assign them here. (Also after you switch to GENERIC_GPIO.)
>
> Yours,
> Linus Walleij

  reply	other threads:[~2015-01-14  8:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  5:10 [PATCH v2 RESEND 0/3] gpio: Add APM X-Gene standy platform GPIO driver Y Vo
2014-12-17  5:10 ` [PATCH v2 RESEND 1/3] gpio: Add APM X-Gene standby GPIO controller driver Y Vo
2015-01-13  9:40   ` Linus Walleij
2015-01-14  8:27     ` Y Vo [this message]
2015-01-16 15:19       ` Linus Walleij
2014-12-17  5:10 ` [PATCH v2 RESEND 2/3] Documentation: gpio: Add APM X-Gene standby GPIO controller DTS binding Y Vo
2015-01-13  9:25   ` Linus Walleij
2015-01-13  9:41     ` Y Vo
2015-01-15 16:16       ` Linus Walleij
     [not found] ` <1418793050-26927-1-git-send-email-yvo-qTEPVZfXA3Y@public.gmane.org>
2014-12-17  5:10   ` [PATCH v2 RESEND 3/3] arm64:dts: Add APM X-Gene standby GPIO controller DTS entries Y Vo

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=CAL4ahLfGNc1sL-hr7bZi_pcxjz7CNHjPRSPnJf_TUCGsbweaDA@mail.gmail.com \
    --to=yvo@apm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=patches@apm.com \
    --cc=pvo@apm.com \
    --cc=toanle@apm.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).