linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Simon Hatliff <hatliff@cadence.com>,
	Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH 1/2] gpio: Add a driver for Cadence GPIO controller
Date: Mon, 24 Apr 2017 15:00:10 +0200	[thread overview]
Message-ID: <CACRpkdZSyjZCe_02uoU0kFabaDR9DDpWhKowZ6rPO_v0N6WfOQ@mail.gmail.com> (raw)
In-Reply-To: <20170410152610.58bc589a@bbrezillon>

On Mon, Apr 10, 2017 at 3:26 PM, Boris Brezillon
<boris.brezillon@free-electrons.com> wrote:

> Linus, what should I do here? Drop support for edge interrupts?

Do whatever makes most sense for your usecases.
I certainly allow dirty hacks if it is to be able to use the hardware
at all.

Yours,
Linus Walleij

      reply	other threads:[~2017-04-24 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 16:04 [PATCH 1/2] gpio: Add a driver for Cadence GPIO controller Boris Brezillon
2017-03-29 16:04 ` [PATCH 2/2] dt-bindings: gpio: Document Cadence GPIO controller bindings Boris Brezillon
2017-03-30  8:37   ` Linus Walleij
2017-03-30  9:03 ` [PATCH 1/2] gpio: Add a driver for Cadence GPIO controller Linus Walleij
2017-03-30 11:29   ` Boris Brezillon
2017-03-30 11:51     ` Linus Walleij
2017-03-30 17:26     ` Simon Hatliff
2017-03-31 13:28       ` Boris Brezillon
2017-04-10 13:26       ` Boris Brezillon
2017-04-24 13:00         ` Linus Walleij [this message]

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=CACRpkdZSyjZCe_02uoU0kFabaDR9DDpWhKowZ6rPO_v0N6WfOQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=boris.brezillon@free-electrons.com \
    --cc=gnurou@gmail.com \
    --cc=hatliff@cadence.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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).