| 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
| ||
|
Date: Wed, 4 May 2011 09:48:13 +0200 From: Philipp Zabel <philipp.zabel@...il.com> To: Paul Parsons <lost.distance@...oo.com> Cc: linux-kernel@...r.kernel.org, rpurdie@...ys.net Subject: Re: [PATCH 2/2] leds: Add ASIC3 LED support On Tue, May 3, 2011 at 10:25 PM, Paul Parsons <lost.distance@...oo.com> wrote: > Hi Philipp, > > --- On Tue, 3/5/11, Philipp Zabel <philipp.zabel@...il.com> wrote: > >> About this, see the other patch I sent. This should work >> with the GPIOs >> configured as outputs. > See my response on the other thread. Will do. >> Could be moved into struct resource definitions in >> asic3.c. >> Get to them with platform_get_resource() in >> asic3_led_probe(). >> After calculating the bus shift from the resource size, you >> have >> everything you need to get rid of the >> asic3_write_register() export. > I understand, but my feeling is that implementing a more generic mechanism will add complexity for little obvious gain. If the LED driver ever needs to be more generic then this can be revisited. Fair enough. Looks like your feeling is right - de-inlining and exporting asic3_read/write_register costs only ~300 bytes. iomem resources + ioremap + bus shift calculation in leds-asic3.o are probably bigger than that. regards Philipp -- 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