linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Cohen <david.a.cohen@linux.intel.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-gpio@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH RFC] gpio: Driver for SYSCON-based GPIOs
Date: Fri, 15 Nov 2013 09:57:12 -0800	[thread overview]
Message-ID: <52866078.2070703@linux.intel.com> (raw)
In-Reply-To: <1384497752-19032-1-git-send-email-shc_work@mail.ru>

Hi Alexander,

On 11/14/2013 10:42 PM, Alexander Shiyan wrote:
> SYSCON driver was designed for using memory areas (registers)
> that are used in several subsystems. There are systems (CPUs)
> which use bits in one register for various purposes and thus
> should be handled by various kernel subsystems. This driver
> allows you to use the individual SYSCON bits as GPIOs.
> This is RFC only yet, so I did not add DT bindings for this
> driver.
>
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> ---
>   drivers/gpio/Kconfig       |   6 ++
>   drivers/gpio/Makefile      |   1 +
>   drivers/gpio/gpio-syscon.c | 141 +++++++++++++++++++++++++++++++++++++++++++++
>   3 files changed, 148 insertions(+)
>   create mode 100644 drivers/gpio/gpio-syscon.c
>

[snip]

> +	if (of_property_read_u32(np, "gpio-syscon,offset", &priv->bit_offset))
> +		return -EINVAL;

Any reason for dropping the error code from of_property_read_u32() in
favor of fixed -EINVAL?

Br, David Cohen

  reply	other threads:[~2013-11-15 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15  6:42 [PATCH RFC] gpio: Driver for SYSCON-based GPIOs Alexander Shiyan
2013-11-15 17:57 ` David Cohen [this message]
2013-11-19  8:47 ` Linus Walleij
2013-11-19  9:17   ` Alexander Shiyan
2013-11-19  9:53     ` Linus Walleij

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=52866078.2070703@linux.intel.com \
    --to=david.a.cohen@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=shc_work@mail.ru \
    /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).