TD;
bd0->mode.count = sizeof(*context) / 4;
bd0->buffer_addr = sdma->context_phys;
bd0->ext_buffer_addr = 2048 + (sizeof(*context) / 4) * channel;
On 2019-06-11 at 17:30 +, Sven Van Asbroeck wrote:
> On Tue, Jun 11, 2019 at 5:09 AM Robin Gong
> wrote:
&
PU1_DI1>;
clock-names = "bus", "di0", "di1";
resets = <&src 2>;
-
+ status = "disabled";
ipu1_csi0: port@0 {
reg = <0>;
> -Original Message-
> From: Sven Van Asbroeck
> Sent: 2019年6月10日 23:47
> To: Robin Gong
> Subject: Re: [v8] media: imx: add mem2mem device
> On Mon, Jun 10, 2019 at 5:09 AM Robin Gong wrote:
> >
> > I can reproduce once enable your config to build firmw
> -Original Message-
> From: Sven Van Asbroeck
> Sent: 2019年6月6日 21:35
> On Wed, Jun 5, 2019 at 10:32 PM Robin Gong wrote:
> >
> > So that's another issue that I can't reproduce. How do you switch
> > between sdma ROM/RAM firmware load? Just
> -Original Message-
> From: Sven Van Asbroeck
> Sent: 2019年6月5日 21:52
> On Wed, Jun 5, 2019 at 6:08 AM Robin Gong wrote:
> >
> > Hi Sven,
> > I met below crash on v5.2-rc1 and found it's related with
> > commit 728e0fbf263e, after googl
0: e80b2000 e80b3c00 c0264c6c c01834b0 800d0013
> -Original Message-
> From: Sven Van Asbroeck
> Sent: 2019年6月5日 1:57>
> Hi Robin,
>
> On Tue, Jun 4, 2019 at 4:51 AM Robin Gong wrote:
> >
> > Hi Sven,
> > I saw similar kernel cra
2019年6月1日 5:59
> Hi Robin,
>
> On Thu, May 30, 2019 at 8:26 PM Robin Gong wrote:
> > What's soc chip and board you used? Could you post log?
>
> The mainline kernel we've been using does not have any sdma firmware, and
> as a result we get this in the
Hi Sven,
What's soc chip and board you used? Could you post log?
> -Original Message-
> From: Fabio Estevam
> Sent: 2019年5月31日 6:18
> To: Sven Van Asbroeck ; Robin Gong
>
> Cc: Nicolas Dufresne ; Philipp Zabel
> ; linux-media ; Hans
> Verkuil ; th
