From: Mauro Ziliani <mauro@faresoftware.it>
To: meta-freescale@lists.yoctoproject.org
Subject: Understanding pads setup
Date: Sun, 12 Mar 2023 19:50:09 +0100 [thread overview]
Message-ID: <a1342fb2-302e-93d7-345e-4aa5cd2c1d32@faresoftware.it> (raw)
Hi all
I'm working on and mx51evk babbage board.
I have a lvds display connected ti disp1 pads.
I need to define DI1_DISP_CLK for pad J18 of the BGA (the chip is 19x19mm)
I know the pad definition is made by 5+1 values
<mux_reg conf_reg input_reg mux_mode input_val CONFIG>
I don't find MX51_PAD_DI1_DISP_CLK__DI1_DISP_CLK or similar in
imx51-pinfunc.h
I find MX51_PAD_DI2_DISP_CLK__DI2_DISP_CLK defined with this values.
#define MX51_PAD_DI2_DISP_CLK__DI2_DISP_CLK 0x34c 0x754 0x000 0x0 0x0
But I don't know how to use the 5 values.
Where I can find some example o detailed info about?
MZ
next reply other threads:[~2023-03-12 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 18:50 Mauro Ziliani [this message]
2023-03-13 7:54 ` Understanding pads setup 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
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=a1342fb2-302e-93d7-345e-4aa5cd2c1d32@faresoftware.it \
--to=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).