lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 29 May 2015 09:26:13 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Gregory Fong <gregory.0xf0@...il.com>, linux-gpio@...r.kernel.org
CC:	Alexandre Courbot <gnurou@...il.com>,
	bcm-kernel-feedback-list@...adcom.com,
	Brian Norris <computersforpeace@...il.com>,
	devicetree@...r.kernel.org,
	Florian Fainelli <f.fainelli@...il.com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Mark Rutland <mark.rutland@....com>,
	Pawel Moll <pawel.moll@....com>,
	Rob Herring <robh+dt@...nel.org>,
	Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH v2 0/6] GPIO support for BRCMSTB

On 28/05/15 19:14, Gregory Fong wrote:
> This patchset adds support for the GPIO controller (UPG GIO) used on Broadcom's
> various BRCMSTB SoCs (BCM7XXX and others). It uses the "basic-mmio-gpio"
> interface to try to reduce duplication of the base logic.
> 
> For all existing hardware, this block hooked up to the BCM7120 L2 IRQ
> controller and so will require CONFIG_BCM7120_L2_IRQ=y.

Unless there are objections, I will take patches 5 and 6 and apply them
to soc/next.

Reviewed-by: Florian Fainelli <f.fainelli@...il.com>

Thanks!

> 
> New in v2:
> - fix license mismatch as pointed out by Paul Bolle
> - move select ARCH_WANT_OPTIONAL_GPIOLIB to separate patch
> - change to have 32 lines per bank per Linus Walleij's comments
> - allow this controller to be used as a wakeup source
> - add default GPIO number for BRCMSTB
> 
> The device tree bindings from v1 were merged to the GPIO tree, so this patchset
> only contains an addition to allow GPIOs to be used as a wakeup source
> (patch 3).  The initial bindings from v1 can be found at
> https://lkml.org/lkml/2015/5/6/200 .
> 
> Gregory Fong (6):
>   gpio: Add GPIO support for Broadcom STB SoCs
>   gpio: brcmstb: Add interrupt support
>   dt-bindings: brcmstb-gpio: document properties for wakeup
>   gpio: brcmstb: Allow GPIOs to be wakeup sources
>   ARM: brcmstb: Select ARCH_WANT_OPTIONAL_GPIOLIB
>   ARM: brcmstb: Add default gpio number
> 
>  .../devicetree/bindings/gpio/brcm,brcmstb-gpio.txt |  26 +-
>  MAINTAINERS                                        |   7 +
>  arch/arm/Kconfig                                   |   3 +-
>  arch/arm/mach-bcm/Kconfig                          |   1 +
>  drivers/gpio/Kconfig                               |   9 +
>  drivers/gpio/Makefile                              |   1 +
>  drivers/gpio/gpio-brcmstb.c                        | 581 +++++++++++++++++++++
>  7 files changed, 626 insertions(+), 2 deletions(-)
>  create mode 100644 drivers/gpio/gpio-brcmstb.c
> 


-- 
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ