[{"id":1772219,"web_url":"http://patchwork.ozlabs.org/comment/1772219/","msgid":"<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>","list_archive_url":null,"date":"2017-09-20T20:52:55","subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","submitter":{"id":62529,"url":"http://patchwork.ozlabs.org/api/people/62529/","name":"Rob Herring (Arm)","email":"robh@kernel.org"},"content":"On Sat, Sep 16, 2017 at 01:42:19PM +0300, Serge Semin wrote:\n> This parameters may be varied in accordance with hardware specifics.\n> So lets add the corresponding settings to the usb251x driver dts\n> specification.\n> \n> Signed-off-by: Serge Semin <fancer.lancer@gmail.com>\n> ---\n>  Documentation/devicetree/bindings/usb/usb251xb.txt   |  6 ++++++\n>  drivers/usb/misc/usb251xb.c                          | 20 ++++++++++++++++----\n>  2 files changed, 22 insertions(+), 4 deletions(-)\n> \n> diff --git a/Documentation/devicetree/bindings/usb/usb251xb.txt b/Documentation/devicetree/bindings/usb/usb251xb.txt\n> index 3d84626d3..dd59a32e7 100644\n> --- a/Documentation/devicetree/bindings/usb/usb251xb.txt\n> +++ b/Documentation/devicetree/bindings/usb/usb251xb.txt\n> @@ -44,6 +44,12 @@ Optional properties :\n>  \tdevice connected.\n>   - sp-disabled-ports : Specifies the ports which will be self-power disabled\n>   - bp-disabled-ports : Specifies the ports which will be bus-power disabled\n> + - sp-max-{power,current} : Indicates the power/current consumed by hub from\n> +\tan upstream port (VBUS) when operation as a self-powered hub. The value\n> +\tis given in mA in a 0 - 100 range (default is 1mA).\n> + - bp-max-{power,current} : Indicates the power/current consumed by hub from\n> +\tan upstream port (VBUS) when operation as a bus-powered hub. The value\n> +\tis given in mA in a 0 - 510 range (default is 100mA).\n\nThese need units as defined in property-units.txt.\n\nWhy do you need power and current? Can't you calculate power?\n\n>   - power-on-time-ms : Specifies the time it takes from the time the host\n>  \tinitiates the power-on sequence to a port until the port has adequate\n>  \tpower. The value is given in ms in a 0 - 510 range (default is 100ms).\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at  http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"<devicetree-owner@vger.kernel.org>","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=<UNKNOWN>)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xyBsG1bxvz9s8J\n\tfor <incoming-dt@patchwork.ozlabs.org>;\n\tThu, 21 Sep 2017 06:57:54 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751854AbdITU5P (ORCPT\n\t<rfc822;incoming-dt@patchwork.ozlabs.org>);\n\tWed, 20 Sep 2017 16:57:15 -0400","from mail-pg0-f67.google.com ([74.125.83.67]:36049 \"EHLO\n\tmail-pg0-f67.google.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1751837AbdITUw5 (ORCPT\n\t<rfc822; devicetree@vger.kernel.org>); Wed, 20 Sep 2017 16:52:57 -0400","by mail-pg0-f67.google.com with SMTP id d8so2245465pgt.3;\n\tWed, 20 Sep 2017 13:52:56 -0700 (PDT)","from localhost ([2620:0:1000:fd28:e83d:5428:912b:b325])\n\tby smtp.gmail.com with ESMTPSA id\n\ty83sm10136650pff.167.2017.09.20.13.52.55\n\t(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);\n\tWed, 20 Sep 2017 13:52:55 -0700 (PDT)"],"X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:in-reply-to:user-agent;\n\tbh=HMVOx+TtkQGIje6KReXnLSe9BBLtdxRBxS1bNvVmvMg=;\n\tb=Drtj3GeWESVd8MJAEQi8LcGo5Pgl5EBm2LWNeZB7IRu+0Hpdwik9H1YCbzg4/dYmZv\n\tRKHJBqE353roOP2nH66Fv7RAl7VkvVD+SSikD5zZzjG3jHQkPyLpYUmeTYSZDcSwFVzI\n\ti64sYx4KM/8CQHXdvM3bqel4Ni0cpNavOUVWDeKWB7m5clIWJN/c3o/jwZTpe4qnTjxt\n\t3uV2yyb2BqZBK58A21Xt8EVNL4ppEkCJ6EkaYirPH8rM9W+l9DLOY/k77eKFBhCiN5Gm\n\tgBFcr1S9k6aQ23gBB/RO1dcL4Ep7bxQSeS/s+U0UKSNvgLQn2TvXHWA8JbSPnxawVk6i\n\tDu+A==","X-Gm-Message-State":"AHPjjUhhX1sc57Wit2QwObeQp14EPB1cSiqGdXe9Fl3jnu2rD2Xfz9Vg\n\tq7hFB6cwCoHca2IsQm7Chw==","X-Google-Smtp-Source":"AOwi7QDZMjzhBRN7OzUbg9P9Inbkn+ywXP3zt8nKgNEBCLkLojzY11V3hB8x8R4R51C+r7QJWK7u9w==","X-Received":"by 10.84.235.200 with SMTP id m8mr3370907plt.310.1505940776542; \n\tWed, 20 Sep 2017 13:52:56 -0700 (PDT)","Date":"Wed, 20 Sep 2017 15:52:55 -0500","From":"Rob Herring <robh@kernel.org>","To":"Serge Semin <fancer.lancer@gmail.com>","Cc":"richard.leitner@skidata.com, gregkh@linuxfoundation.org,\n\tmark.rutland@arm.com, Sergey.Semin@t-platforms.ru,\n\tlinux-usb@vger.kernel.org, devicetree@vger.kernel.org,\n\tlinux-kernel@vger.kernel.org","Subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","Message-ID":"<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>","References":"<20170915233113.17855-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-9-fancer.lancer@gmail.com>","MIME-Version":"1.0","Content-Type":"text/plain; charset=us-ascii","Content-Disposition":"inline","In-Reply-To":"<20170916104220.3742-9-fancer.lancer@gmail.com>","User-Agent":"NeoMutt/20170113 (1.7.2)","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"<devicetree.vger.kernel.org>","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1772259,"web_url":"http://patchwork.ozlabs.org/comment/1772259/","msgid":"<20170920212739.GB3547@mobilestation>","list_archive_url":null,"date":"2017-09-20T21:27:39","subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","submitter":{"id":70038,"url":"http://patchwork.ozlabs.org/api/people/70038/","name":"Serge Semin","email":"fancer.lancer@gmail.com"},"content":"On Wed, Sep 20, 2017 at 03:52:55PM -0500, Rob Herring <robh@kernel.org> wrote:\n> On Sat, Sep 16, 2017 at 01:42:19PM +0300, Serge Semin wrote:\n> > This parameters may be varied in accordance with hardware specifics.\n> > So lets add the corresponding settings to the usb251x driver dts\n> > specification.\n> > \n> > Signed-off-by: Serge Semin <fancer.lancer@gmail.com>\n> > ---\n> >  Documentation/devicetree/bindings/usb/usb251xb.txt   |  6 ++++++\n> >  drivers/usb/misc/usb251xb.c                          | 20 ++++++++++++++++----\n> >  2 files changed, 22 insertions(+), 4 deletions(-)\n> > \n> > diff --git a/Documentation/devicetree/bindings/usb/usb251xb.txt b/Documentation/devicetree/bindings/usb/usb251xb.txt\n> > index 3d84626d3..dd59a32e7 100644\n> > --- a/Documentation/devicetree/bindings/usb/usb251xb.txt\n> > +++ b/Documentation/devicetree/bindings/usb/usb251xb.txt\n> > @@ -44,6 +44,12 @@ Optional properties :\n> >  \tdevice connected.\n> >   - sp-disabled-ports : Specifies the ports which will be self-power disabled\n> >   - bp-disabled-ports : Specifies the ports which will be bus-power disabled\n> > + - sp-max-{power,current} : Indicates the power/current consumed by hub from\n> > +\tan upstream port (VBUS) when operation as a self-powered hub. The value\n> > +\tis given in mA in a 0 - 100 range (default is 1mA).\n> > + - bp-max-{power,current} : Indicates the power/current consumed by hub from\n> > +\tan upstream port (VBUS) when operation as a bus-powered hub. The value\n> > +\tis given in mA in a 0 - 510 range (default is 100mA).\n> \n> These need units as defined in property-units.txt.\n> \n\nOk.\n\n> Why do you need power and current? Can't you calculate power?\n> \n\nThese are different parameters of the device. They got different configuration\nregisters and descriptions:\nmax_power* - ... This value also includes the power consumption of a\npermanently attached peripheral if the hub is configured as a compound\ndevice, and the embedded peripheral reports 0mA in its descriptors.\nmax_current* - ... This value does NOT include the power consumption of a\npermanently attached peripheral if the hub is configured as a compound\ndevice.\n\nAdditionally as you can see, they both are measured in \"mA\", so it isn't\na real physical power.\n\n> >   - power-on-time-ms : Specifies the time it takes from the time the host\n> >  \tinitiates the power-on sequence to a port until the port has adequate\n> >  \tpower. The value is given in ms in a 0 - 510 range (default is 100ms).\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at  http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"<devicetree-owner@vger.kernel.org>","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=<UNKNOWN>)","ozlabs.org;\n\tdkim=fail reason=\"signature verification failed\" (2048-bit key;\n\tunprotected) header.d=gmail.com header.i=@gmail.com\n\theader.b=\"CsFKRSCd\"; dkim-atps=neutral"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xyCX56FMZz9sNr\n\tfor <incoming-dt@patchwork.ozlabs.org>;\n\tThu, 21 Sep 2017 07:28:05 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751801AbdITV1k (ORCPT\n\t<rfc822;incoming-dt@patchwork.ozlabs.org>);\n\tWed, 20 Sep 2017 17:27:40 -0400","from mail-lf0-f67.google.com ([209.85.215.67]:32983 \"EHLO\n\tmail-lf0-f67.google.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1751641AbdITV1i (ORCPT\n\t<rfc822; devicetree@vger.kernel.org>); Wed, 20 Sep 2017 17:27:38 -0400","by mail-lf0-f67.google.com with SMTP id y15so2022151lfd.0;\n\tWed, 20 Sep 2017 14:27:37 -0700 (PDT)","from mobilestation ([95.79.181.62])\n\tby smtp.gmail.com with ESMTPSA id\n\tx28sm466074lfb.87.2017.09.20.14.27.35\n\t(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\n\tWed, 20 Sep 2017 14:27:35 -0700 (PDT)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;\n\th=date:from:to:cc:subject:message-id:references:mime-version\n\t:content-disposition:in-reply-to:user-agent;\n\tbh=fZocCDQG8ZfCRyBSg/pijBYUgaqLtDZ9EsaLUqxiAYM=;\n\tb=CsFKRSCduLBXiUcevlIeerOq9twvFsFp29i9D0QkBUPOIcPah/cUaHHR7ymGci+yXb\n\tN5tv9JkWsYFUXiThBrRSRe+TD3NJoTtCBHPTPsuCb1t+1U5RE9xMuAc2XoD08rwbWN3B\n\ty24NwfIpP//+U3H1aWzqYgQTndrzmVS02t9Msx2eJYdVrJGhFvhgeVZpR5o+OAaA030B\n\tpTJbptCofi9QK45GdwbPolrMOENwoInVKeE6m3oP4kvR5E9XlgoLwbfcZMOFZDxQZNtz\n\tdgklu5dIb5HsqGmc+RoVl0pWlRBPkXD3al1h9e8UqpnZaJFZkY/jF5g2TruFDIst7FLQ\n\tSlZw==","X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:in-reply-to:user-agent;\n\tbh=fZocCDQG8ZfCRyBSg/pijBYUgaqLtDZ9EsaLUqxiAYM=;\n\tb=a536x3yv+zmxbswPSej2oK0QQ4OcSs01SDaqpY0IflzCk2sP85DQ3z8W874RL4J39H\n\tTMUFHVAPoRI7MpbbWEXtQvBclDBGR5iLUJq7hLrtGmKzRfFjVT39m6XmU+QkVR4lOGW+\n\tZqx09dM0Y2Ew+f2WCeDrqv73gS+LNKid1R5xiNMN52vKgCxgyujmAamQyIPGi15mfU1g\n\t3rhoE9zxmAFXiUxsYhR+a82Il+zo2ttouYltEuCtFbzbFv4ZFYwcGPmQ9Z8641Z1SGYs\n\tCsajn1/d1GDoyJuKnuJjnx7WBxsfZqKgGFLiyd0FxSOS5TZJYV6qaNgGa9r1EAYWP96V\n\thQKg==","X-Gm-Message-State":"AHPjjUgOHU7+lyIH02BAHW9Q8bOEx1tsVutrVGB/bFRRKIZaByu27iEh\n\tmEys1fXf8pcGcBTlA2yruqw=","X-Google-Smtp-Source":"AOwi7QBZ8HYFxkq+xeicnFUpmKvqN/dZdyqTwtgKsO4rXNHE76y+O2ZiMAcRO1NFiIW61wJw+ixFuw==","X-Received":"by 10.25.169.19 with SMTP id s19mr12429lfe.235.1505942856667;\n\tWed, 20 Sep 2017 14:27:36 -0700 (PDT)","Date":"Thu, 21 Sep 2017 00:27:39 +0300","From":"Serge Semin <fancer.lancer@gmail.com>","To":"Rob Herring <robh@kernel.org>","Cc":"richard.leitner@skidata.com, gregkh@linuxfoundation.org,\n\tmark.rutland@arm.com, Sergey.Semin@t-platforms.ru,\n\tlinux-usb@vger.kernel.org, devicetree@vger.kernel.org,\n\tlinux-kernel@vger.kernel.org","Subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","Message-ID":"<20170920212739.GB3547@mobilestation>","References":"<20170915233113.17855-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-9-fancer.lancer@gmail.com>\n\t<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>","MIME-Version":"1.0","Content-Type":"text/plain; charset=us-ascii","Content-Disposition":"inline","In-Reply-To":"<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>","User-Agent":"Mutt/1.5.24 (2015-08-30)","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"<devicetree.vger.kernel.org>","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1772973,"web_url":"http://patchwork.ozlabs.org/comment/1772973/","msgid":"<CAL_Jsq+ftbGSQOOor_1L9NO9h7rjYm9nB26PxNOPgyHU6k3j_A@mail.gmail.com>","list_archive_url":null,"date":"2017-09-21T16:26:04","subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","submitter":{"id":62529,"url":"http://patchwork.ozlabs.org/api/people/62529/","name":"Rob Herring (Arm)","email":"robh@kernel.org"},"content":"On Wed, Sep 20, 2017 at 4:27 PM, Serge Semin <fancer.lancer@gmail.com> wrote:\n> On Wed, Sep 20, 2017 at 03:52:55PM -0500, Rob Herring <robh@kernel.org> wrote:\n>> On Sat, Sep 16, 2017 at 01:42:19PM +0300, Serge Semin wrote:\n>> > This parameters may be varied in accordance with hardware specifics.\n>> > So lets add the corresponding settings to the usb251x driver dts\n>> > specification.\n>> >\n>> > Signed-off-by: Serge Semin <fancer.lancer@gmail.com>\n>> > ---\n>> >  Documentation/devicetree/bindings/usb/usb251xb.txt   |  6 ++++++\n>> >  drivers/usb/misc/usb251xb.c                          | 20 ++++++++++++++++----\n>> >  2 files changed, 22 insertions(+), 4 deletions(-)\n>> >\n>> > diff --git a/Documentation/devicetree/bindings/usb/usb251xb.txt b/Documentation/devicetree/bindings/usb/usb251xb.txt\n>> > index 3d84626d3..dd59a32e7 100644\n>> > --- a/Documentation/devicetree/bindings/usb/usb251xb.txt\n>> > +++ b/Documentation/devicetree/bindings/usb/usb251xb.txt\n>> > @@ -44,6 +44,12 @@ Optional properties :\n>> >     device connected.\n>> >   - sp-disabled-ports : Specifies the ports which will be self-power disabled\n>> >   - bp-disabled-ports : Specifies the ports which will be bus-power disabled\n>> > + - sp-max-{power,current} : Indicates the power/current consumed by hub from\n>> > +   an upstream port (VBUS) when operation as a self-powered hub. The value\n>> > +   is given in mA in a 0 - 100 range (default is 1mA).\n>> > + - bp-max-{power,current} : Indicates the power/current consumed by hub from\n>> > +   an upstream port (VBUS) when operation as a bus-powered hub. The value\n>> > +   is given in mA in a 0 - 510 range (default is 100mA).\n>>\n>> These need units as defined in property-units.txt.\n>>\n>\n> Ok.\n>\n>> Why do you need power and current? Can't you calculate power?\n>>\n>\n> These are different parameters of the device. They got different configuration\n> registers and descriptions:\n> max_power* - ... This value also includes the power consumption of a\n> permanently attached peripheral if the hub is configured as a compound\n> device, and the embedded peripheral reports 0mA in its descriptors.\n> max_current* - ... This value does NOT include the power consumption of a\n> permanently attached peripheral if the hub is configured as a compound\n> device.\n\nThen the names here should somehow reflect the above. Perhaps\n\"composite-current\" and \"hub-current\" or something like that.\n\n>\n> Additionally as you can see, they both are measured in \"mA\", so it isn't\n> a real physical power.\n\nWell, I can't because there's no units.\n\nRob\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at  http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"<devicetree-owner@vger.kernel.org>","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=<UNKNOWN>)","mail.kernel.org;\n\tdmarc=none (p=none dis=none) header.from=kernel.org","mail.kernel.org;\n\tspf=none smtp.mailfrom=robh@kernel.org"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xyhnf1zbDz9t4B\n\tfor <incoming-dt@patchwork.ozlabs.org>;\n\tFri, 22 Sep 2017 02:26:30 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751629AbdIUQ02 (ORCPT\n\t<rfc822;incoming-dt@patchwork.ozlabs.org>);\n\tThu, 21 Sep 2017 12:26:28 -0400","from mail.kernel.org ([198.145.29.99]:40214 \"EHLO mail.kernel.org\"\n\trhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP\n\tid S1750790AbdIUQ01 (ORCPT <rfc822;devicetree@vger.kernel.org>);\n\tThu, 21 Sep 2017 12:26:27 -0400","from mail-qt0-f182.google.com (mail-qt0-f182.google.com\n\t[209.85.216.182])\n\t(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128\n\tbits)) (No client certificate requested)\n\tby mail.kernel.org (Postfix) with ESMTPSA id 8359C22A9A;\n\tThu, 21 Sep 2017 16:26:26 +0000 (UTC)","by mail-qt0-f182.google.com with SMTP id q4so6487839qtq.8;\n\tThu, 21 Sep 2017 09:26:26 -0700 (PDT)","by 10.12.209.75 with HTTP; Thu, 21 Sep 2017 09:26:04 -0700 (PDT)"],"DMARC-Filter":"OpenDMARC Filter v1.3.2 mail.kernel.org 8359C22A9A","X-Gm-Message-State":"AHPjjUhEjihrMaaFApiVheQDQLIquNa/HuJMGHtN1U/G0u6k/vraO7Lq\n\tMln86SXc3bSVII4krD3oYpcoWGC0qiKfUiJQ3A==","X-Google-Smtp-Source":"AOwi7QAcPPCHv43wfydQj2eFxSb5+C+o3X73rQEVwEM+JAIAoC5d+AMiCJHBl0xu70ecXpj6f+rVdvQ9AjfF9LnDuUM=","X-Received":"by 10.200.8.131 with SMTP id v3mr3904817qth.262.1506011185513;\n\tThu, 21 Sep 2017 09:26:25 -0700 (PDT)","MIME-Version":"1.0","In-Reply-To":"<20170920212739.GB3547@mobilestation>","References":"<20170915233113.17855-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-9-fancer.lancer@gmail.com>\n\t<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>\n\t<20170920212739.GB3547@mobilestation>","From":"Rob Herring <robh@kernel.org>","Date":"Thu, 21 Sep 2017 11:26:04 -0500","X-Gmail-Original-Message-ID":"<CAL_Jsq+ftbGSQOOor_1L9NO9h7rjYm9nB26PxNOPgyHU6k3j_A@mail.gmail.com>","Message-ID":"<CAL_Jsq+ftbGSQOOor_1L9NO9h7rjYm9nB26PxNOPgyHU6k3j_A@mail.gmail.com>","Subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","To":"Serge Semin <fancer.lancer@gmail.com>","Cc":"Richard Leitner <richard.leitner@skidata.com>,\n\tGreg Kroah-Hartman <gregkh@linuxfoundation.org>,\n\tMark Rutland <mark.rutland@arm.com>, Sergey.Semin@t-platforms.ru,\n\tLinux USB List <linux-usb@vger.kernel.org>,\n\t\"devicetree@vger.kernel.org\" <devicetree@vger.kernel.org>,\n\t\"linux-kernel@vger.kernel.org\" <linux-kernel@vger.kernel.org>","Content-Type":"text/plain; charset=\"UTF-8\"","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"<devicetree.vger.kernel.org>","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1773002,"web_url":"http://patchwork.ozlabs.org/comment/1773002/","msgid":"<20170921171022.GA13721@mobilestation>","list_archive_url":null,"date":"2017-09-21T17:10:22","subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","submitter":{"id":70038,"url":"http://patchwork.ozlabs.org/api/people/70038/","name":"Serge Semin","email":"fancer.lancer@gmail.com"},"content":"On Thu, Sep 21, 2017 at 11:26:04AM -0500, Rob Herring <robh@kernel.org> wrote:\n> On Wed, Sep 20, 2017 at 4:27 PM, Serge Semin <fancer.lancer@gmail.com> wrote:\n> > On Wed, Sep 20, 2017 at 03:52:55PM -0500, Rob Herring <robh@kernel.org> wrote:\n> >> On Sat, Sep 16, 2017 at 01:42:19PM +0300, Serge Semin wrote:\n> >> > This parameters may be varied in accordance with hardware specifics.\n> >> > So lets add the corresponding settings to the usb251x driver dts\n> >> > specification.\n> >> >\n> >> > Signed-off-by: Serge Semin <fancer.lancer@gmail.com>\n> >> > ---\n> >> >  Documentation/devicetree/bindings/usb/usb251xb.txt   |  6 ++++++\n> >> >  drivers/usb/misc/usb251xb.c                          | 20 ++++++++++++++++----\n> >> >  2 files changed, 22 insertions(+), 4 deletions(-)\n> >> >\n> >> > diff --git a/Documentation/devicetree/bindings/usb/usb251xb.txt b/Documentation/devicetree/bindings/usb/usb251xb.txt\n> >> > index 3d84626d3..dd59a32e7 100644\n> >> > --- a/Documentation/devicetree/bindings/usb/usb251xb.txt\n> >> > +++ b/Documentation/devicetree/bindings/usb/usb251xb.txt\n> >> > @@ -44,6 +44,12 @@ Optional properties :\n> >> >     device connected.\n> >> >   - sp-disabled-ports : Specifies the ports which will be self-power disabled\n> >> >   - bp-disabled-ports : Specifies the ports which will be bus-power disabled\n> >> > + - sp-max-{power,current} : Indicates the power/current consumed by hub from\n> >> > +   an upstream port (VBUS) when operation as a self-powered hub. The value\n> >> > +   is given in mA in a 0 - 100 range (default is 1mA).\n> >> > + - bp-max-{power,current} : Indicates the power/current consumed by hub from\n> >> > +   an upstream port (VBUS) when operation as a bus-powered hub. The value\n> >> > +   is given in mA in a 0 - 510 range (default is 100mA).\n> >>\n> >> These need units as defined in property-units.txt.\n> >>\n> >\n> > Ok.\n> >\n> >> Why do you need power and current? Can't you calculate power?\n> >>\n> >\n> > These are different parameters of the device. They got different configuration\n> > registers and descriptions:\n> > max_power* - ... This value also includes the power consumption of a\n> > permanently attached peripheral if the hub is configured as a compound\n> > device, and the embedded peripheral reports 0mA in its descriptors.\n> > max_current* - ... This value does NOT include the power consumption of a\n> > permanently attached peripheral if the hub is configured as a compound\n> > device.\n> \n> Then the names here should somehow reflect the above. Perhaps\n> \"composite-current\" and \"hub-current\" or something like that.\n> \n\nI left the naming in accordance with the device datasheet. I thought it would be\nbetter since the driver user would still need to consult with the device\ndocumentation to properly set them. I don't really get how the difference is reflected\nwith the naming declared there though. So what naming would you prefer then? Might be\nsomething like:\n{sp,bp}-max-total-current - for so named {sp,bp}-max-power, since it includes all the\npermanently attached peripherals.\n{sp,bp}-max-removable-current - for so named {sp,bp}-max-current, since it doesn't\ninclude the permanently attached peripherals.\n\nOr is it better to leave it in compliance with the documentation naming?\n\n> >\n> > Additionally as you can see, they both are measured in \"mA\", so it isn't\n> > a real physical power.\n> \n> Well, I can't because there's no units.\n> \n\nWhat this line means then?\n- sp-max-{power,current} : ... The value is given in mA in a 0 - 100 range (default is 1mA).\n- bp-max-{power,current} : ... The value is given in mA in a 0 - 510 range (default is 100mA).\n\nMaybe I don't know something and the description line should state the units somehow\nclearer?\n\n> Rob\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at  http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"<devicetree-owner@vger.kernel.org>","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=<UNKNOWN>)","ozlabs.org;\n\tdkim=fail reason=\"signature verification failed\" (2048-bit key;\n\tunprotected) header.d=gmail.com header.i=@gmail.com\n\theader.b=\"kQlabUe/\"; dkim-atps=neutral"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xyjmL6S2Sz9t5Y\n\tfor <incoming-dt@patchwork.ozlabs.org>;\n\tFri, 22 Sep 2017 03:10:26 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1752283AbdIURKY (ORCPT\n\t<rfc822;incoming-dt@patchwork.ozlabs.org>);\n\tThu, 21 Sep 2017 13:10:24 -0400","from mail-lf0-f66.google.com ([209.85.215.66]:37146 \"EHLO\n\tmail-lf0-f66.google.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1751871AbdIURKU (ORCPT\n\t<rfc822; devicetree@vger.kernel.org>); Thu, 21 Sep 2017 13:10:20 -0400","by mail-lf0-f66.google.com with SMTP id q132so3315847lfe.4;\n\tThu, 21 Sep 2017 10:10:19 -0700 (PDT)","from mobilestation ([95.79.181.62])\n\tby smtp.gmail.com with ESMTPSA id\n\ty184sm301398lfd.62.2017.09.21.10.10.17\n\t(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\n\tThu, 21 Sep 2017 10:10:18 -0700 (PDT)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;\n\th=date:from:to:cc:subject:message-id:references:mime-version\n\t:content-disposition:in-reply-to:user-agent;\n\tbh=xQk8BkM29tCeV+DfJH9RogdE3MU7L6waql1roYQvvNo=;\n\tb=kQlabUe/CR1zqVIMj/PjPTeIm/tiaWqyEfTNTYJcNkbOAvNXR/Rhb+YI/YP8cOLYgg\n\tyJ50PTcsqfQxArJA+4FSpX12u4vAYIBFDnXF+eAKpPq+uS/CLLh/0EbXNy/fX3d0hPbC\n\t0mf3sgixMXeFbj5ynwiIQVeJYUIY4uk3XV8mygvP68zfQvreuJjBIFLPH7vWGMqkzvHL\n\tOwgcAanlD16TR4MrucZSKMQ9T0qDaYGl5LpXvqBUbZGjm821MD1lD2FHfoOnURnbZMRe\n\t+pzdl7aa8/FlI+isXZ8yWFZZomWa3g7dmoKn7mfhWGN78wP+eSa43aSGM08E2NSTNhzV\n\tR0HA==","X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:in-reply-to:user-agent;\n\tbh=xQk8BkM29tCeV+DfJH9RogdE3MU7L6waql1roYQvvNo=;\n\tb=dihhWEyvni+xBqpm8gOJSe5QKL3kHfOsba9Brfnlq5Uxgzt1rNABrgQNA6WKNY9/5J\n\tg2b2ASIOj1QQXUvZcIDo1e8WRtN4iD/+rxL6SbBZuEHK0YKENYSOidagfuWp7Fg7kH7+\n\t5u4q9DC9hZhAK/DwHF0gwPx7yPhAwiwX0PQCCshPFKL+3WPhq3bE7BKKHf3On4lu9VMV\n\t7Er/PqtTWoHPgzrM/hcec/Z7uSRb/zSX2p53Ru7VyNX/e3Fp9nyvBRI1HVE7p3re6X66\n\tJGsQ8sBW81EDUn9D/6ZZvIwDCBH/GQLRJyWj2OWk14Xwm2xGEdVdzqO4AcpvBY5DpwBr\n\trrRw==","X-Gm-Message-State":"AHPjjUhIt6HUs1hnapzlYfp+NDYroxWFpPkGDOHL/kiOLK1mD6j5YRfh\n\tWUj5sFTpuc8AEadvyrhGY2o=","X-Google-Smtp-Source":"AOwi7QCQJl0aC+IJMycvZDiRgX5DdE+NEzfCn7gXlF38ubGBT2uUTyAO+6L/Foa+AneD969UHU3O1g==","X-Received":"by 10.46.2.19 with SMTP id 19mr1290094ljc.0.1506013818940;\n\tThu, 21 Sep 2017 10:10:18 -0700 (PDT)","Date":"Thu, 21 Sep 2017 20:10:22 +0300","From":"Serge Semin <fancer.lancer@gmail.com>","To":"Rob Herring <robh@kernel.org>","Cc":"Richard Leitner <richard.leitner@skidata.com>,\n\tGreg Kroah-Hartman <gregkh@linuxfoundation.org>,\n\tMark Rutland <mark.rutland@arm.com>, Sergey.Semin@t-platforms.ru,\n\tLinux USB List <linux-usb@vger.kernel.org>,\n\t\"devicetree@vger.kernel.org\" <devicetree@vger.kernel.org>,\n\t\"linux-kernel@vger.kernel.org\" <linux-kernel@vger.kernel.org>","Subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","Message-ID":"<20170921171022.GA13721@mobilestation>","References":"<20170915233113.17855-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-9-fancer.lancer@gmail.com>\n\t<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>\n\t<20170920212739.GB3547@mobilestation>\n\t<CAL_Jsq+ftbGSQOOor_1L9NO9h7rjYm9nB26PxNOPgyHU6k3j_A@mail.gmail.com>","MIME-Version":"1.0","Content-Type":"text/plain; charset=us-ascii","Content-Disposition":"inline","In-Reply-To":"<CAL_Jsq+ftbGSQOOor_1L9NO9h7rjYm9nB26PxNOPgyHU6k3j_A@mail.gmail.com>","User-Agent":"Mutt/1.5.24 (2015-08-30)","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"<devicetree.vger.kernel.org>","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1779499,"web_url":"http://patchwork.ozlabs.org/comment/1779499/","msgid":"<53559bc4-5faa-6797-7c12-f635049f1411@skidata.com>","list_archive_url":null,"date":"2017-10-04T08:12:51","subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","submitter":{"id":70889,"url":"http://patchwork.ozlabs.org/api/people/70889/","name":"Richard Leitner","email":"richard.leitner@skidata.com"},"content":"On 09/21/2017 07:10 PM, Serge Semin wrote:\n> On Thu, Sep 21, 2017 at 11:26:04AM -0500, Rob Herring <robh@kernel.org> wrote:\n>> On Wed, Sep 20, 2017 at 4:27 PM, Serge Semin <fancer.lancer@gmail.com> wrote:\n\n...\n\n>>> These are different parameters of the device. They got different configuration\n>>> registers and descriptions:\n>>> max_power* - ... This value also includes the power consumption of a\n>>> permanently attached peripheral if the hub is configured as a compound\n>>> device, and the embedded peripheral reports 0mA in its descriptors.\n>>> max_current* - ... This value does NOT include the power consumption of a\n>>> permanently attached peripheral if the hub is configured as a compound\n>>> device.\n>>\n>> Then the names here should somehow reflect the above. Perhaps\n>> \"composite-current\" and \"hub-current\" or something like that.\n>>\n> \n> I left the naming in accordance with the device datasheet. I thought it would be\n> better since the driver user would still need to consult with the device\n> documentation to properly set them. I don't really get how the difference is reflected\n> with the naming declared there though. So what naming would you prefer then? Might be\n> something like:\n> {sp,bp}-max-total-current - for so named {sp,bp}-max-power, since it includes all the\n> permanently attached peripherals.\n> {sp,bp}-max-removable-current - for so named {sp,bp}-max-current, since it doesn't\n> include the permanently attached peripherals.\n> \n> Or is it better to leave it in compliance with the documentation naming?\n\nI'd prefer the naming to be in accordance with the device datasheet too.\nChanging it will IMHO generate avoidable misunderstandings...\n\nBut if we should go with Robs proposal please make sure the name from\nthe device datasheet is mentioned somewhere in the description of the\nbinding.\n\n> \n>>>\n>>> Additionally as you can see, they both are measured in \"mA\", so it isn't\n>>> a real physical power.\n>>\n>> Well, I can't because there's no units.\n>>\n> \n> What this line means then?\n> - sp-max-{power,current} : ... The value is given in mA in a 0 - 100 range (default is 1mA).\n> - bp-max-{power,current} : ... The value is given in mA in a 0 - 510 range (default is 100mA).\n> \n> Maybe I don't know something and the description line should state the units somehow\n> clearer?\n\nAppend the unit to the binding name, just like in \"power-on-time-ms\". As\nthere's no \"Standard Unit Suffix\" for mA stated in the documentation\n(Documentation/devicetree/bindings/property-units.txt) I think it should\nbe \"-milliamp\"?\n\nregards,\nRichard.L\n\n\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at  http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"<devicetree-owner@vger.kernel.org>","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=<UNKNOWN>)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3y6TDS142Yz9sPr\n\tfor <incoming-dt@patchwork.ozlabs.org>;\n\tWed,  4 Oct 2017 19:13:12 +1100 (AEDT)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751401AbdJDIM5 (ORCPT\n\t<rfc822;incoming-dt@patchwork.ozlabs.org>);\n\tWed, 4 Oct 2017 04:12:57 -0400","from mail2.skidata.com ([91.230.2.91]:45017 \"EHLO\n\tmail2.skidata.com\"\n\trhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP\n\tid S1751120AbdJDIMy (ORCPT <rfc822;devicetree@vger.kernel.org>);\n\tWed, 4 Oct 2017 04:12:54 -0400"],"X-IronPort-AV":"E=Sophos;i=\"5.42,477,1500933600\"; d=\"scan'208\";a=\"1013709\"","Subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","To":"Serge Semin <fancer.lancer@gmail.com>, Rob Herring <robh@kernel.org>","CC":"Greg Kroah-Hartman <gregkh@linuxfoundation.org>,\n\tMark Rutland <mark.rutland@arm.com>, <Sergey.Semin@t-platforms.ru>,\n\tLinux USB List <linux-usb@vger.kernel.org>,\n\t\"devicetree@vger.kernel.org\" <devicetree@vger.kernel.org>,\n\t\"linux-kernel@vger.kernel.org\" <linux-kernel@vger.kernel.org>,\n\tRichard Leitner <richard.leitner@skidata.com>","References":"<20170915233113.17855-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-9-fancer.lancer@gmail.com>\n\t<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>\n\t<20170920212739.GB3547@mobilestation>\n\t<CAL_Jsq+ftbGSQOOor_1L9NO9h7rjYm9nB26PxNOPgyHU6k3j_A@mail.gmail.com>\n\t<20170921171022.GA13721@mobilestation>","From":"Richard Leitner <richard.leitner@skidata.com>","Message-ID":"<53559bc4-5faa-6797-7c12-f635049f1411@skidata.com>","Date":"Wed, 4 Oct 2017 10:12:51 +0200","User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101\n\tThunderbird/52.3.0","MIME-Version":"1.0","In-Reply-To":"<20170921171022.GA13721@mobilestation>","Content-Type":"text/plain; charset=\"utf-8\"","Content-Language":"en-US","Content-Transfer-Encoding":"8bit","X-Originating-IP":"[172.16.60.30]","X-ClientProxiedBy":"sdex1srv.skidata.net (172.16.10.92) To\n\tsdex1srv.skidata.net (172.16.10.92)","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"<devicetree.vger.kernel.org>","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1779825,"web_url":"http://patchwork.ozlabs.org/comment/1779825/","msgid":"<CAL_Jsq+Z+5xHu4k3iGGGqf2CHLDy6mo9-TbkiniY67=xEbJzNQ@mail.gmail.com>","list_archive_url":null,"date":"2017-10-04T13:44:27","subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","submitter":{"id":62529,"url":"http://patchwork.ozlabs.org/api/people/62529/","name":"Rob Herring (Arm)","email":"robh@kernel.org"},"content":"On Wed, Oct 4, 2017 at 3:12 AM, Richard Leitner\n<richard.leitner@skidata.com> wrote:\n>\n> On 09/21/2017 07:10 PM, Serge Semin wrote:\n>> On Thu, Sep 21, 2017 at 11:26:04AM -0500, Rob Herring <robh@kernel.org> wrote:\n>>> On Wed, Sep 20, 2017 at 4:27 PM, Serge Semin <fancer.lancer@gmail.com> wrote:\n>\n> ...\n>\n>>>> These are different parameters of the device. They got different configuration\n>>>> registers and descriptions:\n>>>> max_power* - ... This value also includes the power consumption of a\n>>>> permanently attached peripheral if the hub is configured as a compound\n>>>> device, and the embedded peripheral reports 0mA in its descriptors.\n>>>> max_current* - ... This value does NOT include the power consumption of a\n>>>> permanently attached peripheral if the hub is configured as a compound\n>>>> device.\n>>>\n>>> Then the names here should somehow reflect the above. Perhaps\n>>> \"composite-current\" and \"hub-current\" or something like that.\n>>>\n>>\n>> I left the naming in accordance with the device datasheet. I thought it would be\n>> better since the driver user would still need to consult with the device\n>> documentation to properly set them. I don't really get how the difference is reflected\n>> with the naming declared there though. So what naming would you prefer then? Might be\n>> something like:\n>> {sp,bp}-max-total-current - for so named {sp,bp}-max-power, since it includes all the\n>> permanently attached peripherals.\n>> {sp,bp}-max-removable-current - for so named {sp,bp}-max-current, since it doesn't\n>> include the permanently attached peripherals.\n>>\n>> Or is it better to leave it in compliance with the documentation naming?\n>\n> I'd prefer the naming to be in accordance with the device datasheet too.\n> Changing it will IMHO generate avoidable misunderstandings...\n\nOkay, then add a vendor prefix.\n\n> But if we should go with Robs proposal please make sure the name from\n> the device datasheet is mentioned somewhere in the description of the\n> binding.\n>\n>>\n>>>>\n>>>> Additionally as you can see, they both are measured in \"mA\", so it isn't\n>>>> a real physical power.\n>>>\n>>> Well, I can't because there's no units.\n>>>\n>>\n>> What this line means then?\n>> - sp-max-{power,current} : ... The value is given in mA in a 0 - 100 range (default is 1mA).\n>> - bp-max-{power,current} : ... The value is given in mA in a 0 - 510 range (default is 100mA).\n>>\n>> Maybe I don't know something and the description line should state the units somehow\n>> clearer?\n\nThe reason we have units in the name is so we don't have to go lookup\nthe documentation to find the units and so people don't use the same\nproperty name with different units.\n\n> Append the unit to the binding name, just like in \"power-on-time-ms\". As\n> there's no \"Standard Unit Suffix\" for mA stated in the documentation\n> (Documentation/devicetree/bindings/property-units.txt) I think it should\n> be \"-milliamp\"?\n\nThe reason being is we align around microamps and try to avoid\neveryone picking their own units (celliamps anyone?). So unless\nmicroamps is not enough range for you, I would stick with that.\n\nIf you have both units and vendor prefix, then I care less about the\npoorly written datasheet naming used.\n\nRob\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at  http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"<devicetree-owner@vger.kernel.org>","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=<UNKNOWN>)","mail.kernel.org;\n\tdmarc=none (p=none dis=none) header.from=kernel.org","mail.kernel.org;\n\tspf=none smtp.mailfrom=robh@kernel.org"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3y6cb909llz9t2l\n\tfor <incoming-dt@patchwork.ozlabs.org>;\n\tThu,  5 Oct 2017 00:44:53 +1100 (AEDT)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1752085AbdJDNou (ORCPT\n\t<rfc822;incoming-dt@patchwork.ozlabs.org>);\n\tWed, 4 Oct 2017 09:44:50 -0400","from mail.kernel.org ([198.145.29.99]:52816 \"EHLO mail.kernel.org\"\n\trhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP\n\tid S1752084AbdJDNou (ORCPT <rfc822;devicetree@vger.kernel.org>);\n\tWed, 4 Oct 2017 09:44:50 -0400","from mail-qt0-f182.google.com (mail-qt0-f182.google.com\n\t[209.85.216.182])\n\t(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128\n\tbits)) (No client certificate requested)\n\tby mail.kernel.org (Postfix) with ESMTPSA id 419FB218CC;\n\tWed,  4 Oct 2017 13:44:49 +0000 (UTC)","by mail-qt0-f182.google.com with SMTP id z50so14192929qtj.4;\n\tWed, 04 Oct 2017 06:44:49 -0700 (PDT)","by 10.12.186.148 with HTTP; Wed, 4 Oct 2017 06:44:27 -0700 (PDT)"],"DMARC-Filter":"OpenDMARC Filter v1.3.2 mail.kernel.org 419FB218CC","X-Gm-Message-State":"AMCzsaWXpN3zbWvNq1rCCenrmnApaefZYVztdmTxwy6hHGU4PHteDv8T\n\ttaNPI4gY2l2aUD1l3aXd2o146XLAZvmtR/BgHg==","X-Google-Smtp-Source":"AOwi7QC3RNu0mW8V0DRn0bVMIRORKHuvt5Vfd4FQPiiAB9JSP96Wa+WspTSBqEzJx+nadWS3VBxLjWmiA9zr0taRmcU=","X-Received":"by 10.200.56.252 with SMTP id g57mr3513068qtc.322.1507124688342; \n\tWed, 04 Oct 2017 06:44:48 -0700 (PDT)","MIME-Version":"1.0","In-Reply-To":"<53559bc4-5faa-6797-7c12-f635049f1411@skidata.com>","References":"<20170915233113.17855-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-1-fancer.lancer@gmail.com>\n\t<20170916104220.3742-9-fancer.lancer@gmail.com>\n\t<20170920205255.5txbub3y6v6avolh@rob-hp-laptop>\n\t<20170920212739.GB3547@mobilestation>\n\t<CAL_Jsq+ftbGSQOOor_1L9NO9h7rjYm9nB26PxNOPgyHU6k3j_A@mail.gmail.com>\n\t<20170921171022.GA13721@mobilestation>\n\t<53559bc4-5faa-6797-7c12-f635049f1411@skidata.com>","From":"Rob Herring <robh@kernel.org>","Date":"Wed, 4 Oct 2017 08:44:27 -0500","X-Gmail-Original-Message-ID":"<CAL_Jsq+Z+5xHu4k3iGGGqf2CHLDy6mo9-TbkiniY67=xEbJzNQ@mail.gmail.com>","Message-ID":"<CAL_Jsq+Z+5xHu4k3iGGGqf2CHLDy6mo9-TbkiniY67=xEbJzNQ@mail.gmail.com>","Subject":"Re: [PATCH 8/9 v2] usb: usb251xb: Add max power/current dts property\n\tsupport","To":"Richard Leitner <richard.leitner@skidata.com>","Cc":"Serge Semin <fancer.lancer@gmail.com>,\n\tGreg Kroah-Hartman <gregkh@linuxfoundation.org>,\n\tMark Rutland <mark.rutland@arm.com>, Sergey.Semin@t-platforms.ru,\n\tLinux USB List <linux-usb@vger.kernel.org>,\n\t\"devicetree@vger.kernel.org\" <devicetree@vger.kernel.org>,\n\t\"linux-kernel@vger.kernel.org\" <linux-kernel@vger.kernel.org>","Content-Type":"text/plain; charset=\"UTF-8\"","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"<devicetree.vger.kernel.org>","X-Mailing-List":"devicetree@vger.kernel.org"}}]