From: Jagan Teki <jagan@amarulasolutions.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Jagan Teki <jagannadh.teki@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Matteo Lisi <matteo.lisi@engicam.com>,
Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH v3 2/3] ARM: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual initial support
Date: Sat, 10 Sep 2016 03:33:41 +0530 [thread overview]
Message-ID: <CAMty3ZC+49D7aALOKcsjoiqptQwrrtHGMAGCtcPn51QDsksSSQ@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5BPhY14S4G541MTpsCW64SsCiNcsksJarBCWqGOnaPf3A@mail.gmail.com>
On Sat, Sep 10, 2016 at 3:29 AM, Fabio Estevam <festevam@gmail.com> wrote:
> On Fri, Sep 9, 2016 at 6:45 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>> +&iomuxc {
>> + pinctrl_flexcan1: flexcan1grp {
>> + fsl,pins = <
>> + MX6QDL_PAD_KEY_ROW2__FLEXCAN1_RX 0x1b020
>> + MX6QDL_PAD_KEY_COL2__FLEXCAN1_TX 0x1b020
>
> In the previous version you had "0x80000000", which means: use the pad
> value that comes from the bootloader.
>
> Does your bootloader configure the CAN pins? If not, then it should be
> 1b0b0, which is the POR value of register
> IOMUXC_SW_PAD_CTL_PAD_KEY_ROW2.
>
> To confirm, you can do this in your bootloader:
>
> => md.l 20E05DC 1
> 020e05dc: 0001b0b0
>
> and see if returns 1b0b0 or 1b020.
Yeah, I got 1b0b0
U-Boot > md.l 20E05DC 1
020e05dc: 0001b0b0
thanks!
--
Jagan Teki
Free Software Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
next prev parent reply other threads:[~2016-09-09 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 21:45 [PATCH v3 1/3] of: Add vendor prefix for Engicam s.r.l company Jagan Teki
2016-09-09 21:45 ` [PATCH v3 2/3] ARM: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual initial support Jagan Teki
[not found] ` <1473457525-27768-2-git-send-email-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2016-09-09 21:59 ` Fabio Estevam
2016-09-09 22:03 ` Jagan Teki [this message]
2016-09-09 22:14 ` Jagan Teki
[not found] ` <CAMty3ZAM-sZ0aZU0Z+8WhDcepx8KM96xUbn+n3UcDSjFTafC-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-09 22:19 ` Fabio Estevam
[not found] ` <CAOMZO5AuZ5DqqKngLw67_-3PdoYx5pMNmm1ZHwRd79rYPJY-+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-09 22:19 ` Fabio Estevam
[not found] ` <CAOMZO5D2WNBh6fy8iFYasSZnovfBJRxzBt55ceaPqwCn3zvepg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-09 22:21 ` Jagan Teki
2016-09-09 22:25 ` Fabio Estevam
2016-09-09 22:30 ` Jagan Teki
2016-09-09 21:45 ` [PATCH v3 3/3] ARM: dts: imx6q: Add Engicam i.CoreM6 DualLite/Solo " Jagan Teki
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=CAMty3ZC+49D7aALOKcsjoiqptQwrrtHGMAGCtcPn51QDsksSSQ@mail.gmail.com \
--to=jagan@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=jagannadh.teki@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matteo.lisi@engicam.com \
--cc=michael@amarulasolutions.com \
--cc=shawnguo@kernel.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 NNTP newsgroup(s).