<div dir='auto'><div>Hi Maxime, <br><div class="gmail_extra"><br><div class="gmail_quote">Il 24 apr 2018 10:41, Maxime Ripard <maxime.ripard@bootlin.com> ha scritto:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hi,
<br>
<br>
On Mon, Apr 23, 2018 at 04:37:33PM +0200, Giulio Benetti wrote:
<br>
> Il 22/03/2018 19:05, Maxime Ripard ha scritto:
<br>
> > On Wed, Mar 21, 2018 at 09:03:13PM +0100, Giulio Benetti wrote:
<br>
> > > The A20-Linova1-7 HMI, also called Q027_2_F which is printed on production
<br>
> > > label, is an industrial Human Machine Interface.
<br>
> > > It features:
<br>
> > > - 512MB DDR RAM
<br>
> > > - 1 Sd-card >= 4GB
<br>
> > > - 1 Usb otg(programmable via software) with A-Usb Connector
<br>
> > > - 1 Usb host
<br>
> > > - 1 Buzzer
<br>
> > > - 1 Input for LiPo
<br>
> > > - 1 Relay to signal absence of power supply
<br>
> > > - 1 External Rtc with 56 bytes of ram + CR2032 battery
<br>
> > > - 1 7" 24-bits Tft 800x480 with PCap on
<br>
> > > - 1 Mono audio 1-watt amplifier
<br>
> > > - 1 RS485 port
<br>
> > > - 1 Power On Line through +12Vdc reaching 57.600baud,
<br>
> > > from where it can be supplied and placed in a network of 50 units
<br>
> > > - exposed jtag pins
<br>
> > >
<br>
> > > HMI is supplied from +12Vdc.
<br>
> > > Ethernet is absent, so for debugging, need to enable rndis on Usb otg
<br>
> > > port through an A-A usb cable.
<br>
> > > It comes in different flavours for connector types and can be found with
<br>
> > > umounted features as requested by customers.
<br>
> >
<br>
> > So this is essentially the same board than in patch 6, but with a
<br>
> > different screen?
<br>
> >
<br>
> > You should have a single DT then, and handle the two different panels
<br>
> > using DT overlays.
<br>
>
<br>
> Ok for having different DT overlays.
<br>
> But do I have to submit them as patches? Or keep them in my company's repo?
<br>
> I ask you this because this involves sending also patches for displays
<br>
> and other little modifications to mainline ex:
<br>
> - rgb888 pins
<br>
> - 2 simple-panels
<br>
> - 1 uart iomux pins
<br>
> etc.
<br>
>
<br>
> If I don't submit those overlays, the other patches wouldn't make sense
<br>
> alone as I've seen, just like rgb888 pins.
<br>
<br>
We don't have a repo for overlays yet
<br></p></blockquote></div></div></div><div dir="auto">Ok I can provide them on my company Repo. </div><div dir="auto"><br></div><div dir="auto">But, sorry if insist, I would try to explain better how it's made LiNova, because I think I didn't provide enough information about it:</div><div dir="auto">LiNova1 is not a board with various headers to connect other peripherals such display, pcap etc. </div><div dir="auto">It's an HMI that I would consider the same as a Tablet, because it has a plastic enclosure also. </div><div dir="auto"><br></div><div dir="auto">So I would like to understand how to manage it in the best way. </div><div dir="auto">Try to consider LiNova1 as a Tablet series, with following list:</div><div dir="auto">LiNova1 4.3" ctp</div><div dir="auto">LiNova1 7" ctp</div><div dir="auto">LiNova1 10.1" ctp</div><div dir="auto">LiNova1 4.3" rtp</div><div dir="auto">LiNova1 7" rtp</div><div dir="auto">LiNova1 10.1" rtp</div><div dir="auto"><br></div><div dir="auto">Every of those has a slightly different BOM, so they are 6 different boards with a common base(uP, ram). And same pcb. </div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">Basically Micronova provides entire system without the capability to hack hardware adding shields of various type.</div><div dir="auto"><br></div><div dir="auto">There are also other 2 LiNova:</div><div dir="auto">LiNova2 and LiNova3</div><div dir="auto"><br></div><div dir="auto">So I understand that this could lead to 18 different dts files and 3 dtsi files. </div><div dir="auto"><br></div><div dir="auto">But with Tablet it should be the same way. </div><div dir="auto">For sure people would be more interested on famous tablets instead of our HMI. </div><div dir="auto"><br></div><div dir="auto">Sorry if I bother you again but I wanted to understand better. </div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">
<br>
> > > +&usb_otg {
<br>
> > > + dr_mode = "otg";
<br>
> >
<br>
> > You're saying that this is a USB-A connector? Then it's not OTG since
<br>
> > it doesn't have an ID pin, this is an host.
<br>
>
<br>
> Right, with a special overlay I will activate Usb Device for RNDIS,
<br>
> so modified as host
<br>
<br>
That doesn't really make much sense. The USB OTG is wired only using a
<br>
daughter board?
<br></p></blockquote></div></div></div><div dir="auto">My fault, I've meant "peripheral" in one case and "host" in another case. </div><div dir="auto">Usually "host". </div><div dir="auto">Are there problem with this? </div><div dir="auto">I can't understand why it shouldn't make sense. </div><div dir="auto">There is no daughter board. </div><div dir="auto"><br></div><div dir="auto">Thank you very much in advance for you patience :) </div><div dir="auto"><br></div><div dir="auto">Giulio </div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">
<br>
<br>
> One last question:
<br>
> now I have some patch already reviewed-by.
<br>
> Do I have to re-submit entire patchset?
<br>
<br>
Yes
<br>
<br>
Maxime
<br>
<br>
--
<br>
Maxime Ripard, Bootlin (formerly Free Electrons)
<br>
Embedded Linux and Kernel engineering
<br>
https://bootlin.com
<br>
</p>
</blockquote></div><br></div></div></div>