From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 1/4] EXYNOS5: Add gpio pin numbering feature
Date: Tue, 15 Apr 2014 08:25:25 +0200 [thread overview]
Message-ID: <20140415082525.1cc20add@amdc2363> (raw)
In-Reply-To: <CAPnjgZ3Eum56=30PAhAQKi7A95OhNT5hpL_TRLzmzkq-=De78g@mail.gmail.com>
Hi Simon,
> Hi Lukasz,
>
> On 14 April 2014 01:17, Lukasz Majewski <l.majewski@samsung.com>
> wrote:
>
> [snip[
>
> I think your questions are mostly answered but I wanted to chime in
> on a few.
>
> What is wrong with specifying the bank field?
> > Why your gpio command cannot use the bank approach?
> >
>
> U-Boot has a generic GPIO API and we should try to use it where
> possible. This has been a long-standing TODO for exynos.
I'm also fully aware that Exynos suffers from inconsistent gpio API.
However, I'm very glad that with Akshay's and our effort this goal
will be accomplished :-)
>
>
> >
> > And one more question: Is this work compliant with new driver model,
> > which will be accepted at the merge window after the v2014.04
> > release?
> >
> > If not, then there is no point to review this code, since GPIO would
> > need to be adjusted to use this framework.
> >
>
> The driver model framework is already in mainline.
I was rather thinking about the "big switch" as we did with KBUILD
after the v2014.01. Anyway, I'm looking forward to see the wide
deployment of device model in u-boot.
> At present only
> sandbox uses it for GPIO. I started looking at exynos since I thought
> it might be quite easy to convert, but found that the generic GPIO
> stuff was still not merged.
>
> This series will make it much easier to convert exynos GPIO to driver
> model, since we can just change the driver.
Thanks for clarification.
>
> Regards,
> Simon
>
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2014-04-15 6:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 9:43 [U-Boot] [PATCH v6 0/4] Exynos5: Add GPIO numbering feature Akshay Saraswat
2014-04-12 9:43 ` [U-Boot] [PATCH v6 1/4] EXYNOS5: Add gpio pin " Akshay Saraswat
2014-04-12 20:30 ` Simon Glass
2014-04-14 7:17 ` Lukasz Majewski
2014-04-14 14:40 ` Simon Glass
2014-04-15 6:25 ` Lukasz Majewski [this message]
2014-04-17 4:21 ` Simon Glass
2014-04-14 15:15 ` Przemyslaw Marczak
2014-04-14 15:59 ` Simon Glass
2014-04-12 9:43 ` [U-Boot] [PATCH v6 2/4] S5P: Rename GPIO definitions Akshay Saraswat
2014-04-12 20:30 ` Simon Glass
2014-04-14 15:15 ` Przemyslaw Marczak
2014-04-12 9:43 ` [U-Boot] [PATCH v6 3/4] EXYNOS5: GPIO: Support GPIO Command for EXYNOS5 Akshay Saraswat
2014-04-12 20:32 ` Simon Glass
2014-04-14 15:19 ` Przemyslaw Marczak
2014-04-12 9:43 ` [U-Boot] [PATCH v6 4/4] Config: Exynos5: Enable Generic GPIO and CMD configs Akshay Saraswat
2014-04-12 20:33 ` Simon Glass
2014-04-12 20:39 ` Simon Glass
2014-04-14 9:31 ` [U-Boot] [PATCH v6 0/4] Exynos5: Add GPIO numbering feature Przemyslaw Marczak
-- strict thread matches above, loose matches on Subject: below --
2014-04-14 9:07 [U-Boot] [PATCH v6 1/4] EXYNOS5: Add gpio pin " Akshay Saraswat
2014-04-14 10:53 ` Lukasz Majewski
2014-04-14 12:42 ` Minkyu Kang
2014-04-14 14:55 Akshay Saraswat
2014-04-14 15:23 ` Przemyslaw Marczak
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=20140415082525.1cc20add@amdc2363 \
--to=l.majewski@samsung.com \
--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