mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Dmitry Rokosov <ddrokosov@sberdevices.ru>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Alexey Romanov <avromanov@sberdevices.ru>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <neil.armstrong@linaro.org>,
	<khilman@baylibre.com>, <jbrunet@baylibre.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-amlogic@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <kernel@sberdevices.ru>
Subject: Re: [PATCH v1 1/2] arm64: dts: meson-a1: add gpio_intc node
Date: Mon, 6 Feb 2023 14:26:38 +0300	[thread overview]
Message-ID: <20230206112638.kbkcghcnbdszd4ru@CAB-WSD-L081021> (raw)
In-Reply-To: <CAFBinCC7=QR3Dd_N8VN-L7CpFWETTTehNo6j54f9Y53w8emwUQ@mail.gmail.com>

Hello Martin,

On Sun, Feb 05, 2023 at 12:05:46AM +0100, Martin Blumenstingl wrote:
> Hi Alexey,
> 
> On Thu, Feb 2, 2023 at 3:15 PM Alexey Romanov <avromanov@sberdevices.ru> wrote:
> >
> > Add gpio interrupt controller node.
> >
> > Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
> I have no way to verify the register offset or interrupt numbers.
> Overall it looks good though, so:
> Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

We've verified interrupt numbers and register offsets on the our device
board based on A1 (A113L) + A113L datasheet.

-- 
Thank you,
Dmitry

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2023-02-06 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 14:15 Alexey Romanov
2023-02-02 14:19 ` Alexey Romanov
2023-02-04 23:05 ` Martin Blumenstingl
2023-02-06 11:26   ` Dmitry Rokosov [this message]
2023-02-08 12:34 ` Neil Armstrong
2023-03-06 18:53   ` Alexey Romanov
2023-03-07  8:00 ` neil.armstrong
2023-03-07  9:30   ` Alexey Romanov

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=20230206112638.kbkcghcnbdszd4ru@CAB-WSD-L081021 \
    --to=ddrokosov@sberdevices.ru \
    --cc=avromanov@sberdevices.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@sberdevices.ru \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    /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

all inboxes | Powered by JetHome®