From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] gpio: Add DW APB GPIO driver
Date: Mon, 3 Aug 2015 02:16:24 +0200 [thread overview]
Message-ID: <201508030216.24431.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ03Sc_WZH-Se879h3-MaE5B_5HPh9ve6_G=xz=JXGV+7Q@mail.gmail.com>
On Monday, August 03, 2015 at 01:38:28 AM, Simon Glass wrote:
> Hi Marek,
Hi Simon,
[...]
> >> > + if (!fdtdec_get_bool(blob, node, "gpio-controller"))
> >> > + continue;
> >> > +
> >> > + plat = NULL;
> >> > + plat = calloc(1, sizeof(*plat));
> >>
> >> I suppose this should use devm_alloc() now.
> >
> > Is that even in u-boot/master ? Also, I'm not sure it's a good idea to
> > put this in if I use this driver in SPL.
>
> Yes it's very new. Only in dm/master.
>
> It's only compiled in when enabled, so you can still use it in SPL.
>
> Up to you. At some point I think we should convert all driver allocs
> to use devm so that we know what allocation is going on.
When is this landing in master ? I don't mind either way, but I can do
a linting pass on the socfpga when things settle down too.
> >> > + if (!plat)
> >> > + return -ENOMEM;
> >> > +
> >> > + plat->base = base;
> >> > + plat->bank = bank;
> >> > + plat->pins = fdtdec_get_int(blob, node,
> >> > "snps,nr-gpios", 0); + snprintf(plat->name,
> >> > sizeof(plat->name) - 1, "%s-bank%i-", + name,
> >> > bank);
> >>
> >> Why such a long name? That's going to be a pain to type in the 'gpio'
> >> command.
> >
> > Do you have a suggestion please ?
>
> A, B, C is good if you have <=26 banks. Tegra does that.
>
> Exynos does PA0, PA1, PB0, PC0, PC1, etc.
How do I identify which one is PA0/PA1/PA2 , shall I perform some transformation
on the register address of the GPIO block or example ? But how can I assure that
if the next SoCFPGA has these addresses completely different, these GPIO numbers
will be stable ? Isn't it better to be explicit about the GPIO block ID then ?
Also, remember that I have an FPGA in the same package, which has a lot of I/O.
> > Also, I can as well use "gpio <operation> N" , where N is a number.
What about this ? How does indexing the GPIOs with plain number fit into the
picture please ?
[...]
next prev parent reply other threads:[~2015-08-03 0:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 20:44 [U-Boot] [PATCH 1/2] gpio: Add DW APB GPIO driver Marek Vasut
2015-07-27 20:44 ` [U-Boot] [PATCH 2/2] arm: socfpga: Enable DWAPB " Marek Vasut
2015-08-02 21:28 ` Simon Glass
2015-08-02 21:28 ` [U-Boot] [PATCH 1/2] gpio: Add DW APB " Simon Glass
2015-08-02 22:19 ` Marek Vasut
2015-08-02 23:38 ` Simon Glass
2015-08-03 0:16 ` Marek Vasut [this message]
2015-08-05 14:39 ` Simon Glass
2015-08-06 1:49 ` Marek Vasut
2015-08-07 19:13 ` Simon Glass
2015-08-07 20:35 ` Marek Vasut
2015-08-07 20:37 ` Simon Glass
2015-08-10 15:01 ` Marek Vasut
2015-08-10 15:35 ` Simon Glass
2015-08-10 16:28 ` Marek Vasut
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=201508030216.24431.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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: 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