On Mon, Jun 17, 2013 at 11:53:53PM -0700, Prafulla Wadaskar wrote:
-----Original Message----- From: Simon Guinot [mailto:simon.guinot@sequanux.org] Sent: 18 June 2013 02:28 To: Prafulla Wadaskar Cc: Albert ARIBAUD; u-boot@lists.denx.de Subject: [PATCH 2/3] LaCie/common: add support for the GPIO extension bus
This patch adds support for the GPIO extension bus found on some LaCie boards (as the 2Big/5Big Network v2 and the 2Big NAS). This bus allows to configure the devices (mostly the LEDs) connected to a CPLD via two GPIO-based registers (address and data).
Hi Simon
Hi Prafulla,
Thanks for your quick answer.
The name given here for the patch as well as files "gpio-ext" is confusing for me.
As you stated here those are the IOs generated by CPLD on your board which can be programmed using bit-banging on two GPIOs.
Not really bit-banging. Here we have 3 GPIOs used as a kind of address register and 3 other GPIOs used as a kind of data register. An another GPIO is used to notify the CPLD than the registers have been updated. I will update the patch description to make clear that a register may include several GPIOs.
At LaCie, this kind of bus is called a "GPIO extension bus". It is like a cheap GPIO expander.
So to me it those are "cpld_ios".
I am not sure that behind this kind of bus we always have a CPLD. I will check this. If it is the case, what do you think about cpld-gpio-bus ?
Moreover as this "bus" is really a lacie specific stuff, should I prepend a "lacie-" prefix ?
Regards,
Simon
May you please rename these files accordingly and resend the patch series for better understanding?
To me "gpio-ext" is generic term application for "General purpose IOs"
Regards... Prafulla . . .