From: Fabio Estevam <festevam@gmail.com>
To: Mauro Ziliani <mauro@faresoftware.it>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Understanding pads setup
Date: Wed, 29 Mar 2023 00:13:54 -0300 [thread overview]
Message-ID: <CAOMZO5DbCVxS0JV5inx-5Qbqu=iES=rQxGrnhMRMZS9bQSMF4A@mail.gmail.com> (raw)
In-Reply-To: <7d15c799-df3a-c94c-170c-61b2a0abc551@faresoftware.it>
Hi Mauro,
On Tue, Mar 28, 2023 at 6:51 AM Mauro Ziliani <mauro@faresoftware.it> wrote:
>
> Hi Fabio.
>
> In the schematic of the board, the pin J18 is connected to lvds transceiver as DI1_DISP_CLK.
DI1_DISP_CLK is also used on the imx51-evk.
I don't understand why you want to include DI1_DISP_CLK into imx51-pinfunc.h.
The i.MX51 Reference Manual states that the DI1_DISP_CLK has no mux
option. It can only work as DI1_DISP_CLK functionality, so you don't
need to include it in imx51-pinfunc.h.
prev parent reply other threads:[~2023-03-29 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 18:50 Understanding pads setup Mauro Ziliani
2023-03-13 7:54 ` Marco Cavallini
2023-03-13 16:06 ` [meta-freescale] " Mauro Ziliani
2023-03-14 0:39 ` Fabio Estevam
2023-03-28 9:50 ` Mauro Ziliani
2023-03-29 3:13 ` Fabio Estevam [this message]
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='CAOMZO5DbCVxS0JV5inx-5Qbqu=iES=rQxGrnhMRMZS9bQSMF4A@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=mauro@faresoftware.it \
--cc=meta-freescale@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).