Re: [PATCH 2/2] [media] exynos4-is: FIMC port parse should fail if there's no endpoint

2016-03-22 Thread Javier Martinez Canillas
Hello Sylwester, On 03/11/2016 10:03 AM, Sylwester Nawrocki wrote: > On 03/04/2016 09:20 PM, Javier Martinez Canillas wrote: >> The fimc_md_parse_port_node() function return 0 if an endpoint node is >> not found but according to Documentation/devicetree/bindings/graph.txt, >> a port must always ha

Re: [PATCH 2/2] [media] exynos4-is: FIMC port parse should fail if there's no endpoint

2016-03-11 Thread Javier Martinez Canillas
Hello Sylwester, On Fri, Mar 11, 2016 at 10:03 AM, Sylwester Nawrocki wrote: > On 03/04/2016 09:20 PM, Javier Martinez Canillas wrote: >> The fimc_md_parse_port_node() function return 0 if an endpoint node is >> not found but according to Documentation/devicetree/bindings/graph.txt, >> a port mus

Re: [PATCH 2/2] [media] exynos4-is: FIMC port parse should fail if there's no endpoint

2016-03-11 Thread Sylwester Nawrocki
On 03/04/2016 09:20 PM, Javier Martinez Canillas wrote: > The fimc_md_parse_port_node() function return 0 if an endpoint node is > not found but according to Documentation/devicetree/bindings/graph.txt, > a port must always have at least one enpoint. > > So return an -EINVAL errno code to the call

[PATCH 2/2] [media] exynos4-is: FIMC port parse should fail if there's no endpoint

2016-03-04 Thread Javier Martinez Canillas
The fimc_md_parse_port_node() function return 0 if an endpoint node is not found but according to Documentation/devicetree/bindings/graph.txt, a port must always have at least one enpoint. So return an -EINVAL errno code to the caller instead, so it knows that the port node parse failed due an inv