linux-kernel - Re: [PATCH] extcon : callback function to read cable property

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Oct 2012 23:45:28 +0900
From:	anish kumar <anish198519851985@...il.com>
To:	Jenny TC <jenny.tc@...el.com>
Cc:	myungjoo.ham@...sung.com, cw00.choi@...sung.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] extcon : callback function to read cable property

On Wed, 2012-10-10 at 15:53 +0530, Jenny TC wrote:
> For some cables a boolean variable will not be enough to represent
> the state and properties of the cable. For example a charger cable can
> have states CONNECT,DISCOONECT,SUSPEND(Host suspend for SDP cable),
> RESUME(Host wakeup), and UPDATE (to increase the charge
> current after USB enumaeration).Also the properties of the cable may
> vary based on the state. FOr example in SUSPENDED state platforms can
> support 0/100/500/950(USB 3.0) mA based on the HW. To initiate charging
> the consumer should be able to get the charger properties dynamically.
> 
> Signed-off-by: Jenny TC <jenny.tc@...el.com>
> ---
>  include/linux/extcon.h |   14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/include/linux/extcon.h b/include/linux/extcon.h
> index 073fd49..2e61ee0 100644
> --- a/include/linux/extcon.h
> +++ b/include/linux/extcon.h
> @@ -122,6 +122,7 @@ struct extcon_dev {
>  	/* --- Optional callbacks to override class functions --- */
>  	ssize_t	(*print_name)(struct extcon_dev *edev, char *buf);
>  	ssize_t	(*print_state)(struct extcon_dev *edev, char *buf);
> +	int (*get_cable_properties)(const char *cable_name, void *cable_props);
>  
>  	/* --- Internal data. Please do not set. --- */
>  	struct device	*dev;
> @@ -177,6 +178,19 @@ struct extcon_specific_cable_nb {
>  	unsigned long previous_value;
>  };
>  
> +enum extcon_chrgr_cbl_stat {
> +	EXTCON_CHRGR_CABLE_CONNECTED,
> +	EXTCON_CHRGR_CABLE_DISCONNECTED,
> +	EXTCON_CHRGR_CABLE_SUSPENDED,
> +	EXTCON_CHRGR_CABLE_RESUMED,
> +	EXTCON_CHRGR_CABLE_UPDATED,
> +};
I think the reason why we have extcon is in first place
is to only notify the clients of cable connection and
disconnection and it is up to the client to decide what
else to do with the cable such as finding which state it
is in and other details.
So I feel this should not be handled in the extcon.

However it is up to the maintainer to decide.
> +
> +struct extcon_chrgr_cbl_props {
> +	enum extcon_chrgr_cbl_stat cable_stat;
> +	unsigned long mA;
> +};
> +
>  #if IS_ENABLED(CONFIG_EXTCON)
>  
>  /*


--
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/