From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARC: HSDK: introduce CREG GPIO driver
Date: Fri, 13 Oct 2017 09:55:58 -0400 [thread overview]
Message-ID: <20171013135558.GJ12015@bill-the-cat> (raw)
In-Reply-To: <1507902927.3810.12.camel@synopsys.com>
On Fri, Oct 13, 2017 at 01:55:28PM +0000, Alexey Brodkin wrote:
> Hi Tom,
>
> On Fri, 2017-10-13 at 09:46 -0400, Tom Rini wrote:
> > On Fri, Oct 13, 2017 at 01:33:22PM +0000, Alexey Brodkin wrote:
> > >
> > > Hi Tom,
> > >
> > > On Fri, 2017-10-13 at 16:21 +0300, Eugeniy Paltsev wrote:
> > > >
> > > > The HSDK can manage some pins via CREG registers block.
> > > >
> > > > Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
> > > > ---
> > > > MAINTAINERS | 6 +++
> > > > drivers/gpio/Kconfig | 7 +++
> > > > drivers/gpio/Makefile | 1 +
> > > > drivers/gpio/hsdk-creg-gpio.c | 109 ++++++++++++++++++++++++++++++++++++++++++
> > > > 4 files changed, 123 insertions(+)
> > > > create mode 100644 drivers/gpio/hsdk-creg-gpio.c
> > >
> > > I'm wondering if this one should go through my tree as this
> > > is for one of our Synopsys ARC devboards or GPIO stuff usually
> > > goes through some other tree?
> >
> > The ARC tree is fine, but it's a bit late posting for this release.
>
> So should I keep this one in "next" branch of my tree before v2017.11
> gets cut?
Yes, thanks.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171013/5cc2ff52/attachment.sig>
next prev parent reply other threads:[~2017-10-13 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 13:21 [U-Boot] [PATCH] ARC: HSDK: introduce CREG GPIO driver Eugeniy Paltsev
2017-10-13 13:33 ` Alexey Brodkin
2017-10-13 13:46 ` Tom Rini
2017-10-13 13:55 ` Alexey Brodkin
2017-10-13 13:55 ` Tom Rini [this message]
2017-10-16 12:30 ` Alexey Brodkin
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=20171013135558.GJ12015@bill-the-cat \
--to=trini@konsulko.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