| 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: Thu, 27 Oct 2011 13:18:07 -0700 From: Stephen Warren <swarren@...dia.com> To: Peter De Schrijver <pdeschrijver@...dia.com>, Peter De Schrijver <pdeschrijver@...dia.com> CC: Russell King <linux@....linux.org.uk>, Colin Cross <ccross@...roid.com>, Olof Johansson <olof@...om.net>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org> Subject: RE: [PATCH 5/6] arm/tegra: pinmux tables and definitions for tegra30 Peter De Schrijver wrote at Tuesday, October 25, 2011 10:54 AM: > Define the pinmuxing and pindrive tables for tegra30. The pinmux table defines > the available functions for each pinmux group. The pindrive table defines the > default pullup or pulldowns for each group. This is almost fine. You added some new fields to struct tegra_pingroup_desc. This should be noted in the change description, pointing out that there are new HW features on Tegra30, but that the driver hasn't been updated to support them. You probably want to actually add those new fields in a separate patch before-hand, so you can modify pinmux-tegra20-tables.c to set all those reg fields to -1, so if/when the driver does support the fields, Tegra20 will indicate it doesn't support those parameters. -- nvpublic -- 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