From: Pratyush Yadav <p.yadav@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/2] drivers: gpio: Add a managed API to get a GPIO from the device-tree
Date: Wed, 17 Jun 2020 13:29:31 +0530 [thread overview]
Message-ID: <20200617075931.hkgmavd2tzvqzkyo@ti.com> (raw)
In-Reply-To: <CAPnjgZ0btgoTJGrWDhdLgTddK08xjN7ogE5vSO0QB7rSsZvCLw@mail.gmail.com>
On 16/06/20 05:37PM, Simon Glass wrote:
> Hi Pratyush,
>
> On Fri, 29 May 2020 at 15:38, Pratyush Yadav <p.yadav@ti.com> wrote:
> >
> > From: Jean-Jacques Hiblot <jjhiblot@ti.com>
> >
> > Add managed functions to get a gpio from the devce-tree, based on a
> > property name (minus the '-gpios' suffix) and optionally an index.
> >
> > When the device is unbound, the GPIO is automatically released and the
> > data structure is freed.
> >
> > Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
> > ---
> > drivers/gpio/gpio-uclass.c | 70 ++++++++++++++++++++++++++++++++++++++
> > include/asm-generic/gpio.h | 47 +++++++++++++++++++++++++
> > 2 files changed, 117 insertions(+)
>
> Is there a change log for this one?
No changes to this patch from v1 other than adding a couple #include to
fix compilation errors.
--
Regards,
Pratyush Yadav
Texas Instruments India
next prev parent reply other threads:[~2020-06-17 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 21:38 [PATCH v2 0/2] gpio: Add a managed API Pratyush Yadav
2020-05-29 21:38 ` [PATCH v2 1/2] drivers: gpio: Add a managed API to get a GPIO from the device-tree Pratyush Yadav
2020-06-16 23:37 ` Simon Glass
2020-06-17 7:59 ` Pratyush Yadav [this message]
2020-06-26 1:12 ` Simon Glass
2020-05-29 21:38 ` [PATCH v2 2/2] test: gpio: Add tests for the managed API Pratyush Yadav
2020-06-17 3:11 ` Simon Glass
2020-05-31 14:08 ` [PATCH v2 0/2] gpio: Add a " Simon Glass
2020-06-01 11:22 ` Pratyush Yadav
2020-06-01 14:45 ` Simon Glass
2020-06-08 18:05 ` Pratyush Yadav
2020-06-17 3:11 ` Simon Glass
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=20200617075931.hkgmavd2tzvqzkyo@ti.com \
--to=p.yadav@ti.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 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.