[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h83rj4ha.fsf@gmail.com>
Date: Tue, 29 Oct 2019 11:17:05 +0200
From: Felipe Balbi <balbi@...nel.org>
To: John Stultz <john.stultz@...aro.org>,
lkml <linux-kernel@...r.kernel.org>
Cc: John Stultz <john.stultz@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
ShuFan Lee <shufan_lee@...htek.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Chunfeng Yun <chunfeng.yun@...iatek.com>,
Yu Chen <chenyu56@...wei.com>,
Hans de Goede <hdegoede@...hat.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Jun Li <lijun.kernel@...il.com>,
Valentin Schneider <valentin.schneider@....com>,
Jack Pham <jackp@...eaurora.org>, linux-usb@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v4 6/9] usb: dwc3: Rework resets initialization to be more flexible
Hi,
John Stultz <john.stultz@...aro.org> writes:
> The dwc3 core binding specifies one reset.
>
> However some variants of the hardware my not have more.
^^
may
According to synopsys databook, there's a single *input* reset signal on
this IP. What is this extra reset you have?
Is this, perhaps, specific to your glue layer around the synopsys ip?
Should, perhaps, your extra reset be managed by the glue layer?
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)
Powered by blists - more mailing lists