From: Tao Ren <rentao.bupt@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 1/3] usb: gadget: aspeed: read vhub config from of_device_id
Date: Tue, 11 Feb 2020 18:37:47 -0800 [thread overview]
Message-ID: <20200212023746.GA9834@taoren-ubuntu-R90MNF91> (raw)
In-Reply-To: <746b08aabf7ea976a382ad2ca30fa10a095e7ed8.camel@kernel.crashing.org>
On Tue, Feb 11, 2020 at 09:50:42AM +0100, Benjamin Herrenschmidt wrote:
> On Mon, 2020-02-10 at 11:07 -0800, Tao Ren wrote:
> > > > This looks generally okay. We should wait for Ben's ack before
> > > > applying.
> > >
> > > Shouldn't we instead have DT fields indicating those values ?
> >
> > May I ask why we prefer adding dt fields (such as "aspeed,vhub-max-ports"
> > and "aspeed,vhub-max-endpoints") instead of assigning these values based
> > on aspeed family? For example, is it to allow users to set a smaller
> > number of ports/endpoints?
>
> It's not a strong drive but it makes it more convenient to add support
> to newer revisions if the only differences are those numbers.
Got it. Thanks for the clarify. Will send out v2 patches after more
testing.
> >
> > > Also we should add a DT representation for the various ID/strings of
> > > the hub itself so manufacturers can customize them.
> >
> > Sure. I will add DT nodes for vendor/product/device IDs/strings. As it's
> > not directly related to ast2600-support, shall I handle it in a separate
> > patch? Or I can include the patch in this patch series?
>
> Separate. Thanks !
Will take care of the change once this patch series is accepted.
Cheers,
Tao
>
> Cheers,
> Ben.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Tao Ren <rentao.bupt@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Joel Stanley <joel@jms.id.au>,
Mark Rutland <mark.rutland@arm.com>,
Felipe Balbi <balbi@kernel.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
devicetree <devicetree@vger.kernel.org>,
Andrew Jeffery <andrew@aj.id.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Colin Ian King <colin.king@canonical.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] usb: gadget: aspeed: read vhub config from of_device_id
Date: Tue, 11 Feb 2020 18:37:47 -0800 [thread overview]
Message-ID: <20200212023746.GA9834@taoren-ubuntu-R90MNF91> (raw)
In-Reply-To: <746b08aabf7ea976a382ad2ca30fa10a095e7ed8.camel@kernel.crashing.org>
On Tue, Feb 11, 2020 at 09:50:42AM +0100, Benjamin Herrenschmidt wrote:
> On Mon, 2020-02-10 at 11:07 -0800, Tao Ren wrote:
> > > > This looks generally okay. We should wait for Ben's ack before
> > > > applying.
> > >
> > > Shouldn't we instead have DT fields indicating those values ?
> >
> > May I ask why we prefer adding dt fields (such as "aspeed,vhub-max-ports"
> > and "aspeed,vhub-max-endpoints") instead of assigning these values based
> > on aspeed family? For example, is it to allow users to set a smaller
> > number of ports/endpoints?
>
> It's not a strong drive but it makes it more convenient to add support
> to newer revisions if the only differences are those numbers.
Got it. Thanks for the clarify. Will send out v2 patches after more
testing.
> >
> > > Also we should add a DT representation for the various ID/strings of
> > > the hub itself so manufacturers can customize them.
> >
> > Sure. I will add DT nodes for vendor/product/device IDs/strings. As it's
> > not directly related to ast2600-support, shall I handle it in a separate
> > patch? Or I can include the patch in this patch series?
>
> Separate. Thanks !
Will take care of the change once this patch series is accepted.
Cheers,
Tao
>
> Cheers,
> Ben.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Tao Ren <rentao.bupt@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Felipe Balbi <balbi@kernel.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
devicetree <devicetree@vger.kernel.org>,
Andrew Jeffery <andrew@aj.id.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Colin Ian King <colin.king@canonical.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] usb: gadget: aspeed: read vhub config from of_device_id
Date: Tue, 11 Feb 2020 18:37:47 -0800 [thread overview]
Message-ID: <20200212023746.GA9834@taoren-ubuntu-R90MNF91> (raw)
In-Reply-To: <746b08aabf7ea976a382ad2ca30fa10a095e7ed8.camel@kernel.crashing.org>
On Tue, Feb 11, 2020 at 09:50:42AM +0100, Benjamin Herrenschmidt wrote:
> On Mon, 2020-02-10 at 11:07 -0800, Tao Ren wrote:
> > > > This looks generally okay. We should wait for Ben's ack before
> > > > applying.
> > >
> > > Shouldn't we instead have DT fields indicating those values ?
> >
> > May I ask why we prefer adding dt fields (such as "aspeed,vhub-max-ports"
> > and "aspeed,vhub-max-endpoints") instead of assigning these values based
> > on aspeed family? For example, is it to allow users to set a smaller
> > number of ports/endpoints?
>
> It's not a strong drive but it makes it more convenient to add support
> to newer revisions if the only differences are those numbers.
Got it. Thanks for the clarify. Will send out v2 patches after more
testing.
> >
> > > Also we should add a DT representation for the various ID/strings of
> > > the hub itself so manufacturers can customize them.
> >
> > Sure. I will add DT nodes for vendor/product/device IDs/strings. As it's
> > not directly related to ast2600-support, shall I handle it in a separate
> > patch? Or I can include the patch in this patch series?
>
> Separate. Thanks !
Will take care of the change once this patch series is accepted.
Cheers,
Tao
>
> Cheers,
> Ben.
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-12 2:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 22:21 [PATCH 0/3] aspeed-g6: enable usb support rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-01-31 22:21 ` [PATCH 1/3] usb: gadget: aspeed: read vhub config from of_device_id rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-02-10 2:47 ` Joel Stanley
2020-02-10 2:47 ` Joel Stanley
2020-02-10 2:47 ` Joel Stanley
2020-02-10 7:27 ` Benjamin Herrenschmidt
2020-02-10 7:27 ` Benjamin Herrenschmidt
2020-02-10 7:27 ` Benjamin Herrenschmidt
2020-02-10 19:07 ` Tao Ren
2020-02-10 19:07 ` Tao Ren
2020-02-10 19:07 ` Tao Ren
2020-02-11 8:50 ` Benjamin Herrenschmidt
2020-02-11 8:50 ` Benjamin Herrenschmidt
2020-02-11 8:50 ` Benjamin Herrenschmidt
2020-02-12 2:37 ` Tao Ren [this message]
2020-02-12 2:37 ` Tao Ren
2020-02-12 2:37 ` Tao Ren
2020-02-10 19:16 ` Tao Ren
2020-02-10 19:16 ` Tao Ren
2020-02-10 19:16 ` Tao Ren
2020-01-31 22:21 ` [PATCH 2/3] usb: gadget: aspeed: add ast2600 vhub support rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-02-10 2:48 ` Joel Stanley
2020-02-10 2:48 ` Joel Stanley
2020-02-10 2:48 ` Joel Stanley
2020-02-10 7:29 ` Benjamin Herrenschmidt
2020-02-10 7:29 ` Benjamin Herrenschmidt
2020-02-10 7:29 ` Benjamin Herrenschmidt
2020-02-10 19:31 ` Tao Ren
2020-02-10 19:31 ` Tao Ren
2020-02-10 19:31 ` Tao Ren
2020-01-31 22:21 ` [PATCH 3/3] ARM: dts: aspeed-g6: add usb functions rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-01-31 22:21 ` rentao.bupt
2020-02-10 2:47 ` Joel Stanley
2020-02-10 2:47 ` Joel Stanley
2020-02-10 2:47 ` Joel Stanley
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=20200212023746.GA9834@taoren-ubuntu-R90MNF91 \
--to=rentao.bupt@gmail.com \
--cc=linux-aspeed@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.