linux-kernel - Re: [PATCH RESEND v9 1/2] gpio: Adjust of_xlate API to support multiple GPIO chips

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:	Thu, 17 May 2012 14:37:06 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Roland Stigge <stigge@...com.de>, glikely@...retlab.ca,
	arm@...nel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linus.walleij@...ricsson.com,
	kevin.wells@....com, srinivas.bakki@....com,
	devicetree-discuss@...ts.ozlabs.org, rob.herring@...xeda.com
Cc:	Roland Stigge <stigge@...com.de>
Subject: Re: [PATCH RESEND v9 1/2] gpio: Adjust of_xlate API to support multiple GPIO chips

On Wed, 16 May 2012 22:40:31 +0200, Roland Stigge <stigge@...com.de> wrote:
> This patch changes the of_xlate API to make it possible to manipulate the
> actual used gc. This way, multiple GPIO banks can be supported with the same DT
> registered GPIO controller.
> 
> The issue was discussed upon the integration of LPC32xx's DT support for its
> GPIO (see separate patch).
> 
> Signed-off-by: Roland Stigge <stigge@...com.de>

I still wasn't happy with this approach, so I bugged Arnd and we
discussed some options.  So, I think I've got a better solution that
doesn't change the signature of of_xlate.  Instead it allows of_xlate
to return an error code and still have multiple banks referring to the
same gpio_chip.

I've just posted the series.  Can you try it out and make sure it
works for you?

g.
--
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/