From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: "Jenny TC" <jenny.tc@intel.com>, 최찬우 <cw00.choi@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: myungjoo.ham@gmail.com
Subject: Re: [PATCH] extcon : register for cable interest by cable name
Date: Wed, 10 Oct 2012 06:52:24 +0000 (GMT) [thread overview]
Message-ID: <7103095.833841349851943826.JavaMail.weblogic@epml02> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1130 bytes --]
> 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@intel.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
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2012-10-10 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 6:52 MyungJoo Ham [this message]
2012-10-11 10:37 ` [PATCH] extcon : register for cable interest by cable name Tc, Jenny
2012-10-15 14:53 ` MyungJoo Ham
-- strict thread matches above, loose matches on Subject: below --
2012-10-10 10:20 Jenny TC
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7103095.833841349851943826.JavaMail.weblogic@epml02 \
--to=myungjoo.ham@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=jenny.tc@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox