From: Linus Walleij <linus.walleij@linaro.org> To: Michal Simek <michal.simek@xilinx.com> Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Michal Simek <monstr@monstr.eu>, Steffen Trumtrar <s.trumtrar@pengutronix.de>, Peter Crosthwaite <peter.crosthwaite@xilinx.com>, "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>, Rob Herring <robherring2@gmail.com>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID Date: Wed, 23 May 2018 11:42:14 +0200 [thread overview] Message-ID: <CACRpkdbCsUBMcHg+xGOQCBmhoJsqh9VjK+4pjhG5Hf6Fjzwjww@mail.gmail.com> (raw) In-Reply-To: <57e4bbdd-1e30-0352-f758-998b64a6b77f@xilinx.com> On Wed, May 2, 2018 at 4:19 PM, Michal Simek <michal.simek@xilinx.com> wrote: > On 2.5.2018 15:56, Linus Walleij wrote: >> Would it be possible that I apply the patch, and somehow also >> establish some understanding with all users of the Xilinx >> platform that whatever legacy applications are out there >> must start to migrate towards using the character device so >> this reliance on the numberspace doesn't stick around forever? > > When someone contacts me for asking guidance for gpio I am telling them > not to use legacy sysfs interface and use libgpiod. Awesome, thanks for your support :) > Last one was a week > ago in connection to Ultra96 and libmraa. > > But even chardev is not supported there now. > https://github.com/intel-iot-devkit/mraa/issues/713 Hm I hope this happens soon. Manavanninan is doing a great job in switching this over, I just have to accept that the pace isn't always what it should be in all upstream projects, and deal with an imperfect world. > If you take a look at > arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts > 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!) > 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 :/ Let's go for this patch and try to improve the situation gradually moving forward. Yours, Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] gpio: zynq: Setup chip->base based on alias ID Date: Wed, 23 May 2018 11:42:14 +0200 [thread overview] Message-ID: <CACRpkdbCsUBMcHg+xGOQCBmhoJsqh9VjK+4pjhG5Hf6Fjzwjww@mail.gmail.com> (raw) In-Reply-To: <57e4bbdd-1e30-0352-f758-998b64a6b77f@xilinx.com> On Wed, May 2, 2018 at 4:19 PM, Michal Simek <michal.simek@xilinx.com> wrote: > On 2.5.2018 15:56, Linus Walleij wrote: >> Would it be possible that I apply the patch, and somehow also >> establish some understanding with all users of the Xilinx >> platform that whatever legacy applications are out there >> must start to migrate towards using the character device so >> this reliance on the numberspace doesn't stick around forever? > > When someone contacts me for asking guidance for gpio I am telling them > not to use legacy sysfs interface and use libgpiod. Awesome, thanks for your support :) > Last one was a week > ago in connection to Ultra96 and libmraa. > > But even chardev is not supported there now. > https://github.com/intel-iot-devkit/mraa/issues/713 Hm I hope this happens soon. Manavanninan is doing a great job in switching this over, I just have to accept that the pace isn't always what it should be in all upstream projects, and deal with an imperfect world. > If you take a look at > arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts > 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!) > 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 :/ Let's go for this patch and try to improve the situation gradually moving forward. Yours, Linus Walleij
next prev parent reply other threads:[~2018-05-23 9:42 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-11 13:55 [PATCH] gpio: zynq: Setup chip->base based on alias ID Michal Simek 2018-04-11 13:55 ` Michal Simek 2018-04-26 13:08 ` Linus Walleij 2018-04-26 13:08 ` Linus Walleij 2018-04-26 13:35 ` Michal Simek 2018-04-26 13:35 ` Michal Simek 2018-05-02 10:10 ` Linus Walleij 2018-05-02 10:10 ` Linus Walleij 2018-05-02 10:15 ` Michal Simek 2018-05-02 10:15 ` Michal Simek 2018-05-02 13:01 ` Linus Walleij 2018-05-02 13:01 ` Linus Walleij 2018-05-02 13:41 ` Michal Simek 2018-05-02 13:41 ` Michal Simek 2018-05-02 13:56 ` Linus Walleij 2018-05-02 13:56 ` Linus Walleij 2018-05-02 14:19 ` Michal Simek 2018-05-02 14:19 ` Michal Simek 2018-05-15 13:26 ` Michal Simek 2018-05-15 13:26 ` Michal Simek 2018-05-23 9:44 ` Linus Walleij 2018-05-23 9:44 ` Linus Walleij 2018-05-23 10:26 ` Michal Simek 2018-05-23 10:26 ` Michal Simek 2018-05-23 9:42 ` Linus Walleij [this message] 2018-05-23 9:42 ` Linus Walleij 2018-05-23 10:17 ` Michal Simek 2018-05-23 10:17 ` Michal Simek
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=CACRpkdbCsUBMcHg+xGOQCBmhoJsqh9VjK+4pjhG5Hf6Fjzwjww@mail.gmail.com \ --to=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=michal.simek@xilinx.com \ --cc=monstr@monstr.eu \ --cc=peter.crosthwaite@xilinx.com \ --cc=robherring2@gmail.com \ --cc=s.trumtrar@pengutronix.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.