All of lore.kernel.org
 help / color / mirror / Atom feed
From: aisheng.dong@freescale.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: Pinctrl crash on latest linux-next/master
Date: Mon, 16 Apr 2012 22:05:44 +0800	[thread overview]
Message-ID: <20120416140543.GC17173@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <CACRpkdb9JOKK=XY0t3GcrOCxyfefi5nw08S4yv=bXREemOM10w@mail.gmail.com>

On Mon, Apr 16, 2012 at 02:50:47PM +0200, Linus Walleij wrote:
> On Mon, Apr 16, 2012 at 12:53 PM, Viresh Kumar <viresh.kumar@st.com> wrote:
> 
> > I don't know if the issue is in my patches or something else, but i was
> > able to boot it earlier. Till my V3 for pinctrl. And nothing much changed
> > since then, i just rebased on latest kernel.
> 
> Hm I haven't tested the pinctrl tree on v3.4-rc3 yet.
> 
Your for-next tree is ok since i'm working on it for pinctrl-imx driver. :-)
It seems it's based on v3.4-rc2.

Hi Viresh,
Some info for your reference:

You may want to check if you call platform_set_drvdata after pinctrl_register
like:
ipmx->pctl = pinctrl_register(&imx_pmx_desc, &pdev->dev, ipmx);
...
platform_set_drvdata(pdev, ipmx);

If that, you may need to change to:
platform_set_drvdata(pdev, ipmx);
..
ipmx->pctl = pinctrl_register(&imx_pmx_desc, &pdev->dev, ipmx);

Because during the registration, the get_group_count will be called which
may reply on platform_set_drvdata(pdev, ipmx);

Regards
Dong Aisheng

> Did you git bisect to figure out which patch broke it?
> 
> Yours,
> Linus Walleij
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  parent reply	other threads:[~2012-04-16 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 10:53 Pinctrl crash on latest linux-next/master Viresh Kumar
2012-04-16 12:50 ` Linus Walleij
2012-04-16 13:44   ` viresh kumar
2012-04-16 14:05   ` Dong Aisheng [this message]
2012-04-17  8:29     ` Viresh Kumar

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=20120416140543.GC17173@shlinux2.ap.freescale.net \
    --to=aisheng.dong@freescale.com \
    --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 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.