From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: 'Dong Aisheng' <b29396@freescale.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kgene.kim@samsung.com, linux@arm.linux.org.uk, arnd@arndb.de,
naushad@samsung.com, tomasz.figa@gmail.com, joshi@samsung.com,
thomas.ab@samsung.com, vikas.sajjan@samsung.com,
chow.kim@samsung.com, lee.jones@linaro.org,
'Boris BREZILLON' <boris.brezillon@free-electrons.com>
Subject: RE: [PATCH v3] mfd: syscon: Decouple syscon interface from platform devices
Date: Wed, 17 Sep 2014 16:50:50 +0530 [thread overview]
Message-ID: <000401cfd269$922dfc40$b689f4c0$@samsung.com> (raw)
In-Reply-To: <20140917085818.GA10285@shlinux1.ap.freescale.net>
Hi,
On Wednesday, September 17, 2014, Dong Aisheng Wrote,
> >
> > +static struct syscon *of_syscon_register(struct device_node *np) {
> > + struct syscon *syscon;
> > + struct regmap *regmap;
> > + void __iomem *base;
> > +
> > + if (!of_device_is_compatible(np, "syscon"))
> > + return ERR_PTR(-EINVAL);
> > +
> > + syscon = kzalloc(sizeof(*syscon), GFP_KERNEL);
> > + if (!syscon)
> > + return ERR_PTR(-ENOMEM);
> > +
> > + base = of_iomap(np, 0);
> > + if (!base)
> > + return ERR_PTR(-ENOMEM);
> > +
> > + regmap = regmap_init_mmio(NULL, base, &syscon_regmap_config);
>
> Does a NULL device pointer work?
Yes, it is safe, at least we are able to test on Exynos based SoC.
I have tested it with kgene/for-next kernel on Exynos3250.
Also it has been tested on Exynos5250 based Snow board with 3.17-rc5 based
kernel
by Vivek Gautam.
Patch V2 also has been tested by "Borris Brezillon" on AT91 platform.
> I just tested on MX6SX SDB board and it seemed crashed at here in
regmap_init
> function.
>
Can you please provide crash log which can give more information about the
crash?
Thanks,
Pankaj Dubey
> Regards
> Dong Aisheng
>
> > + if (IS_ERR(regmap)) {
> > + pr_err("regmap init failed\n");
> > + return ERR_CAST(regmap);
> > + }
> > +
> > + syscon->regmap = regmap;
> > + syscon->np = np;
> > +
> > + spin_lock(&syscon_list_slock);
> > + list_add_tail(&syscon->list, &syscon_list);
> > + spin_unlock(&syscon_list_slock);
> > +
> > + return syscon;
> > +}
> > +
> > static int syscon_probe(struct platform_device *pdev) {
> > struct device *dev = &pdev->dev;
> > @@ -167,7 +204,6 @@ static struct platform_driver syscon_driver = {
> > .driver = {
> > .name = "syscon",
> > .owner = THIS_MODULE,
> > - .of_match_table = of_syscon_match,
> > },
> > .probe = syscon_probe,
> > .id_table = syscon_ids,
> > --
> > 1.7.9.5
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: pankaj.dubey@samsung.com (Pankaj Dubey)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] mfd: syscon: Decouple syscon interface from platform devices
Date: Wed, 17 Sep 2014 16:50:50 +0530 [thread overview]
Message-ID: <000401cfd269$922dfc40$b689f4c0$@samsung.com> (raw)
In-Reply-To: <20140917085818.GA10285@shlinux1.ap.freescale.net>
Hi,
On Wednesday, September 17, 2014, Dong Aisheng Wrote,
> >
> > +static struct syscon *of_syscon_register(struct device_node *np) {
> > + struct syscon *syscon;
> > + struct regmap *regmap;
> > + void __iomem *base;
> > +
> > + if (!of_device_is_compatible(np, "syscon"))
> > + return ERR_PTR(-EINVAL);
> > +
> > + syscon = kzalloc(sizeof(*syscon), GFP_KERNEL);
> > + if (!syscon)
> > + return ERR_PTR(-ENOMEM);
> > +
> > + base = of_iomap(np, 0);
> > + if (!base)
> > + return ERR_PTR(-ENOMEM);
> > +
> > + regmap = regmap_init_mmio(NULL, base, &syscon_regmap_config);
>
> Does a NULL device pointer work?
Yes, it is safe, at least we are able to test on Exynos based SoC.
I have tested it with kgene/for-next kernel on Exynos3250.
Also it has been tested on Exynos5250 based Snow board with 3.17-rc5 based
kernel
by Vivek Gautam.
Patch V2 also has been tested by "Borris Brezillon" on AT91 platform.
> I just tested on MX6SX SDB board and it seemed crashed at here in
regmap_init
> function.
>
Can you please provide crash log which can give more information about the
crash?
Thanks,
Pankaj Dubey
> Regards
> Dong Aisheng
>
> > + if (IS_ERR(regmap)) {
> > + pr_err("regmap init failed\n");
> > + return ERR_CAST(regmap);
> > + }
> > +
> > + syscon->regmap = regmap;
> > + syscon->np = np;
> > +
> > + spin_lock(&syscon_list_slock);
> > + list_add_tail(&syscon->list, &syscon_list);
> > + spin_unlock(&syscon_list_slock);
> > +
> > + return syscon;
> > +}
> > +
> > static int syscon_probe(struct platform_device *pdev) {
> > struct device *dev = &pdev->dev;
> > @@ -167,7 +204,6 @@ static struct platform_driver syscon_driver = {
> > .driver = {
> > .name = "syscon",
> > .owner = THIS_MODULE,
> > - .of_match_table = of_syscon_match,
> > },
> > .probe = syscon_probe,
> > .id_table = syscon_ids,
> > --
> > 1.7.9.5
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-09-17 11:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 6:31 [PATCH v3] mfd: syscon: Decouple syscon interface from platform devices Pankaj Dubey
2014-09-17 6:31 ` Pankaj Dubey
2014-09-17 8:58 ` Dong Aisheng
2014-09-17 8:58 ` Dong Aisheng
2014-09-17 8:58 ` Dong Aisheng
2014-09-17 11:20 ` Pankaj Dubey [this message]
2014-09-17 11:20 ` Pankaj Dubey
2014-09-18 3:05 ` Dong Aisheng
2014-09-18 3:05 ` Dong Aisheng
2014-09-18 3:05 ` Dong Aisheng
2014-09-18 6:03 ` Pankaj Dubey
2014-09-18 6:03 ` Pankaj Dubey
2014-09-18 6:33 ` Li.Xiubo
2014-09-18 6:33 ` Li.Xiubo at freescale.com
2014-09-18 7:55 ` Dong Aisheng
2014-09-18 7:55 ` Dong Aisheng
2014-09-18 7:55 ` Dong Aisheng
2014-09-18 8:58 ` Li.Xiubo
2014-09-18 8:58 ` Li.Xiubo at freescale.com
2014-09-18 9:40 ` Pankaj Dubey
2014-09-18 9:40 ` Pankaj Dubey
2014-09-18 9:36 ` Pankaj Dubey
2014-09-18 9:36 ` Pankaj Dubey
2014-09-18 10:05 ` Dong Aisheng
2014-09-18 10:05 ` Dong Aisheng
2014-09-18 10:05 ` Dong Aisheng
2014-09-19 3:38 ` Li.Xiubo
2014-09-19 3:38 ` Li.Xiubo at freescale.com
2014-09-19 4:19 ` Dong Aisheng
2014-09-19 4:19 ` Dong Aisheng
2014-09-19 4:19 ` Dong Aisheng
2014-09-19 5:20 ` Li.Xiubo
2014-09-19 5:20 ` Li.Xiubo
2014-09-19 5:20 ` Li.Xiubo at freescale.com
2014-09-19 5:46 ` Dong Aisheng
2014-09-19 5:46 ` Dong Aisheng
2014-09-19 5:46 ` Dong Aisheng
2014-09-19 9:20 ` Pankaj Dubey
2014-09-19 9:20 ` Pankaj Dubey
2014-09-18 7:58 ` Li.Xiubo
2014-09-18 7:58 ` Li.Xiubo at freescale.com
2014-09-17 15:23 ` Arnd Bergmann
2014-09-17 15:23 ` Arnd Bergmann
2014-09-18 3:29 ` Pankaj Dubey
2014-09-18 3:29 ` Pankaj Dubey
2014-09-18 3:07 ` Dong Aisheng
2014-09-18 3:07 ` Dong Aisheng
2014-09-18 3:07 ` Dong Aisheng
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='000401cfd269$922dfc40$b689f4c0$@samsung.com' \
--to=pankaj.dubey@samsung.com \
--cc=arnd@arndb.de \
--cc=b29396@freescale.com \
--cc=boris.brezillon@free-electrons.com \
--cc=chow.kim@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=naushad@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=vikas.sajjan@samsung.com \
/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.