From: l.majewski@samsung.com (Lukasz Majewski)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 7/7] Samsung SoC for v3.14
Date: Mon, 23 Dec 2013 10:36:18 +0100 [thread overview]
Message-ID: <20131223103618.5815379e@amdc2363> (raw)
In-Reply-To: <1566886.jecinlyiQ0@flatron>
Hi Tomasz,
> Hi Olof,
>
> On Sunday 22 of December 2013 14:11:41 Olof Johansson wrote:
> > On Mon, Dec 16, 2013 at 05:23:01AM +0900, Kukjin Kim wrote:
> > > The following changes since commit
> > > 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
> > >
> > > Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
> > >
> > > are available in the git repository at:
> > >
> >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > > tags/samsung-soc
> > >
> > > for you to fetch changes up to
> > > 538cfbb4c40ab59688236484138133b8e3e89220:
> > >
> > > ARM: dts: Add initial support for Arndale Octa board (2013-12-16
> > > 05:05:43 +0900)
> >
> > Hi,
> >
> > I'm not going to pull this.
> >
> > I've asked you for about 6 months now (ever since Arnd went on
> > leave) to please finish his multiplatform work for Exynos. Nothing
> > has happened.
> >
> > I'm not going to merge any more platform or SoC enablement code
> > for Samsung platforms until Exynos has been converted over to
> > multiplatform. Sorry.
>
> Well, it's hard to disagree with you on this. Keeping adding new
> things constantly definitely does not make us closer to multiplatform
> support, as it only increases codebase of code that needs to be
> cleaned up and made multiplatform aware.
>
> However it's not that we're not doing anything towards mutliplatform
> support. We're slowly getting there. A bit too slowly, but I'm afraid
> this is due to the fact that we have definitely too little manpower
> working on mainline support of Samsung SoCs.
>
> As for good news, I already have a series cleaning up PM/sleep support
> and making it multiplatform friendly and I'm going to post it
> tomorrow. The bad news is that it depends on other series and I'm not
> sure if we can get it merged in this release. I'll try to do whatever
> possible to merge things as soon as possible, though.
>
> From smaller things, we still need to sort out Exynos cpufreq driver
> that has dependencies on headers in plat-samsung/ and mach-exynos/.
> Unfortunately I don't have so much time to work on all the things at
> the same time, so I hope that someone else could pick this task up.
> Marek, Lukasz, what do you think?
Regarding the cpufreq for Exynos, we do need to clean things up.
It shall be possible to reuse generic cpufreq-cpu0.c and
arm_big_little.c code instead of several copy pasted
exynos[4|5]xxx-cpufreq.c ones.
This change will require some "virtual" clocks implementation for atomic
clocks dividers change.
I've already committed myself to fix this code. When all goes smooth, I
shall deliver some RFC code after new year.
>
> Best regards,
> Tomasz
>
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2013-12-23 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 20:23 [GIT PULL 7/7] Samsung SoC for v3.14 Kukjin Kim
2013-12-22 22:11 ` Olof Johansson
2013-12-22 22:39 ` Tomasz Figa
2013-12-23 9:36 ` Lukasz Majewski [this message]
2013-12-23 21:38 ` Olof Johansson
2013-12-24 1:35 ` Kukjin Kim
2013-12-24 3:09 ` Olof Johansson
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=20131223103618.5815379e@amdc2363 \
--to=l.majewski@samsung.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 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).