From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: u-boot@lists.denx.de
Subject: [PATCH 4/5] sun7i: add support for Micronova srl s027_3 board
Date: Fri, 19 Feb 2021 12:10:10 +0100 [thread overview]
Message-ID: <99c5198e-7c75-c301-e35b-252d55e51e1e@benettiengineering.com> (raw)
In-Reply-To: <1351fdc4-3c7c-bc3f-83ed-f70c175018d5@eurek.it>
Hi Gianluca,
On 2/19/21 11:38 AM, gianluca wrote:
> On 2/19/21 11:18 AM, Giulio Benetti wrote:
>> On 2/19/21 11:12 AM, Giulio Benetti wrote:
>>> Hi Andre,
>>>
>>> On 2/19/21 2:44 AM, Andre Przywara wrote:
>>>> On Fri, 19 Feb 2021 00:26:19 +0100
>>>> Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
>>>>
>>>> Hi Giulio,
>>>>
>>>>> From: Giulio Benetti <giulio.benetti@micronovasrl.com>
>>>>>
>>>>> Add support for Micronova srl s027_3 board by adding new vendor/board
>>>>> folders and using in local Makefile the already present
>>>>> board/sunxi/Makefile. The reason is that s027_3 needs a pin to be
>>>>> asserted
>>>>> to enable lcd before setting controller up and sunxi board doesn't
>>>>> provide
>>>>> a way to do this customization.
>>>>
>>>> Have you tried CONFIG_VIDEO_LCD_POWER?
>>>
>>> Yes, I already use that for DISPONOFF.
>>>
>>>> I am strongly against introducing per-board code files, and we
>>>> definitely won't introduce them just for one GPIO.
>>>
>>> I knew it was a strange hack, but I have 2 different pins to be set high
>>> before init video controller. Another idea that comes into my mind is to
>>> handle CONFIG_VIDEO_LCD_POWER as a gpio list and iterate/enable, what
>>> about that?
>>
>> Or introduce CONFIG_VIDEO_LCD_ENABLE, that would be easier. Here is the
>> schematic of my lcd connector to understand:
>> https://pasteboard.co/JP3PiYo.png
>>
>> I have net LCD_PWR that should be CONFIG_VIDEO_LCD_POWER, while
>> net LCD0_DISPONOFF should be CONFIG_VIDEO_LCD_ENABLE.
>>
>> At least this is my idea. Do you have any suggestion to make it work?
>>
>
> May I say a word?
Of course!
> Is it possible to wire the LCD0_DISPONOFF (I suppose it is high active)
> with the same pin routed to a SN74LVC1G04 to the pullup thru the Q6
> Transistor?
>
> Supposed there is no such timing restritctions
Unfortunately board can't be changed, thanks though.
Best regards
--
Giulio Benetti
Benetti Engineering sas
next prev parent reply other threads:[~2021-02-19 11:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 23:26 [PATCH 0/5] Add Micronova srl S027_3 board support Giulio Benetti
2021-02-18 23:26 ` [PATCH 1/5] arm: allwinner: dts: a20: add uart2_pa_pins Giulio Benetti
2021-02-19 11:04 ` Andre Przywara
2021-02-19 11:45 ` Giulio Benetti
2021-02-18 23:26 ` [PATCH 2/5] sunxi: allow SYS_BOARD to be set Giulio Benetti
2021-02-18 23:26 ` [PATCH 3/5] sunxi: add SYS_VENDOR to Kconfig Giulio Benetti
2021-02-18 23:26 ` [PATCH 4/5] sun7i: add support for Micronova srl s027_3 board Giulio Benetti
2021-02-19 1:44 ` Andre Przywara
2021-02-19 10:12 ` Giulio Benetti
2021-02-19 10:18 ` Giulio Benetti
2021-02-19 10:38 ` gianluca
2021-02-19 11:10 ` Giulio Benetti [this message]
2021-02-19 11:37 ` Andre Przywara
2021-02-19 15:27 ` Giulio Benetti
2021-02-20 1:57 ` Andre Przywara
2021-02-18 23:26 ` [PATCH 5/5] pwm: sunxi: enable pwm0 support on sun7i Giulio Benetti
2021-02-19 11:21 ` Andre Przywara
2021-02-18 23:28 ` [PATCH 0/5] Add Micronova srl S027_3 board support Giulio Benetti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99c5198e-7c75-c301-e35b-252d55e51e1e@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox