From: Arnd Bergmann <arnd@arndb.de>
To: Joachim Eastwood <manabian@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Pankaj Dubey" <pankaj.dubey@samsung.com>,
"Douglas Anderson" <dianders@chromium.org>,
kgene.kim@samsung.com,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Heiko Stübner" <heiko@sntech.de>,
naushad@samsung.com, Li.Xiubo@freescale.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Tomasz Figa" <tomasz.figa@gmail.com>,
linux-samsung-soc@vger.kernel.org, thomas.ab@samsung.com,
vikas.sajjan@samsung.com, chow.kim@samsung.com,
"Lee Jones" <lee.jones@linaro.org>,
"sunil joshi" <joshi@samsung.com>,
b29396@freescale.com
Subject: Re: [PATCH v5] mfd: syscon: Decouple syscon interface from platform devices
Date: Fri, 26 Sep 2014 11:14:30 +0200 [thread overview]
Message-ID: <3291391.H71MjevFsA@wuerfel> (raw)
In-Reply-To: <CAGhQ9VwAe7d7fX1Lw22ocxDSXjOZbvXdmG1u6_d5v7ptmYMYeg@mail.gmail.com>
On Friday 26 September 2014 09:48:24 Joachim Eastwood wrote:
> On 26 September 2014 09:16, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 26 September 2014 07:34:12 Joachim Eastwood wrote:
> >> I am working on Cortex-M4 no-MMU platform that isn't upstream yet, btw.
> >>
> >
> > Sorry for drifting off-topic, but this is very interesting to me. Can you
> > say which one you are working on and what your timeline is for submitting
> > it upstream?
>
> It's NXP LPC18xx/43xx which is Cortex-M3/M4.
>
> 3.19 or 3.20 might be target.
Ah, very nice!
> Right now everything is in a github repository here:
> https://github.com/manabian/linux-lpc
>
> Most stuff are working now and I am in the process of clean it up and
> adding documentation.
Ok, looks like you are making good progress. I noticed three high-level
issues that you may want to address:
- the watchdog driver should use the generic watchdog framework rather
than registering a misc device.
- the ehci glue can probably go away if you make very small changes
to the generic ehci platform driver
- I don't like the way that the stmmac glue drivers are added, I thought
we had fixed this before but I think I need to dig up old emails.
The driver should really be a loadable module that hooks calls into
the common code rather than being linked into one module.
I also have a plan for doing multiplatform builds of nommu kernels,
for build testing mostly, I wouldn't expect you to run that configuration.
No need for you to address that yourself though, we'll get there.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] mfd: syscon: Decouple syscon interface from platform devices
Date: Fri, 26 Sep 2014 11:14:30 +0200 [thread overview]
Message-ID: <3291391.H71MjevFsA@wuerfel> (raw)
In-Reply-To: <CAGhQ9VwAe7d7fX1Lw22ocxDSXjOZbvXdmG1u6_d5v7ptmYMYeg@mail.gmail.com>
On Friday 26 September 2014 09:48:24 Joachim Eastwood wrote:
> On 26 September 2014 09:16, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 26 September 2014 07:34:12 Joachim Eastwood wrote:
> >> I am working on Cortex-M4 no-MMU platform that isn't upstream yet, btw.
> >>
> >
> > Sorry for drifting off-topic, but this is very interesting to me. Can you
> > say which one you are working on and what your timeline is for submitting
> > it upstream?
>
> It's NXP LPC18xx/43xx which is Cortex-M3/M4.
>
> 3.19 or 3.20 might be target.
Ah, very nice!
> Right now everything is in a github repository here:
> https://github.com/manabian/linux-lpc
>
> Most stuff are working now and I am in the process of clean it up and
> adding documentation.
Ok, looks like you are making good progress. I noticed three high-level
issues that you may want to address:
- the watchdog driver should use the generic watchdog framework rather
than registering a misc device.
- the ehci glue can probably go away if you make very small changes
to the generic ehci platform driver
- I don't like the way that the stmmac glue drivers are added, I thought
we had fixed this before but I think I need to dig up old emails.
The driver should really be a loadable module that hooks calls into
the common code rather than being linked into one module.
I also have a plan for doing multiplatform builds of nommu kernels,
for build testing mostly, I wouldn't expect you to run that configuration.
No need for you to address that yourself though, we'll get there.
Arnd
next prev parent reply other threads:[~2014-09-26 9:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 4:40 [PATCH v5] mfd: syscon: Decouple syscon interface from platform devices Pankaj Dubey
2014-09-22 4:40 ` Pankaj Dubey
2014-09-22 9:19 ` Dong Aisheng
2014-09-22 9:19 ` Dong Aisheng
2014-09-22 9:19 ` Dong Aisheng
2014-09-23 10:29 ` Pankaj Dubey
2014-09-23 10:29 ` Pankaj Dubey
2014-09-25 12:42 ` Arnd Bergmann
2014-09-25 12:42 ` Arnd Bergmann
2014-09-26 5:28 ` Pankaj Dubey
2014-09-26 5:28 ` Pankaj Dubey
2014-09-26 7:14 ` Arnd Bergmann
2014-09-26 7:14 ` Arnd Bergmann
2014-09-22 9:55 ` Li.Xiubo
2014-09-22 9:55 ` Li.Xiubo
2014-09-22 9:55 ` Li.Xiubo at freescale.com
2014-09-23 18:12 ` Joachim Eastwood
2014-09-23 18:12 ` Joachim Eastwood
2014-09-24 18:35 ` Heiko Stübner
2014-09-24 18:35 ` Heiko Stübner
2014-09-25 12:21 ` Heiko Stübner
2014-09-25 12:21 ` Heiko Stübner
2014-09-26 4:56 ` Pankaj Dubey
2014-09-26 4:56 ` Pankaj Dubey
2014-09-26 5:34 ` Joachim Eastwood
2014-09-26 5:34 ` Joachim Eastwood
2014-09-26 7:16 ` Arnd Bergmann
2014-09-26 7:16 ` Arnd Bergmann
2014-09-26 7:48 ` Joachim Eastwood
2014-09-26 7:48 ` Joachim Eastwood
2014-09-26 9:14 ` Arnd Bergmann [this message]
2014-09-26 9:14 ` Arnd Bergmann
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=3291391.H71MjevFsA@wuerfel \
--to=arnd@arndb.de \
--cc=Li.Xiubo@freescale.com \
--cc=b29396@freescale.com \
--cc=chow.kim@samsung.com \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--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=manabian@gmail.com \
--cc=naushad@samsung.com \
--cc=pankaj.dubey@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.