Received: by 10.192.165.148 with SMTP id m20csp4980392imm; Tue, 24 Apr 2018 11:34:08 -0700 (PDT) X-Google-Smtp-Source: AIpwx49X+XVzE8U+M2CsmVUqHLBDfqfVDk+kg/sgpSQKyMWitSS1TZQ5LXzDkqAO6WSlcCjHHspa X-Received: by 10.98.47.2 with SMTP id v2mr21226643pfv.239.1524594848060; Tue, 24 Apr 2018 11:34:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524594848; cv=none; d=google.com; s=arc-20160816; b=tRoc8FKeaVMNxwI0JyIdrbEFjj1GfydzlwgjOPNnqp/2nFHHTs1oljmDqTKu0sAcvL 1UDYdTnieaz74oNJShP/HfPQLSebQqlayKDIZLy4b9tUc5ZSEw3WsSpTxAzYbFokLF3X wZgYdlf9i+3arpR9iUAsIqD8A3aTJWCKncbGN4npsoPX+eP2YaLrxT9qKowWr3fTaNzk EB26QrkqUrhv3p7O3wMXd7Exw0AqgartsCd1BYs4m+WUV85rZHJGnTp55aS8Ju9MXMrO Mug3QLQSdEHwRm79o+QDmyqpJnzb+grxKf1jlrdbJpT4/dKG+/Gm+WunmaK7gCpQnkS2 3UXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=n4v2FBsG3Cu99/rESEjIihGO+cjcG5aT0v35/AdFxiY=; b=hqi9GofWFdvzHZnZKIUKAasgCbbBd6rODy+47UIsX0tiQQDrP8uSJd04AYY10MZvkM Zx9i0E5yLIRdEG3wIWh8ohTmD/DaiLeHnLOz+nm3JKjodY/9kLjxc7bATKamKE5IcsVv DBhdApvoiCT3H+Z+5I13q7/UeYFxl+niHIwTxbsNXtt47dUP9qb5ZbWTRiRhmFkRrlI+ oMkjMeT/8Xsv1rk6jd/KdWQ1rszWf+OkyVs5WgnD8PWw3Vl5YKCeW0jPGEmiz11lLzIs yaSEz1Yt03IrR4rb4JWDLbXSn+2uBrokqDzKgThO9UVLemLKS0EHvG46jNKJb06TWFLk UKdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@micronovasrl.com header.s=dkim header.b=v7xR/OF5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b6-v6si14413322plm.202.2018.04.24.11.33.53; Tue, 24 Apr 2018 11:34:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=temperror (no key for signature) header.i=@micronovasrl.com header.s=dkim header.b=v7xR/OF5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751500AbeDXSbt (ORCPT + 99 others); Tue, 24 Apr 2018 14:31:49 -0400 Received: from mail.micronovasrl.com ([212.103.203.10]:43314 "EHLO mail.micronovasrl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750938AbeDXSbr (ORCPT ); Tue, 24 Apr 2018 14:31:47 -0400 Received: from mail.micronovasrl.com (mail.micronovasrl.com [127.0.0.1]) by mail.micronovasrl.com (Postfix) with ESMTP id 078CAB0093F for ; Tue, 24 Apr 2018 20:31:46 +0200 (CEST) Authentication-Results: mail.micronovasrl.com (amavisd-new); dkim=pass reason="pass (just generated, assumed good)" header.d=micronovasrl.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=micronovasrl.com; h=content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:to:subject:subject; s=dkim; t= 1524594705; x=1525458706; bh=OJsRSTztkVU2ywllECM0Pz1mCeaqJvtE3eh NzzGFwAM=; b=v7xR/OF5ZlBA4y2iQKMR7eNi3T0HqiPNfXwSNFnMdx/CZ6gtzLd T9IDSF4BWBCaE8B6AjsQz/goiYDJkj1vWR9jpwOfgPQqUm3jc7GKnjuPwqwajbi/ fZIzmOUUHDwxqj39pajAqOYWwoG0cQvfCbp819tNYUgvsEjTiA/MsCmE= X-Virus-Scanned: Debian amavisd-new at mail.micronovasrl.com X-Spam-Flag: NO X-Spam-Score: -2.9 X-Spam-Level: X-Spam-Status: No, score=-2.9 tagged_above=-10 required=4.5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9] autolearn=unavailable autolearn_force=no Received: from mail.micronovasrl.com ([127.0.0.1]) by mail.micronovasrl.com (mail.micronovasrl.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9mp4ui7PlHcD for ; Tue, 24 Apr 2018 20:31:45 +0200 (CEST) Received: from [192.168.123.60] (unknown [192.168.123.60]) by mail.micronovasrl.com (Postfix) with ESMTPSA id E08B8B00348; Tue, 24 Apr 2018 20:31:43 +0200 (CEST) Subject: Re: [PATCH 7/7] ARM: dts: sun7i: Add dts file for the A20-linova1-7 HMI To: Maxime Ripard Cc: Thierry Reding , David Airlie , Chen-Yu Tsai , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org References: <1521662593-25468-1-git-send-email-giulio.benetti@micronovasrl.com> <1521662593-25468-7-git-send-email-giulio.benetti@micronovasrl.com> <20180322180508.my64gobhh5rc2x2m@flea> <8ef3b259-03b4-6987-286e-36ff627a8b76@micronovasrl.com> <20180424084137.7xfwji2gcibxavvt@flea> From: Giulio Benetti Message-ID: <03a02abb-e95c-b4ec-748f-907c0af67969@micronovasrl.com> Date: Tue, 24 Apr 2018 20:31:44 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180424084137.7xfwji2gcibxavvt@flea> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: it Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Maxime and all, I resend the e-mail since it was refused by some address(my phone composed it in HTML). Sorry. Il 24/04/2018 10:41, Maxime Ripard ha scritto: > Hi, > > On Mon, Apr 23, 2018 at 04:37:33PM +0200, Giulio Benetti wrote: >> Il 22/03/2018 19:05, Maxime Ripard ha scritto: >>> On Wed, Mar 21, 2018 at 09:03:13PM +0100, Giulio Benetti wrote: >>>> The A20-Linova1-7 HMI, also called Q027_2_F which is printed on production >>>> label, is an industrial Human Machine Interface. >>>> It features: >>>> - 512MB DDR RAM >>>> - 1 Sd-card >= 4GB >>>> - 1 Usb otg(programmable via software) with A-Usb Connector >>>> - 1 Usb host >>>> - 1 Buzzer >>>> - 1 Input for LiPo >>>> - 1 Relay to signal absence of power supply >>>> - 1 External Rtc with 56 bytes of ram + CR2032 battery >>>> - 1 7" 24-bits Tft 800x480 with PCap on >>>> - 1 Mono audio 1-watt amplifier >>>> - 1 RS485 port >>>> - 1 Power On Line through +12Vdc reaching 57.600baud, >>>> from where it can be supplied and placed in a network of 50 units >>>> - exposed jtag pins >>>> >>>> HMI is supplied from +12Vdc. >>>> Ethernet is absent, so for debugging, need to enable rndis on Usb otg >>>> port through an A-A usb cable. >>>> It comes in different flavours for connector types and can be found with >>>> umounted features as requested by customers. >>> >>> So this is essentially the same board than in patch 6, but with a >>> different screen? >>> >>> You should have a single DT then, and handle the two different panels >>> using DT overlays. >> >> Ok for having different DT overlays. >> But do I have to submit them as patches? Or keep them in my company's repo? >> I ask you this because this involves sending also patches for displays >> and other little modifications to mainline ex: >> - rgb888 pins >> - 2 simple-panels >> - 1 uart iomux pins >> etc. >> >> If I don't submit those overlays, the other patches wouldn't make sense >> alone as I've seen, just like rgb888 pins. > > We don't have a repo for overlays yet Ok I can provide them on my company Repo. But, sorry if insist(please don't kill me! :) ), I would try to explain better how it's made LiNova, because I think I didn't provide enough information about it: LiNova1 is not a board with various headers to connect other peripherals such display, pcap etc. It's an HMI that I would consider the same as a Tablet, because it has a plastic enclosure also. So I would like to understand how to manage it in the best way. Try to consider LiNova1 as a Tablet series, with following list: LiNova1 4.3" ctp LiNova1 7" ctp LiNova1 10.1" ctp LiNova1 4.3" rtp LiNova1 7" rtp LiNova1 10.1" rtp Every of those has a slightly different BOM, so they are 6 different boards with a common base(uP, ram). And same pcb. So I don't know if submit only the common base and provide separately on our github DT-overlays, or provide as many dts patches as the HMI number with a base dtsi. Basically Micronova provides entire system without the capability to hack hardware adding shields of various type. There are also other 2 LiNova: LiNova2 and LiNova3 So I understand that this could lead to 18 different dts files and 3 dtsi files. But with Tablet it should be the same way. For sure people would be more interested on famous tablets instead of our HMI. In the case I need to use dt-overlays, you mean .dto files with fragments inside loaded by u-boot or runtime, right? Sorry if I bother you again but I wanted to understand better. > >>>> +&usb_otg { >>>> + dr_mode = "otg"; >>> >>> You're saying that this is a USB-A connector? Then it's not OTG since >>> it doesn't have an ID pin, this is an host. >> >> Right, with a special overlay I will activate Usb Device for RNDIS, >> so modified as host > > That doesn't really make much sense. The USB OTG is wired only using a > daughter board? My fault, I've meant "peripheral" in one case and "host" in another case. Usually "host". Are there problem with this? There is no daughter board. Thank you very very much in advance for you patience :) -- Giulio Benetti CTO MICRONOVA SRL Sede: Via A. Niedda 3 - 35010 Vigonza (PD) Tel. 049/8931563 - Fax 049/8931346 Cod.Fiscale - P.IVA 02663420285 Capitale Sociale ? 26.000 i.v. Iscritta al Reg. Imprese di Padova N. 02663420285 Numero R.E.A. 258642 > > >> One last question: >> now I have some patch already reviewed-by. >> Do I have to re-submit entire patchset? > > Yes > > Maxime >