[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59055782-7fc2-4b16-af8b-a56fb845a43f@gmail.com>
Date: Thu, 15 Aug 2019 03:15:55 +0200
From: Vicente Bergas <vicencb@...il.com>
To: Robin Murphy <robin.murphy@....com>,
Felipe Balbi <balbi@...nel.org>
Cc: Heiko Stuebner <heiko@...ech.de>,
Will Deacon <will.deacon@....com>,
Marc Zyngier <marc.zyngier@....com>,
Catalin Marinas <catalin.marinas@....com>,
Matthias Brugger <mbrugger@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
<linux-usb@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-rockchip@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: kexec on rk3399
On Wednesday, August 14, 2019 3:12:26 PM CEST, Robin Murphy wrote:
> On 14/08/2019 13:53, Vicente Bergas wrote:
>> On Monday, July 22, 2019 4:31:27 PM CEST, Vicente Bergas wrote: ...
>
> This particular change looks like it's implicitly specific to
> RK3399, which wouldn't be ideal. Presumably if the core dwc3
> driver implemented shutdown correctly (echoing parts of
> dwc3_remove(), I guess) then the glue layers shouldn't need
> anything special anyway.
>
> Robin.
I just checked simple->resets from dwc3-of-simple.c and it is an array
with multiple resets whereas dwc->reset from core.c is NULL.
So the reset seems specific to the glue layers.
Is there another way than resetting the thing that is
generic enough to go to core.c and allows kexec?
Powered by blists - more mailing lists