linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: NeilBrown <neilb@suse.de>
Cc: NeilBrown <neil@brown.name>,
	linux-kernel@vger.kernel.org,
	GTA04 owners <gta04-owner@goldelico.com>,
	Tony Lindgren <tony@atomide.com>, Pavel Machek <pavel@ucw.cz>,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH 5/6] phy: twl4030-usb: add support for reading resistor on ID pin.
Date: Tue, 2 Jun 2015 19:19:53 +0530	[thread overview]
Message-ID: <556DB481.3080906@ti.com> (raw)
In-Reply-To: <20150602073731.26edbd3b@notabene.brown>

Hi,

On Tuesday 02 June 2015 03:07 AM, NeilBrown wrote:
> On Mon, 1 Jun 2015 19:06:52 +0530 Kishon Vijay Abraham I <kishon@ti.com>
> wrote:
>
>> Hi,
>>
>> On Thursday 16 April 2015 01:33 PM, NeilBrown wrote:
>>> From: NeilBrown <neilb@suse.de>
>>>
>>> The twl4030 phy can measure, with low precision, the
>>> resistance-to-ground of the ID pin.
>>>
>>> Add a function to read the value, and export the result
>>> via sysfs.
>>
>> Little sceptical about adding new sysfs entries. Do you have a good reason to
>> add this?
>
> The hardware can report the value, so why not present it to user-space?
>
> I originally used this with a udev rule which would configure the maximum
> current based on the resistance measure - to work with the particular charger
> hardware I have.
>
> More recent patches try to do all of the max-current configuration in the
> kernel, so I could live without exporting the value via sysfs if that is a
> show-stopper.
>
> I can't see where the scepticism comes from though.  It is a well defined
> and cleary documented feature of the hardware.  Why not expose it?

ABI can never be removed or modified later. So should be really careful before 
adding it.

Thanks
Kishon

>
> Thanks,
> NeilBrown
>
>
>>
>> Thanks
>> Kishon
>>>
>>> If the read fails, which it does sometimes, try again in 50msec.
>>>
>>> Acked-by: Pavel Machek <pavel@ucw.cz>
>>> Signed-off-by: NeilBrown <neilb@suse.de>
>>> ---
>>>    .../ABI/testing/sysfs-platform-twl4030-usb         |   22 +++++++
>>>    drivers/phy/phy-twl4030-usb.c                      |   63 ++++++++++++++++++++
>>>    2 files changed, 85 insertions(+)
>>>
>>> diff --git a/Documentation/ABI/testing/sysfs-platform-twl4030-usb b/Documentation/ABI/testing/sysfs-platform-twl4030-usb
>>> index 512c51be64ae..425d23676f8a 100644
>>> --- a/Documentation/ABI/testing/sysfs-platform-twl4030-usb
>>> +++ b/Documentation/ABI/testing/sysfs-platform-twl4030-usb
>>> @@ -6,3 +6,25 @@ Description:
>>>    	Possible values: "on", "off".
>>>
>>>    	Changes are notified via select/poll.
>>> +
>>> +What: /sys/bus/platform/devices/*twl4030-usb/id
>>> +Description:
>>> +	Read-only report on measurement of USB-OTG ID pin.
>>> +
>>> +	The ID pin may be floating, grounded, or pulled to
>>> +	ground by a resistor.
>>> +
>>> +	A very course grained reading of the resistance is
>>> +	available.  The numbers given in kilo-ohms are roughly
>>> +	the center-point of the detected range.
>>> +
>>> +	Possible values are:
>>> +		ground
>>> +		102k
>>> +		200k
>>> +		440k
>>> +		floating
>>> +		unknown
>>> +
>>> +	"unknown" indicates a problem with trying to detect
>>> +	the resistance.
>>> diff --git a/drivers/phy/phy-twl4030-usb.c b/drivers/phy/phy-twl4030-usb.c
>>> index 3a707dd14238..1d6f3e70193e 100644
>>> --- a/drivers/phy/phy-twl4030-usb.c
>>> +++ b/drivers/phy/phy-twl4030-usb.c
>>> @@ -379,6 +379,56 @@ static void twl4030_i2c_access(struct twl4030_usb *twl, int on)
>>>    	}
>>>    }
>>>
>>> +enum twl4030_id_status {
>>> +	TWL4030_GROUND,
>>> +	TWL4030_102K,
>>> +	TWL4030_200K,
>>> +	TWL4030_440K,
>>> +	TWL4030_FLOATING,
>>> +	TWL4030_ID_UNKNOWN,
>>> +};
>>> +static char *twl4030_id_names[] = {
>>> +	"ground",
>>> +	"102k",
>>> +	"200k",
>>> +	"440k",
>>> +	"floating",
>>> +	"unknown"
>>> +};
>>> +
>>> +enum twl4030_id_status twl4030_get_id(struct twl4030_usb *twl)
>>> +{
>>> +	int ret;
>>> +
>>> +	pm_runtime_get_sync(twl->dev);
>>> +	if (twl->usb_mode == T2_USB_MODE_ULPI)
>>> +		twl4030_i2c_access(twl, 1);
>>> +	ret = twl4030_usb_read(twl, ULPI_OTG_CTRL);
>>> +	if (ret < 0 || !(ret & ULPI_OTG_ID_PULLUP)) {
>>> +		/* Need pull-up to read ID */
>>> +		twl4030_usb_set_bits(twl, ULPI_OTG_CTRL,
>>> +				     ULPI_OTG_ID_PULLUP);
>>> +		mdelay(50);
>>> +	}
>>> +	ret = twl4030_usb_read(twl, ID_STATUS);
>>> +	if (ret < 0 || (ret & 0x1f) == 0) {
>>> +		mdelay(50);
>>> +		ret = twl4030_usb_read(twl, ID_STATUS);
>>> +	}
>>> +
>>> +	if (twl->usb_mode == T2_USB_MODE_ULPI)
>>> +		twl4030_i2c_access(twl, 0);
>>> +	pm_runtime_put_autosuspend(twl->dev);
>>> +
>>> +	if (ret < 0)
>>> +		return TWL4030_ID_UNKNOWN;
>>> +	ret = ffs(ret) - 1;
>>> +	if (ret < TWL4030_GROUND || ret > TWL4030_FLOATING)
>>> +		return TWL4030_ID_UNKNOWN;
>>> +
>>> +	return ret;
>>> +}
>>> +
>>>    static void __twl4030_phy_power(struct twl4030_usb *twl, int on)
>>>    {
>>>    	u8 pwr = twl4030_usb_read(twl, PHY_PWR_CTRL);
>>> @@ -532,6 +582,16 @@ static ssize_t twl4030_usb_vbus_show(struct device *dev,
>>>    }
>>>    static DEVICE_ATTR(vbus, 0444, twl4030_usb_vbus_show, NULL);
>>>
>>> +static ssize_t twl4030_usb_id_show(struct device *dev,
>>> +				   struct device_attribute *attr,
>>> +				   char *buf)
>>> +{
>>> +	struct twl4030_usb *twl = dev_get_drvdata(dev);
>>> +	return scnprintf(buf, PAGE_SIZE, "%s\n",
>>> +			 twl4030_id_names[twl4030_get_id(twl)]);
>>> +}
>>> +static DEVICE_ATTR(id, 0444, twl4030_usb_id_show, NULL);
>>> +
>>>    static irqreturn_t twl4030_usb_irq(int irq, void *_twl)
>>>    {
>>>    	struct twl4030_usb *twl = _twl;
>>> @@ -709,6 +769,8 @@ static int twl4030_usb_probe(struct platform_device *pdev)
>>>    	platform_set_drvdata(pdev, twl);
>>>    	if (device_create_file(&pdev->dev, &dev_attr_vbus))
>>>    		dev_warn(&pdev->dev, "could not create sysfs file\n");
>>> +	if (device_create_file(&pdev->dev, &dev_attr_id))
>>> +		dev_warn(&pdev->dev, "could not create sysfs file\n");
>>>
>>>    	ATOMIC_INIT_NOTIFIER_HEAD(&twl->phy.notifier);
>>>
>>> @@ -753,6 +815,7 @@ static int twl4030_usb_remove(struct platform_device *pdev)
>>>    	pm_runtime_get_sync(twl->dev);
>>>    	cancel_delayed_work(&twl->id_workaround_work);
>>>    	device_remove_file(twl->dev, &dev_attr_vbus);
>>> +	device_remove_file(twl->dev, &dev_attr_id);
>>>
>>>    	/* set transceiver mode to power on defaults */
>>>    	twl4030_usb_set_mode(twl, -1);
>>>
>>>
>

  reply	other threads:[~2015-06-02 13:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16  8:03 [PATCH 0/6] Enhancements to twl4030 phy to support better charging NeilBrown
2015-04-16  8:03 ` [PATCH 4/6] phy: twl4030-usb: add ABI documentation NeilBrown
2015-04-17 22:14   ` Pavel Machek
2015-04-17 22:34     ` NeilBrown
2015-04-16  8:03 ` [PATCH 2/6] phy: twl4030-usb: remove pointless 'suspended' test in 'suspend' callback NeilBrown
2015-04-16  8:03 ` [PATCH 1/6] phy: twl4030-usb: make runtime pm more reliable NeilBrown
2015-04-16  8:03 ` [PATCH 3/6] phy: twl4030-usb: remove incorrect pm_runtime_get_sync() in probe function NeilBrown
2015-04-16  8:03 ` [PATCH 5/6] phy: twl4030-usb: add support for reading resistor on ID pin NeilBrown
2015-06-01 13:36   ` Kishon Vijay Abraham I
2015-06-01 21:37     ` NeilBrown
2015-06-02 13:49       ` Kishon Vijay Abraham I [this message]
2015-06-02 14:06         ` [Gta04-owner] " Dr. H. Nikolaus Schaller
2015-06-02 20:11           ` Pavel Machek
2015-06-02 20:47             ` Dr. H. Nikolaus Schaller
2015-06-06 13:10       ` Pavel Machek
2015-06-08  3:45         ` Felipe Balbi
2015-06-23  9:09       ` [Gta04-owner] " Dr. H. Nikolaus Schaller
2015-04-16  8:03 ` [PATCH 6/6] phy: twl4030-usb: add extcon to report cable connections NeilBrown
2015-05-11 13:38   ` Kishon Vijay Abraham I
2015-05-11 15:58     ` Chanwoo Choi

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=556DB481.3080906@ti.com \
    --to=kishon@ti.com \
    --cc=gta04-owner@goldelico.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=neilb@suse.de \
    --cc=pavel@ucw.cz \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).