Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932415AbcDTIjw (ORCPT ); Wed, 20 Apr 2016 04:39:52 -0400 Received: from mail-cys01nam02on0059.outbound.protection.outlook.com ([104.47.37.59]:4352 "EHLO NAM02-CY1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751964AbcDTIjs (ORCPT ); Wed, 20 Apr 2016 04:39:48 -0400 Authentication-Results: spf=pass (sender IP is 149.199.60.100) smtp.mailfrom=xilinx.com; lists.infradead.org; dkim=none (message not signed) header.d=none;lists.infradead.org; dmarc=bestguesspass action=none header.from=xilinx.com; From: Appana Durga Kedareswara Rao To: Shubhrajyoti Datta CC: Rob Herring , Pawel Moll , "Mark Rutland" , Ian Campbell , Kumar Gala , "Michal Simek" , Soren Brinkmann , "vinod.koul@intel.com" , "dan.j.williams@intel.com" , Moritz Fischer , Laurent Pinchart , "luis@debethencourt.com" , Anirudha Sarangi , Punnaiah Choudary Kalluri , "dmaengine@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: RE: [PATCH 1/2] Documentation: DT: vdma: Add clock support for vdma Thread-Topic: [PATCH 1/2] Documentation: DT: vdma: Add clock support for vdma Thread-Index: AQHRmtUcT+O2WvI48kejn/QLVUZjhp+R+V4AgACOcUA= Date: Wed, 20 Apr 2016 08:39:40 +0000 Message-ID: References: <1461136800-20334-1-git-send-email-appanad@xilinx.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.23.95.210] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-RCIS-Action: ALLOW X-TM-AS-Product-Ver: IMSS-7.1.0.1224-8.0.0.1202-22272.005 X-TM-AS-User-Approved-Sender: Yes;Yes X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:149.199.60.100;IPV:NLI;CTRY:US;EFV:NLI;SFV:NSPM;SFS:(10009020)(6009001)(2980300002)(438002)(199003)(24454002)(13464003)(189002)(377454003)(5008740100001)(23676002)(6806005)(63266004)(19580405001)(19580395003)(54356999)(189998001)(106466001)(1720100001)(15975445007)(2900100001)(76176999)(106116001)(110136002)(2950100001)(50986999)(2920100001)(4326007)(6116002)(11100500001)(33656002)(5003600100002)(92566002)(55846006)(86362001)(586003)(2906002)(3846002)(1096002)(1220700001)(5004730100002)(102836003)(87936001)(50466002)(5250100002)(81166005)(107986001);DIR:OUT;SFP:1101;SCL:1;SRVR:SN1NAM02HT158;H:xsj-pvapsmtpgw02;FPR:;SPF:Pass;MLV:sfv;A:1;MX:1;LANG:en; X-MS-Office365-Filtering-Correlation-Id: 771ed02e-338e-4ffc-456e-08d368f7534c X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(8251501002);SRVR:SN1NAM02HT158; X-Microsoft-Antispam-PRVS: <75b78998ecca4d4589852d9d029e6353@SN1NAM02HT158.eop-nam02.prod.protection.outlook.com> X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(9101521026)(601004)(2401047)(13024025)(13023025)(13017025)(8121501046)(13015025)(5005006)(13018025)(3002001)(10201501046);SRVR:SN1NAM02HT158;BCL:0;PCL:0;RULEID:;SRVR:SN1NAM02HT158; X-Forefront-PRVS: 0918748D70 X-OriginatorOrg: xilinx.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Apr 2016 08:39:44.6813 (UTC) X-MS-Exchange-CrossTenant-Id: 657af505-d5df-48d0-8300-c31994686c5c X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=657af505-d5df-48d0-8300-c31994686c5c;Ip=[149.199.60.100];Helo=[xsj-pvapsmtpgw02] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM02HT158 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u3K8dxlE000574 Content-Length: 4040 Lines: 93 Hi Shubhrajyoti, > -----Original Message----- > From: Shubhrajyoti Datta [mailto:shubhrajyoti.datta@gmail.com] > Sent: Wednesday, April 20, 2016 1:30 PM > To: Appana Durga Kedareswara Rao > Cc: Rob Herring ; Pawel Moll ; > Mark Rutland ; Ian Campbell > ; Kumar Gala ; Michal > Simek ; Soren Brinkmann ; > vinod.koul@intel.com; dan.j.williams@intel.com; Appana Durga Kedareswara > Rao ; Moritz Fischer ; > Laurent Pinchart ; > luis@debethencourt.com; Anirudha Sarangi ; Punnaiah > Choudary Kalluri ; dmaengine@vger.kernel.org; > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm- > kernel@lists.infradead.org > Subject: Re: [PATCH 1/2] Documentation: DT: vdma: Add clock support for vdma > > On Wed, Apr 20, 2016 at 12:49 PM, Kedareswara rao Appana > wrote: > > This patch updates the binding doc with clock description for vdma. > > > > Signed-off-by: Kedareswara rao Appana > > --- > > Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt | 6 > > ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git > > a/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt > > b/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt > > index fcc2b65..e1c9019 100644 > > --- a/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt > > +++ b/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt > > @@ -21,6 +21,10 @@ Required properties: > > - dma-channel child node: Should have at least one channel and can have up > to > > two channels per device. This node specifies the properties of each > > DMA channel (see child node properties below). > > +- clocks: Input clock specifier. Refer to common clock bindings. > > +- clock-names: List of input clocks "axi_clk", "tx_clk", "txs_clk" (list of input > > + cloks may vary based on the ip configuration. see clock bindings > > + for more info). > > > > Required properties for VDMA: > > - xlnx,num-fstores: Should be the number of framebuffers as configured in > h/w. > > @@ -60,6 +64,8 @@ axi_vdma_0: axivdma@40030000 { > > xlnx,num-fstores = <0x8>; > > xlnx,flush-fsync = <0x1>; > > xlnx,addrwidth = <0x20>; > > + clocks = <&clk 0>, <&clk 1>, <&clk 2>; > > + clock-names = "axi_clk", "tx_clk", "txs_clk"; > > the module has > s_axi_lite_aclk Clock I AXI VDMA AXI4-Lite interface clock m_axi_mm2s_aclk > Clock I AXI VDMA MM2S clock m_axi_s2mm_aclk Clock I AXI VDMA S2MM clock > m_axis_mm2s_aclk Clock I AXI VDMA MM2S AXIS clock s_axis_s2mm_aclk > Clock I AXI VDMA S2MM AXIS clock > > I think a partial support is not wrong. It is not partial support the driver is supporting all the clocks available in the IP (please refer the patch 2 in the series). In the example I just putted clock names for TX path I mean when the IP is configured only with one channel. Will update the clock-names example with the all the supported clocks in the next version. > however we should keep the names same as the TRM. Why?? Why can't we use simple convenient names that refers to equivalent clocks of h/w I mean I used axi_clk instead of s_axi_lite_aclk, Used tx_clk instead of m_axi_mm2s_aclk, Used txs_clk instead of m_axis_mm2s_aclk. If it mandatory to use names as the TRM please let me know will update the same v2... Regards, Kedar. > > > > dma-channel@40030000 { > > compatible = "xlnx,axi-vdma-mm2s-channel"; > > interrupts = < 0 54 4 >; > > -- > > 2.1.2 > > > > > > _______________________________________________ > > linux-arm-kernel mailing list > > linux-arm-kernel@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel