linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] ARM: dts: imx6q-icore-rqs: Add Engicam IMX6 Q7 initial support
Date: Wed, 23 Dec 2015 10:27:34 +0800	[thread overview]
Message-ID: <20151223022707.GG26290@tiger> (raw)
In-Reply-To: <20151216181159.GC20121@panicking>

On Wed, Dec 16, 2015 at 07:12:05PM +0100, Michael Trimarchi wrote:
> > > > +	imx6qdl-icore-rqs {
> > > > +
> > > 
> > > With commit 5fcdf6a7ed95 (pinctrl: imx: Allow parsing DT without function
> > > nodes) in place, we can now save this container.
> > > 
> 
> If I save this I can not register usb. Group is not found
> 
> [    2.768476] imx6q-pinctrl 20e0000.iomuxc: unable to find group for node usdhc1grp-1
> [    2.768844] imx6q-pinctrl 20e0000.iomuxc: unable to find group for node usdhc1grp-1
> [    2.768932] sdhci-esdhc-imx: probe of 2190000.usdhc failed with error -22
> [    2.768994] imx6q-pinctrl 20e0000.iomuxc: unable to find group for node usdhc3grp-2
> [    2.769240] imx6q-pinctrl 20e0000.iomuxc: unable to find group for node usdhc3grp-2
> [    2.769322] sdhci-esdhc-imx: probe of 2198000.usdhc failed with error -22
> [    2.769381] imx6q-pinctrl 20e0000.iomuxc: unable to find group for node usdhc4grp-1
> [    2.769621] imx6q-pinctrl 20e0000.iomuxc: unable to find group for node usdhc4grp-1
> [    2.769701] sdhci-esdhc-imx: probe of 219c000.usdhc failed with error -22

Sorry.  I just found that to get this work on imx6q board we need to
clean up the ipu2/ipu2grp-1 group.  I just send a patch doing that with
you on copy.  Let me know if it works for you.

Shawn

  parent reply	other threads:[~2015-12-23  2:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-15 10:54 [PATCH] ARM: dts: imx6q-icore-rqs: Add Engicam IMX6 Q7 initial support Michael Trimarchi
2015-11-16  9:19 ` Lucas Stach
2015-11-16 11:29   ` Michael Trimarchi
2015-11-16 11:38     ` Lucas Stach
2015-11-16 11:41       ` Michael Trimarchi
2015-11-16 11:51         ` Lucas Stach
2015-11-16 11:54           ` Michael Trimarchi
2015-11-16 17:23             ` [PATCH V2] " Michael Trimarchi
2015-11-16 22:02               ` Michael Trimarchi
2015-11-17  9:31               ` Lucas Stach
2015-11-18 15:10                 ` [PATCH V3] " Michael Trimarchi
2015-11-25 18:14                   ` Michael Trimarchi
2015-12-02  2:09                     ` Shawn Guo
2015-12-02  9:15                       ` Michael Trimarchi
2015-12-11  8:36                   ` Shawn Guo
2015-12-14  8:45                     ` Michael Trimarchi
2015-12-16 18:12                       ` Michael Trimarchi
2015-12-21  6:12                         ` Shawn Guo
2015-12-23  2:27                         ` Shawn Guo [this message]
2015-12-23  9:18                           ` Michael Trimarchi
2015-12-24  9:06                           ` [PATCH V4] " Michael Trimarchi
2015-12-24  9:13                             ` Michael Trimarchi
2015-12-24  9:24                           ` [PATCH V5] " Michael Trimarchi
2016-01-12 17:37                             ` Michael Trimarchi
2016-01-28  2:04                             ` Shawn Guo
2016-01-28  2:12                               ` Michael Trimarchi
2016-01-29  8:01                               ` [PATCH V6] " Michael Trimarchi
2016-02-01 11:07                                 ` Shawn Guo
2015-11-24  9:19       ` [PATCH] " Shawn Guo
2015-11-24  9:31         ` Lucas Stach

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=20151223022707.GG26290@tiger \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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).