From: Fabio Estevam <festevam@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: DTS: imx53: Add support for imx53 HSC/DDC boards from K+P
Date: Wed, 23 May 2018 10:56:13 -0300 [thread overview]
Message-ID: <CAOMZO5DoLwEmQz5BQHDLk8sBq7mDH_UxBjRA0RGKb+PunMYu-Q@mail.gmail.com> (raw)
In-Reply-To: <20180519140202.3449e3c1@jawa>
Hi Lukasz,
On Sat, May 19, 2018 at 9:02 AM, Lukasz Majewski <lukma@denx.de> wrote:
> After removing imx53-kp-ddc and imx53-kp-common iomux subnodes I do see
> following errors in the dmesg (v4.17-rc5):
>
> imx53-pinctrl 53fa8000.iomuxc: function 'iomuxc' not supported
> imx53-pinctrl 53fa8000.iomuxc: invalid function iomuxc in map table
Could you please investigate this error?
I have just tried the following change on a imx53-qsb:
http://code.bulix.org/ik01yu-339697
and it works as expected:
# dmesg | grep iomux
[ 0.100046] imx53-pinctrl 53fa8000.iomuxc: initialized IMX pinctrl driver
WARNING: multiple messages have this Message-ID (diff)
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: DTS: imx53: Add support for imx53 HSC/DDC boards from K+P
Date: Wed, 23 May 2018 10:56:13 -0300 [thread overview]
Message-ID: <CAOMZO5DoLwEmQz5BQHDLk8sBq7mDH_UxBjRA0RGKb+PunMYu-Q@mail.gmail.com> (raw)
In-Reply-To: <20180519140202.3449e3c1@jawa>
Hi Lukasz,
On Sat, May 19, 2018 at 9:02 AM, Lukasz Majewski <lukma@denx.de> wrote:
> After removing imx53-kp-ddc and imx53-kp-common iomux subnodes I do see
> following errors in the dmesg (v4.17-rc5):
>
> imx53-pinctrl 53fa8000.iomuxc: function 'iomuxc' not supported
> imx53-pinctrl 53fa8000.iomuxc: invalid function iomuxc in map table
Could you please investigate this error?
I have just tried the following change on a imx53-qsb:
http://code.bulix.org/ik01yu-339697
and it works as expected:
# dmesg | grep iomux
[ 0.100046] imx53-pinctrl 53fa8000.iomuxc: initialized IMX pinctrl driver
next prev parent reply other threads:[~2018-05-23 13:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:34 [PATCH] ARM: DTS: imx53: Add support for imx53 HSC/DDC boards from K+P Lukasz Majewski
2018-05-09 15:34 ` Lukasz Majewski
2018-05-10 1:10 ` Fabio Estevam
2018-05-10 1:10 ` Fabio Estevam
2018-05-19 12:02 ` Lukasz Majewski
2018-05-19 12:02 ` Lukasz Majewski
2018-05-23 13:56 ` Fabio Estevam [this message]
2018-05-23 13:56 ` Fabio Estevam
2018-05-23 22:18 ` Lukasz Majewski
2018-05-23 22:18 ` Lukasz Majewski
2018-05-29 13:58 ` Lukasz Majewski
2018-05-29 13:58 ` Lukasz Majewski
2018-05-29 14:11 ` Fabio Estevam
2018-05-29 14:11 ` Fabio Estevam
2018-05-29 15:09 ` Lukasz Majewski
2018-05-29 15:09 ` Lukasz Majewski
2018-05-10 1:45 ` Fabio Estevam
2018-05-10 1:45 ` Fabio Estevam
2018-05-19 12:15 ` [PATCH v2] " Lukasz Majewski
2018-05-19 12:15 ` Lukasz Majewski
2018-05-29 15:12 ` Fabio Estevam
2018-05-29 15:12 ` Fabio Estevam
2018-06-07 8:51 ` Lukasz Majewski
2018-06-07 8:51 ` Lukasz Majewski
2018-06-11 5:13 ` Shawn Guo
2018-06-11 5:13 ` Shawn Guo
2018-06-12 11:28 ` Lukasz Majewski
2018-06-12 11:28 ` Lukasz Majewski
2018-06-12 13:32 ` [PATCH v3] " Lukasz Majewski
2018-06-12 13:32 ` Lukasz Majewski
2018-06-17 6:57 ` Shawn Guo
2018-06-17 6:57 ` Shawn Guo
2018-06-17 7:31 ` Lukasz Majewski
2018-06-17 7:31 ` Lukasz Majewski
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=CAOMZO5DoLwEmQz5BQHDLk8sBq7mDH_UxBjRA0RGKb+PunMYu-Q@mail.gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukma@denx.de \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.