Re: [PATCH v6 1/5] Extcon (external connector): import Android'sswitch class and modify.
From: MyungJoo Ham
Date: Fri Mar 30 2012 - 04:56:26 EST
On Fri, Mar 30, 2012 at 7:27 AM, Erik Gilling <konkers@xxxxxxxxxx> wrote:
> On Fri, Mar 9, 2012 at 4:41 AM, Mark Brown
> <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>> On Mon, Feb 27, 2012 at 09:15:35PM +0900, MyungJoo Ham wrote:
>>> +#ifdef CONFIG_ANDROID
>>> + extcon_class = class_create(THIS_MODULE, "switch");
>>> +#else /* !CONFIG_ANDROID */
>>> + extcon_class = class_create(THIS_MODULE, "extcon");
>>> +#endif /* CONFIG_ANDROID */
>> This seems somewhat sad - if ANDROID is turned on the standard ABI
>> vanishes. It'd be much nicer to do this with a symlink (or with
>> symlinks within the android directory if the driver core doesn't support
>> that). That way userspace code can be written to the new ABI and will
>> work on Android systems without ifdefery.
> This won't work if userspace code is receiving uevents through netlink
> and comparing based on the device name which it does in android. Why
> change the name at all? Extcon is much more specific than "switch."
> A switch can can be used for more than just external connections such
> as availability of HMDI audio (which is only available once a HDMI
> mode is chosen and the interface is enabled.)
With class_compat as in patchset v7, (this thread is w/ v6) does the
issue (missing link from device name directory) still exist? (I don't
In the earlier iteration of dicussion, the name "switch" was dropped
as "switch" may mislead the concept.
For HDMI and HDMI-audio, although HDMI-audio is not physically
seperated from HDMI-cable and it is available after HDMI-cable is
"attached", HDMI-audio is still an external connection to the kernel
and its device drivers, isn' it?
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/