linux-kernel - Re: [PATCH] extcon : register for cable interest by cable name

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Oct 2012 06:52:24 +0000 (GMT)
From:	MyungJoo Ham <myungjoo.ham@...sung.com>
To:	Jenny TC <jenny.tc@...el.com>,
	최찬우 <cw00.choi@...sung.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:	myungjoo.ham@...il.com
Subject: Re: [PATCH] extcon : register for cable interest by cable name

> There are some scnearios where a driver/framework needs to register
> interest for a particular cable without specifying the extcon device
> name. One such scenario is charger notifications. The platform will
> have charger cabel which will be bound to any extcon device. It's
> not mandatory for the charger driver to know which extcon device
> it should use. This patch enables the support for registering
> interest for a cable just by cable name wihtout specifying the
> extcon device name
> 
> Signed-off-by: Jenny TC <jenny.tc@...el.com>
> ---
[]
> +extern struct extcon_dev *register_interest_cable_byname
> +		(struct extcon_specific_cable_nb *extcon_dev,
> +		const char *cable_name, struct notifier_block *nb);

What about allowing extcon_register_interest() to support the functionality?

I.e., allowing extcon_register_interest() to accept NULL extcon_name.


ps. anyway, usually, the "platforms" have the list of node paths, don't they?

Cheers!
MyungJoo