[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1337290826.7033.10.camel@trivette.site>
Date: Thu, 17 May 2012 17:40:26 -0400
From: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To: Grant Likely <grant.likely@...retlab.ca>
Cc: x86@...nel.org,
Jerome Oufella <jerome.oufella@...oirfairelinux.com>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
lm-sensors@...sensors.org,
Guenter Roeck <guenter.roeck@...csson.com>,
Jean Delvare <khali@...ux-fr.org>,
Linus Walleij <linus.walleij@...ricsson.com>
Subject: Re: [PATCH v6 3/3] gpio: TS-5500 GPIO support
On Thu, 2012-05-17 at 15:06 -0600, Grant Likely wrote:
> > arch/x86/include/asm/ts5500.h | 62 ++++++++
>
> Why the separate header file? What will use these defines? I
> normally expect driver-specific defines to be in the driver .c file
> directly; particularly for things like gpio drivers which should be a
> generic interface that doesn't need to export symbols.
Should an intermediate driver directly use values for GPIOs instead of
these symbols? For example, how should a temperature sensor plugged on
this platform refer to inputs and outputs?
Thanks,
Vivien
--
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