Re: [PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

Hi, On Wed, Jan 17, 2018 at 09:46:13PM +0800, Chen-Yu Tsai wrote: > > + for_each_available_child_of_node(port, ep) { > > + remote = of_graph_get_remote_port_parent(ep); > > + if (!remote) > > + continue; > > + > > + /* does

Re: [PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

Hi, On Wed, Jan 17, 2018 at 09:46:13PM +0800, Chen-Yu Tsai wrote: > > + for_each_available_child_of_node(port, ep) { > > + remote = of_graph_get_remote_port_parent(ep); > > + if (!remote) > > + continue; > > + > > + /* does

Re: [PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

On Tue, Jan 9, 2018 at 6:09 PM, Maxime Ripard wrote: > Now that we have a driver, we can make use of it. This is done by > adding a flag to our custom plane state that will trigger whether we should > use the frontend on that particular plane or not. > > The rest

Re: [PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

On Tue, Jan 9, 2018 at 6:09 PM, Maxime Ripard wrote: > Now that we have a driver, we can make use of it. This is done by > adding a flag to our custom plane state that will trigger whether we should > use the frontend on that particular plane or not. > > The rest is just plumbing to set up the

[PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

Now that we have a driver, we can make use of it. This is done by adding a flag to our custom plane state that will trigger whether we should use the frontend on that particular plane or not. The rest is just plumbing to set up the backend to not perform the DMA but receive its data from the

[PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

Now that we have a driver, we can make use of it. This is done by adding a flag to our custom plane state that will trigger whether we should use the frontend on that particular plane or not. The rest is just plumbing to set up the backend to not perform the DMA but receive its data from the