From: Felipe Balbi <balbi@ti.com>
To: Rob Herring <robh@kernel.org>,
Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@xilinx.com>
Cc: devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
Subject: Re: [PATCH 1/2] usb: doc: dwc3-xilinx: Add devicetree bindings
Date: Wed, 18 Nov 2015 17:02:53 -0600 [thread overview]
Message-ID: <87ziyagbc2.fsf@saruman.tx.rr.com> (raw)
In-Reply-To: <20151118225331.GA22325@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
Hi,
Rob Herring <robh@kernel.org> writes:
> On Wed, Nov 18, 2015 at 06:20:31PM +0530, Subbaraya Sundeep Bhatta wrote:
>> This patch adds binding doc for Xilinx DWC3 glue driver.
>>
>> Signed-off-by: Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
>
> I really dislike how the DWC3 binding has been done. The sub-node here
> is pointless. The only thing the outer node does is add clocks which
> should simply be part of the DWC3 node. Presumably the IP block needs
> some clocks...
>
> Anyway, it's self-contained within the DWC3, so I won't make you clean
> up the mess.
heh, it's definitely not pointless. We get a lot of free goodies by
doing it that way. I'm just not going to repeat it once again. But in
summary:
a) we force people to write glue layers for *only* their HW specific
details
b) there's really no way to abuse dwc3 core because there's no symbol
exported from dwc3 core to glue
c) PM (both system sleep and runtime) becomes a lot simpler with core
only caring about what PM details delivered by SNPS (e.g. Hibernation
mode from DWC3) and glue only has to consider the SoC integration parts
of PM (for OMAP that would be PRCM details, hwmod, etc).
I'm definitely not going to change dwc3 because it has made my life a
lot saner. Definitely a lot saner than MUSB. Besides, DTS is supposed to
describe the HW and that's, really, how the HW is.
There's a piece of HW which is somewhat platform agnostic and delivered
by SNPS as a black box (SNPS customers don't touch SNPS RTL) and there's
another piece of HW which bridges this dwc3 to the platform specific
details and integration context of the platform (for OMAP that would the
SYSCONFIG/SYSSTATUS registers, Clock autogating, PRCM, etc, etc etc).
So you _do_ in fact, have two separate pieces of HW which are SW visible
and controllable independently. They each have their own IRQs (though in
some SoCs they share the same line), they're own address space, yada
yada yada.
cheers
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@ti.com>
To: Rob Herring <robh@kernel.org>,
Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@xilinx.com>
Cc: <devicetree@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
Subject: Re: [PATCH 1/2] usb: doc: dwc3-xilinx: Add devicetree bindings
Date: Wed, 18 Nov 2015 17:02:53 -0600 [thread overview]
Message-ID: <87ziyagbc2.fsf@saruman.tx.rr.com> (raw)
In-Reply-To: <20151118225331.GA22325@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
Hi,
Rob Herring <robh@kernel.org> writes:
> On Wed, Nov 18, 2015 at 06:20:31PM +0530, Subbaraya Sundeep Bhatta wrote:
>> This patch adds binding doc for Xilinx DWC3 glue driver.
>>
>> Signed-off-by: Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
>
> I really dislike how the DWC3 binding has been done. The sub-node here
> is pointless. The only thing the outer node does is add clocks which
> should simply be part of the DWC3 node. Presumably the IP block needs
> some clocks...
>
> Anyway, it's self-contained within the DWC3, so I won't make you clean
> up the mess.
heh, it's definitely not pointless. We get a lot of free goodies by
doing it that way. I'm just not going to repeat it once again. But in
summary:
a) we force people to write glue layers for *only* their HW specific
details
b) there's really no way to abuse dwc3 core because there's no symbol
exported from dwc3 core to glue
c) PM (both system sleep and runtime) becomes a lot simpler with core
only caring about what PM details delivered by SNPS (e.g. Hibernation
mode from DWC3) and glue only has to consider the SoC integration parts
of PM (for OMAP that would be PRCM details, hwmod, etc).
I'm definitely not going to change dwc3 because it has made my life a
lot saner. Definitely a lot saner than MUSB. Besides, DTS is supposed to
describe the HW and that's, really, how the HW is.
There's a piece of HW which is somewhat platform agnostic and delivered
by SNPS as a black box (SNPS customers don't touch SNPS RTL) and there's
another piece of HW which bridges this dwc3 to the platform specific
details and integration context of the platform (for OMAP that would the
SYSCONFIG/SYSSTATUS registers, Clock autogating, PRCM, etc, etc etc).
So you _do_ in fact, have two separate pieces of HW which are SW visible
and controllable independently. They each have their own IRQs (though in
some SoCs they share the same line), they're own address space, yada
yada yada.
cheers
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-11-18 23:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 12:50 [PATCH 1/2] usb: doc: dwc3-xilinx: Add devicetree bindings Subbaraya Sundeep Bhatta
2015-11-18 12:50 ` Subbaraya Sundeep Bhatta
[not found] ` <1447851031-16241-1-git-send-email-sbhatta-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2015-11-18 22:53 ` Rob Herring
2015-11-18 22:53 ` Rob Herring
2015-11-18 23:02 ` Felipe Balbi [this message]
2015-11-18 23:02 ` Felipe Balbi
[not found] ` <87ziyagbc2.fsf-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
2015-11-19 1:24 ` Rob Herring
2015-11-19 1:24 ` Rob Herring
[not found] ` <CAL_JsqKE6f8DwvJQok=JGuzj5=9g8vrwY+wscLJkhFaG4229Mw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-19 4:59 ` Felipe Balbi
2015-11-19 4:59 ` Felipe Balbi
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=87ziyagbc2.fsf@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sbhatta@xilinx.com \
--cc=subbaraya.sundeep.bhatta@xilinx.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 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.