From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey Brodkin Date: Fri, 13 Oct 2017 13:55:28 +0000 Subject: [U-Boot] [PATCH] ARC: HSDK: introduce CREG GPIO driver In-Reply-To: <20171013134659.GH12015@bill-the-cat> References: <20171013132143.26340-1-Eugeniy.Paltsev@synopsys.com> <1507901601.3810.9.camel@synopsys.com> <20171013134659.GH12015@bill-the-cat> Message-ID: <1507902927.3810.12.camel@synopsys.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.denx.de 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 > > > --- > > >  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? -Alexey