From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: JaeJoon Jung <rgbi3307@gmail.com>
Cc: Anup Patel <anup@brainfault.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH] RISC-V: Add and Update gpio-sifive.c for SiFive FU540 GPIO
Date: Tue, 28 Jan 2020 08:50:49 +0200 [thread overview]
Message-ID: <CAEn-LToqmqXJC0dMvu9qjSCBNRsSkYGrCFVbTojoOZDxTfwfSw@mail.gmail.com> (raw)
In-Reply-To: <CAHOvCC5h1cKJzYx4sm-U0HDY9LGkhqWYGh+VaaOaJidP=Jkerw@mail.gmail.com>
On Tue, Jan 28, 2020 at 8:42 AM JaeJoon Jung <rgbi3307@gmail.com> wrote:
>
> I added and updated gpio-sifive.c for SiFive FU540 GPIO.
> (References: SiFive FU540-C000 manual v1p0, Chapter 17 "GPIO")
> I attached drivers/gpio/gpio-sifive.c (new)
>
> RISCV-FU540:/root# uname -a
> Linux RISCV-FU540 5.5.0-dirty #6 SMP Tue Jan 28 14:38:11 KST 2020
> riscv64 GNU/Linux
>
> $ git diff v5.5 --compact-summary
> arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 13 ++++
> arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts | 36 +++++++++
> drivers/gpio/Kconfig | 8 ++
> drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-sifive.c (new) | 447
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 574 insertions(+)
>
> I used drivers/gpio/gpio-sifive.c in kernel v4.15(freedom-u-sdk)
> released by sifive.
Yash Shah (SiFive) is upstreaming a new GPIO driver.
You might want to look at:
[PATCH v4 0/6] GPIO & Hierarchy IRQ support for HiFive Unleashed
https://lists.infradead.org/pipermail/linux-riscv/2019-December/007883.html
david
prev parent reply other threads:[~2020-01-28 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 6:41 [PATCH] RISC-V: Add and Update gpio-sifive.c for SiFive FU540 GPIO JaeJoon Jung
2020-01-28 6:50 ` David Abdurachmanov [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=CAEn-LToqmqXJC0dMvu9qjSCBNRsSkYGrCFVbTojoOZDxTfwfSw@mail.gmail.com \
--to=david.abdurachmanov@gmail.com \
--cc=andrew@sifive.com \
--cc=anup@brainfault.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rgbi3307@gmail.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).