LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michal Simek <email@example.com>
To: Linus Walleij <firstname.lastname@example.org>,
Michal Simek <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Michal Simek <firstname.lastname@example.org>,
Steffen Trumtrar <email@example.com>,
Peter Crosthwaite <firstname.lastname@example.org>,
"open list:GPIO SUBSYSTEM" <email@example.com>,
Rob Herring <firstname.lastname@example.org>,
Linux ARM <email@example.com>
Subject: Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID
Date: Wed, 23 May 2018 12:17:09 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
>> If you take a look at
>> which is Ultra96 board gpio-line-names are filled there for the whole PS
>> part. Definitely take a look and let know if you find out any issue there.
> It looks good. I even managed to boot my Ultra96 board which
> was sent over as price in some competition (great hardware!)
Wonderful that you get hw available to be closer to issues.
Maybe it would be worth to give you some guidance what to do with PL and
how to add more stuff there especially in connection to GPIO.
We have pinctrl driver in vendor tree but my colleague needs to upstream
firmware interface first.
>> zynq/zynqmp gpio controller contains PS pins (hard part) and PL pins
>> coming to logic.
>> I can't describe PL gpio pins because it can be whatever even I have
>> done that for one fixed hw design.
>> Interesting part on that sha1 you shared is how "NC" pin is described.
>> gpio pin 35 I have on zcu100 as "" but it should be maybe TP_PAD which
>> is really just a pad on real board. And the rest of "" gpio names are
>> connected to PL.
> How to handle anything routed to/from programmable logic is
> in a bit of mess right now, I understand this work isn't the
> easiest :/
I am happy to discuss this to find out a way how this can be handled.
There are several things together.
On arm64 how to disable/enable access for NS software.
Maybe also separate pins PS pins from PL pins. Right now all are
together and not sure if this is ideal in sense of DT overal for
example. Separate nodes would enable better flexibility. Also if you
look at partial reconfiguration you can just route just part of pins
which suggest list of gpios used there.
prev parent reply other threads:[~2018-05-23 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 13:55 Michal Simek
2018-04-26 13:08 ` Linus Walleij
2018-04-26 13:35 ` Michal Simek
2018-05-02 10:10 ` Linus Walleij
2018-05-02 10:15 ` Michal Simek
2018-05-02 13:01 ` Linus Walleij
2018-05-02 13:41 ` Michal Simek
2018-05-02 13:56 ` Linus Walleij
2018-05-02 14:19 ` Michal Simek
2018-05-15 13:26 ` Michal Simek
2018-05-23 9:44 ` Linus Walleij
2018-05-23 10:26 ` Michal Simek
2018-05-23 9:42 ` Linus Walleij
2018-05-23 10:17 ` Michal Simek [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).