[{"id":1759298,"web_url":"http://patchwork.ozlabs.org/comment/1759298/","msgid":"<5996934.WE9heBV2Dy@avalon>","list_archive_url":null,"date":"2017-08-29T12:48:17","subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","submitter":{"id":11034,"url":"http://patchwork.ozlabs.org/api/people/11034/","name":"Laurent Pinchart","email":"laurent.pinchart@ideasonboard.com"},"content":"Hi Tony,\n\nThank you for the patch.\n\nOn Tuesday, 29 August 2017 00:19:14 EEST Tony Lindgren wrote:\n> On omap4 we're missing the fdif node with it's related \"ti,hwmods\"\n> property that the SoC interconnect code needs.\n> \n> Note that this will only show up as a bug with \"doesn't have\n> mpu register target base\" boot errors when the legacy platform\n> data is removed.\n> \n> Cc: Laurent Pinchart \n> Cc: Mauro Carvalho Chehab \n> Cc: Sakari Ailus \n> Signed-off-by: Tony Lindgren \n> ---\n> .../devicetree/bindings/media/ti-fdif.txt | 37 +++++++++++++++++++\n> arch/arm/boot/dts/omap4.dtsi | 7 ++++\n> 2 files changed, 44 insertions(+)\n> create mode 100644 Documentation/devicetree/bindings/media/ti-fdif.txt\n> \n> diff --git a/Documentation/devicetree/bindings/media/ti-fdif.txt\n> b/Documentation/devicetree/bindings/media/ti-fdif.txt new file mode 100644\n> --- /dev/null\n> +++ b/Documentation/devicetree/bindings/media/ti-fdif.txt\n> @@ -0,0 +1,37 @@\n> +Texas Instruments Face Detect (FDIF) binding\n> +\n> +FDD can be used for face detection on Texas Instruments SoCs.\n\nDid you mean s/FDD/FDIF/ ?\n\n> +Note that the fdif binding is currently only used by the SoC interconnect\n> +code to idle the module on init and no open source driver is available\n> +for fdif. Please update this documentation if that changes.\n\nDevice tree bindings should be driver-agnostic. I don't think this paragraph \nis needed.\n\n> +Required properties:\n> +\n> +compatible: Shall be one of the following:\n> +\t \"ti,omap4-fdif\"\n> +\n> +reg: Shall contain the device instance IO range\n> +\n> +interrupts: Shall contain the device instance interrupt\n> +\n> +\n> +Optional properties:\n> +\n> +reg-names: Shall contain the IO range names if multiple IO\n> +\t ranges are used by the SoC\n\nIs this ever the case on OMAP4 ? If not you can drop this property.\n\n> +ti,hwmods: Shall contain the TI interconnect module name if needed\n> +\t by the SoC\n\nAre there SoCs that don't need this ?\n\n> +Example:\n> +\n> +\tfdif: fdif@4a10a000 {\n> +\t\tcompatible = \"ti,omap4-fdif\";\n> +\t\treg = <0x4a10a000 0x200>;\n> +\t\tinterrupts = ;\n> +\t\tti,hwmods = \"fdif\";\n> +\t};\n> +\n> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi\n> --- a/arch/arm/boot/dts/omap4.dtsi\n> +++ b/arch/arm/boot/dts/omap4.dtsi\n> @@ -864,6 +864,13 @@\n> \t\t\t};\n> \t\t};\n> \n> +\t\tfdif: fdif@4a10a000 {\n> +\t\t\tcompatible = \"ti,omap4-fdif\";\n> +\t\t\treg = <0x4a10a000 0x200>;\n\nAccording to the OMAP4460 datasheet the register range is 0x390 bytes long.\n\n> +\t\t\tinterrupts = ;\n> +\t\t\tti,hwmods = \"fdif\";\n> +\t\t};\n> +\n> \t\ttimer1: timer@4a318000 {\n> \t\t\tcompatible = \"ti,omap3430-timer\";\n> \t\t\treg = <0x4a318000 0x80>;","headers":{"Return-Path":"","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=)","ozlabs.org;\n\tdkim=fail reason=\"signature verification failed\" (1024-bit key;\n\tunprotected) header.d=ideasonboard.com header.i=@ideasonboard.com\n\theader.b=\"TRutKVxU\"; dkim-atps=neutral"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xhT1w2BT2z9t33\n\tfor ;\n\tTue, 29 Aug 2017 22:47:48 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1752652AbdH2Mrp (ORCPT\n\t);\n\tTue, 29 Aug 2017 08:47:45 -0400","from galahad.ideasonboard.com ([185.26.127.97]:57187 \"EHLO\n\tgalahad.ideasonboard.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1751917AbdH2Mrn (ORCPT\n\t); Tue, 29 Aug 2017 08:47:43 -0400","from avalon.localnet (unknown [145.15.244.38])\n\tby galahad.ideasonboard.com (Postfix) with ESMTPSA id 47141201C5;\n\tTue, 29 Aug 2017 14:45:59 +0200 (CEST)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com;\n\ts=mail; t=1504010759;\n\tbh=yKl5WmAltJGnh/aY+CCHNWy6aRjsdw2rPy/P8S2W+fc=;\n\th=From:To:Cc:Subject:Date:In-Reply-To:References:From;\n\tb=TRutKVxU+iG51p6PJKOQQxi9fRjtPMxMQe6wBA6naLxk4rf+IvIsBsGwNYIlBKe+9\n\tj6RAuai3SV+TaUPwEw3gcQC9wqUtLPctGD9a08zk5+hZViKOHf3K8EdyUT4nIVtaDX\n\tXU7yGdF6EX4MFXfuYCbRY6DYtUs5CS65h2itErE0=","From":"Laurent Pinchart ","To":"Tony Lindgren ","Cc":"linux-omap@vger.kernel.org, =?iso-8859-1?q?Beno=EEt?=\n\tCousson , devicetree@vger.kernel.org,\n\tMauro Carvalho Chehab , \n\tSakari Ailus ","Subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","Date":"Tue, 29 Aug 2017 15:48:17 +0300","Message-ID":"<5996934.WE9heBV2Dy@avalon>","In-Reply-To":"<20170828211918.11573-14-tony@atomide.com>","References":"<20170828211918.11573-1-tony@atomide.com>\n\t<20170828211918.11573-14-tony@atomide.com>","MIME-Version":"1.0","Content-Transfer-Encoding":"7Bit","Content-Type":"text/plain; charset=\"us-ascii\"","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1759391,"web_url":"http://patchwork.ozlabs.org/comment/1759391/","msgid":"<20170829142941.GU6008@atomide.com>","list_archive_url":null,"date":"2017-08-29T14:29:42","subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","submitter":{"id":365,"url":"http://patchwork.ozlabs.org/api/people/365/","name":"Tony Lindgren","email":"tony@atomide.com"},"content":"* Laurent Pinchart [170829 05:48]:\n> On Tuesday, 29 August 2017 00:19:14 EEST Tony Lindgren wrote:\n> > On omap4 we're missing the fdif node with it's related \"ti,hwmods\"\n> > property that the SoC interconnect code needs.\n> > \n> > Note that this will only show up as a bug with \"doesn't have\n> > mpu register target base\" boot errors when the legacy platform\n> > data is removed.\n...\n\n> > --- /dev/null\n> > +++ b/Documentation/devicetree/bindings/media/ti-fdif.txt\n> > @@ -0,0 +1,37 @@\n> > +Texas Instruments Face Detect (FDIF) binding\n> > +\n> > +FDD can be used for face detection on Texas Instruments SoCs.\n> \n> Did you mean s/FDD/FDIF/ ?\n\nOops thanks for spotting that.\n\n> > +Note that the fdif binding is currently only used by the SoC interconnect\n> > +code to idle the module on init and no open source driver is available\n> > +for fdif. Please update this documentation if that changes.\n> \n> Device tree bindings should be driver-agnostic. I don't think this paragraph \n> is needed.\n\nOK will drop.\n\n> > +Required properties:\n> > +\n> > +compatible: Shall be one of the following:\n> > +\t \"ti,omap4-fdif\"\n> > +\n> > +reg: Shall contain the device instance IO range\n> > +\n> > +interrupts: Shall contain the device instance interrupt\n> > +\n> > +\n> > +Optional properties:\n> > +\n> > +reg-names: Shall contain the IO range names if multiple IO\n> > +\t ranges are used by the SoC\n> \n> Is this ever the case on OMAP4 ? If not you can drop this property.\n\nOh right, that's only for audio related devices in the abe l4\ninstance. Will drop.\n\n> > +ti,hwmods: Shall contain the TI interconnect module name if needed\n> > +\t by the SoC\n> \n> Are there SoCs that don't need this ?\n\nDaVinci or Keystone maybe? And I do have patches coming that will\nremove the need for \"ti,hwmods\" but that's still maybe 200 patches\naway or something..\n\n> > +Example:\n> > +\n> > +\tfdif: fdif@4a10a000 {\n> > +\t\tcompatible = \"ti,omap4-fdif\";\n> > +\t\treg = <0x4a10a000 0x200>;\n> > +\t\tinterrupts = ;\n> > +\t\tti,hwmods = \"fdif\";\n> > +\t};\n> > +\n> > diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi\n> > --- a/arch/arm/boot/dts/omap4.dtsi\n> > +++ b/arch/arm/boot/dts/omap4.dtsi\n> > @@ -864,6 +864,13 @@\n> > \t\t\t};\n> > \t\t};\n> > \n> > +\t\tfdif: fdif@4a10a000 {\n> > +\t\t\tcompatible = \"ti,omap4-fdif\";\n> > +\t\t\treg = <0x4a10a000 0x200>;\n> \n> According to the OMAP4460 datasheet the register range is 0x390 bytes long.\n\nOK we have it wrong in the legacy platform data then. And the module\nsize is 0x1000 in the hardware, so I'll use that.\n\nRegards,\n\nTony\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xhWJ73fRWz9t38\n\tfor ;\n\tWed, 30 Aug 2017 00:30:15 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1754344AbdH2O3s (ORCPT\n\t);\n\tTue, 29 Aug 2017 10:29:48 -0400","from muru.com ([72.249.23.125]:38390 \"EHLO muru.com\"\n\trhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP\n\tid S1754337AbdH2O3r (ORCPT );\n\tTue, 29 Aug 2017 10:29:47 -0400","from atomide.com (localhost [127.0.0.1])\n\tby muru.com (Postfix) with ESMTPS id 67538813A;\n\tTue, 29 Aug 2017 14:30:06 +0000 (UTC)"],"Date":"Tue, 29 Aug 2017 07:29:42 -0700","From":"Tony Lindgren ","To":"Laurent Pinchart ","Cc":"linux-omap@vger.kernel.org, =?utf-8?q?Beno=C3=AEt?=\n\tCousson , devicetree@vger.kernel.org,\n\tMauro Carvalho Chehab , \n\tSakari Ailus ","Subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","Message-ID":"<20170829142941.GU6008@atomide.com>","References":"<20170828211918.11573-1-tony@atomide.com>\n\t<20170828211918.11573-14-tony@atomide.com>\n\t<5996934.WE9heBV2Dy@avalon>","MIME-Version":"1.0","Content-Type":"text/plain; charset=us-ascii","Content-Disposition":"inline","In-Reply-To":"<5996934.WE9heBV2Dy@avalon>","User-Agent":"Mutt/1.8.3 (2017-05-23)","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1759553,"web_url":"http://patchwork.ozlabs.org/comment/1759553/","msgid":"<5659095.JaecBxseot@avalon>","list_archive_url":null,"date":"2017-08-29T17:13:40","subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","submitter":{"id":11034,"url":"http://patchwork.ozlabs.org/api/people/11034/","name":"Laurent Pinchart","email":"laurent.pinchart@ideasonboard.com"},"content":"Hi Tony,\n\nOn Tuesday, 29 August 2017 17:29:42 EEST Tony Lindgren wrote:\n> * Laurent Pinchart [170829 05:48]:\n> > On Tuesday, 29 August 2017 00:19:14 EEST Tony Lindgren wrote:\n> >> On omap4 we're missing the fdif node with it's related \"ti,hwmods\"\n> >> property that the SoC interconnect code needs.\n> >> \n> >> Note that this will only show up as a bug with \"doesn't have\n> >> mpu register target base\" boot errors when the legacy platform\n> >> data is removed.\n> \n> ...\n> \n> >> --- /dev/null\n> >> +++ b/Documentation/devicetree/bindings/media/ti-fdif.txt\n> >> @@ -0,0 +1,37 @@\n> >> +Texas Instruments Face Detect (FDIF) binding\n> >> +\n> >> +FDD can be used for face detection on Texas Instruments SoCs.\n> > \n> > Did you mean s/FDD/FDIF/ ?\n> \n> Oops thanks for spotting that.\n> \n> >> +Note that the fdif binding is currently only used by the SoC\n> >> interconnect\n> >> +code to idle the module on init and no open source driver is available\n> >> +for fdif. Please update this documentation if that changes.\n> > \n> > Device tree bindings should be driver-agnostic. I don't think this\n> > paragraph is needed.\n> \n> OK will drop.\n> \n> >> +Required properties:\n> >> +\n> >> +compatible: Shall be one of the following:\n> >> +\t \"ti,omap4-fdif\"\n> >> +\n> >> +reg: Shall contain the device instance IO range\n> >> +\n> >> +interrupts: Shall contain the device instance interrupt\n> >> +\n> >> +\n> >> +Optional properties:\n> >> +\n> >> +reg-names: Shall contain the IO range names if multiple IO\n> >> +\t ranges are used by the SoC\n> > \n> > Is this ever the case on OMAP4 ? If not you can drop this property.\n> \n> Oh right, that's only for audio related devices in the abe l4\n> instance. Will drop.\n> \n> >> +ti,hwmods: Shall contain the TI interconnect module name if needed\n> >> +\t by the SoC\n> > \n> > Are there SoCs that don't need this ?\n> \n> DaVinci or Keystone maybe? And I do have patches coming that will\n> remove the need for \"ti,hwmods\" but that's still maybe 200 patches\n> away or something..\n\nThat would be amazing :-)\n\n> >> +Example:\n> >> +\n> >> +\tfdif: fdif@4a10a000 {\n> >> +\t\tcompatible = \"ti,omap4-fdif\";\n> >> +\t\treg = <0x4a10a000 0x200>;\n> >> +\t\tinterrupts = ;\n> >> +\t\tti,hwmods = \"fdif\";\n> >> +\t};\n> >> +\n> >> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi\n> >> --- a/arch/arm/boot/dts/omap4.dtsi\n> >> +++ b/arch/arm/boot/dts/omap4.dtsi\n> >> @@ -864,6 +864,13 @@\n> >> \t\t\t};\n> >> \t\t};\n> >> \n> >> +\t\tfdif: fdif@4a10a000 {\n> >> +\t\t\tcompatible = \"ti,omap4-fdif\";\n> >> +\t\t\treg = <0x4a10a000 0x200>;\n> > \n> > According to the OMAP4460 datasheet the register range is 0x390 bytes\n> > long.\n> \n> OK we have it wrong in the legacy platform data then. And the module\n> size is 0x1000 in the hardware, so I'll use that.","headers":{"Return-Path":"","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=)","ozlabs.org;\n\tdkim=fail reason=\"signature verification failed\" (1024-bit key;\n\tunprotected) header.d=ideasonboard.com header.i=@ideasonboard.com\n\theader.b=\"eu8Z//OE\"; dkim-atps=neutral"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xhZwJ4S4Pz9s76\n\tfor ;\n\tWed, 30 Aug 2017 03:13:20 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751655AbdH2RNS (ORCPT\n\t);\n\tTue, 29 Aug 2017 13:13:18 -0400","from galahad.ideasonboard.com ([185.26.127.97]:58110 \"EHLO\n\tgalahad.ideasonboard.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1751641AbdH2RNR (ORCPT\n\t); Tue, 29 Aug 2017 13:13:17 -0400","from avalon.localnet (85-76-13-67-nat.elisa-mobile.fi\n\t[85.76.13.67])\n\tby galahad.ideasonboard.com (Postfix) with ESMTPSA id 2E617201C5;\n\tTue, 29 Aug 2017 19:11:32 +0200 (CEST)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com;\n\ts=mail; t=1504026692;\n\tbh=qd8wkbNdIfSZ7LeyaJjPREX+idgseDP4U/EqtnyfZO8=;\n\th=From:To:Cc:Subject:Date:In-Reply-To:References:From;\n\tb=eu8Z//OEGIW7+ondyF13itYlIOT4FSboz7T4Qfft8wokEwFo/fqDktnXFqL3lI5is\n\tOEKQY232GpjB7yv6pwXZ6MIE7lCC5UCSognFLqBT/w/nUQ03K/7yv+SLWXrAzbYagU\n\tXCmKpHb+Np33mmCFeOJDKMDrLvzSJ4643xe9fp5g=","From":"Laurent Pinchart ","To":"Tony Lindgren ","Cc":"linux-omap@vger.kernel.org, =?iso-8859-1?q?Beno=EEt?=\n\tCousson , devicetree@vger.kernel.org,\n\tMauro Carvalho Chehab , \n\tSakari Ailus ","Subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","Date":"Tue, 29 Aug 2017 20:13:40 +0300","Message-ID":"<5659095.JaecBxseot@avalon>","In-Reply-To":"<20170829142941.GU6008@atomide.com>","References":"<20170828211918.11573-1-tony@atomide.com>\n\t<5996934.WE9heBV2Dy@avalon> <20170829142941.GU6008@atomide.com>","MIME-Version":"1.0","Content-Transfer-Encoding":"7Bit","Content-Type":"text/plain; charset=\"us-ascii\"","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1759606,"web_url":"http://patchwork.ozlabs.org/comment/1759606/","msgid":"<20170829190107.GE6008@atomide.com>","list_archive_url":null,"date":"2017-08-29T19:01:07","subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","submitter":{"id":365,"url":"http://patchwork.ozlabs.org/api/people/365/","name":"Tony Lindgren","email":"tony@atomide.com"},"content":"* Laurent Pinchart [170829 10:13]:\n> On Tuesday, 29 August 2017 17:29:42 EEST Tony Lindgren wrote:\n> > > Are there SoCs that don't need this ?\n> > \n> > DaVinci or Keystone maybe? And I do have patches coming that will\n> > remove the need for \"ti,hwmods\" but that's still maybe 200 patches\n> > away or something..\n> \n> That would be amazing :-)\n\nYeah.. FYI, the way to get there is to have a generic interonnect\ntarget agent driver for the module, then have the device ip\ninstance(s) just be children of the interconnect target. But\nit will be a while until I can start posting those patches.\n\nUntil that's available, we can have minimal device specific\ninterconnect target module drivers just like we have\ndrivers/usb/musb/musb_am335x.c. That's the parent for two\nmusb instances and one cppi41 dma instance. See also the\nrelated \"usb@47400000\" node in am33xx.dtsi and it's children.\n\nRegards,\n\nTony\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xhdJm6KRYz9sPk\n\tfor ;\n\tWed, 30 Aug 2017 05:01:12 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751264AbdH2TBL (ORCPT\n\t);\n\tTue, 29 Aug 2017 15:01:11 -0400","from muru.com ([72.249.23.125]:38666 \"EHLO muru.com\"\n\trhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP\n\tid S1751186AbdH2TBK (ORCPT );\n\tTue, 29 Aug 2017 15:01:10 -0400","from atomide.com (localhost [127.0.0.1])\n\tby muru.com (Postfix) with ESMTPS id 56FEC813A;\n\tTue, 29 Aug 2017 19:01:31 +0000 (UTC)"],"Date":"Tue, 29 Aug 2017 12:01:07 -0700","From":"Tony Lindgren ","To":"Laurent Pinchart ","Cc":"linux-omap@vger.kernel.org, =?utf-8?q?Beno=C3=AEt?=\n\tCousson , devicetree@vger.kernel.org,\n\tMauro Carvalho Chehab , \n\tSakari Ailus ","Subject":"Re: [PATCH 13/17] ARM: dts: Add missing fdif node and binding for\n\tomap4","Message-ID":"<20170829190107.GE6008@atomide.com>","References":"<20170828211918.11573-1-tony@atomide.com>\n\t<5996934.WE9heBV2Dy@avalon> <20170829142941.GU6008@atomide.com>\n\t<5659095.JaecBxseot@avalon>","MIME-Version":"1.0","Content-Type":"text/plain; charset=us-ascii","Content-Disposition":"inline","In-Reply-To":"<5659095.JaecBxseot@avalon>","User-Agent":"Mutt/1.8.3 (2017-05-23)","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"devicetree@vger.kernel.org"}}]