Messages in this thread | | | Date | Wed, 29 Feb 2012 10:57:48 +0900 | Subject | Re: [PULL-REQUEST] EXTCON Patches (Re: [PATCH v6 0/5] Introduce External Connector Class (extcon)) | From | MyungJoo Ham <> |
| |
On Wed, Feb 29, 2012 at 1:44 AM, Greg KH <gregkh@linuxfoundation.org> wrote: > On Tue, Feb 28, 2012 at 05:58:02PM +0900, MyungJoo Ham wrote: >> Hello Arnd, >> >> >> Presuming that the requests and comments upto v5 patchsets were >> addressed in the last patchset (v6), here goes a pull request of >> Extcon. > > Wait, please, before this code can be accepted, I would like to get > verification that you have also made the needed changes to the Android > userspace side of this interface, and that the code works there, and it > is on its way to be included in the main Android repo. > > Is this true? If not, what is the plans for this to happen? Without > that happening, I don't think this code can be accepted, do you? > > thanks, > > greg k-h
When an extcon device driver is not using the extended features (multistate & mutually-exclusiveness) and CONFIG_ANDROID is on, the userspace interface is same as the Android kernel's switch class (name and state ABI, which were read-only in Android kernel).
If an extcon device drivers uses the extended features (multistate & mutually-exclusiveness) by adding "cable names", the state ABI will provided information in different format. Besides, Android kernel's switch device driver cannot provide the extended feature anyway.
Thanks.
Cheers! MyungJoo. -- MyungJoo Ham, Ph.D. System S/W Lab, S/W Center, Samsung Electronics -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |