| 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
| ||
|
Message-ID: <AANLkTiknYmWOmiFXGp6h2dT==aMuGs3BtXi82b6Vdq5i@mail.gmail.com> Date: Thu, 18 Nov 2010 14:02:09 -0800 From: Janakiram Sistla <janakiram.sistla@...il.com> To: Gregory Bean <gbean@...eaurora.org> Cc: dwalker@...eaurora.org, linux-arm-msm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v4 2/2] msm: gpio: Add irq support to v2 gpiolib. On Thu, Nov 18, 2010 at 12:59 PM, Gregory Bean <gbean@...eaurora.org> wrote: >>>> Do you mean to MSM have v1 and v2 gpio hardware ??? can not we >>>> have one file under mach-msm as gpio.c?? >>> >>> The MSM8x60 is the first MSM chip to carry the second-generation, or v2, >>> GPIO hardware block. This block is not backward compatible with the >>> v1 block found on older MSMs, so the two drivers cannot be elegantly >>> merged. >> >> so this is applicable to 8x60 and coming chip sets.I basically have a >> question,How come a a new person under stand the chipset uses gpio-v1 >> or gpiov2?? > > Targets with the v2 block define CONFIG_MSM_V2_TLMM. So in that case we can name it as gpio-tlmm.c ?? > -- > Employee of Qualcomm Innovation Center, Inc. > Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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