Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Olof Johansson' <olof@lixom.net>,
	'Doug Anderson' <dianders@chromium.org>
Cc: 'Sachin Kamat' <sachin.kamat@samsung.com>,
	'linux-samsung-soc' <linux-samsung-soc@vger.kernel.org>,
	'Sachin Kamat' <spk.linux@gmail.com>,
	'Javier Martinez Canillas' <javier.martinez@collabora.co.uk>,
	'Kevin Hilman' <khilman@linaro.org>
Subject: RE: [PATCH 1/1] ARM: exynos_defconfig: Update exynos_defconfig
Date: Tue, 15 Jul 2014 10:28:41 +0900	[thread overview]
Message-ID: <020e01cf9fcc$1c91dda0$55b598e0$@samsung.com> (raw)
In-Reply-To: <CAOesGMgyZN8TApVO0Svi65qLBzV6jnzGNg9UP1U+hRw=uXg1Bw@mail.gmail.com>

Olof Johansson wrote:
> 
> On Mon, Jul 14, 2014 at 9:47 AM, Doug Anderson <dianders@chromium.org> wrote:
> > Sachin,
> >
> > On Wed, Jul 9, 2014 at 3:22 AM, Sachin Kamat <sachin.kamat@samsung.com> wrote:
> >> Removed outdated configs. Enabled most of the configs used on latest
> >> Exynos based platforms. This will provide a reference for users trying
> >> to verify and test various features on Exynos based platforms and also
> >> help in detecting breakages by widening the build coverage.
> >>
> >> Signed-off-by: Sachin Kamat <sachin.kamat@samsung.com>
> >> ---
> >>  arch/arm/configs/exynos_defconfig |   56 +++++++++++++++++++++++++++++++------
> >>  1 file changed, 48 insertions(+), 8 deletions(-)
> >
> > How about "CONFIG_CPU_FREQ=y" + related configs?  I'm pretty sure that
> > CPU_FREQ works on exynos5250-snow and the config didn't hurt last time
> > I tried on exynos5420/5800.
> >
> > Once Javier's changes land we'll need to add max77802 in here, but
> > it's fine to leave it out until then.
> >
> > I'd also wonder about CONFIG_DRM eventually being set for graphics,
> > but I'll admit to very little knowledge there.  That seems like it
> > could be in a followup patch.
> >
> > I would strongly suggest PREMPT_VOLUNTARY=y for now (again in a
> > separate patch).  With your config and 'slub_debug=FZPUA' I continue
> > to get constant errors reported.  These errors are not your fault
> > (they also show up on tegra boards).  I've already reported this and
> > it's pretty much gone nowhere.
> >
> > Another suggestion is to enable the WiFi that's on ARM Chromebooks:
> >   CONFIG_MWIFIEX=m
> >   CONFIG_MWIFIEX_SDIO=m
> >
> > ...and that probably means some WiFi configs.  I'm not an expert, but
> > possibly these.  The first of these appears to be needed to keep shill
> > (present in the default ChromeOS rootfilesystem) from crashing wildly:
> >   CONFIG_CFG80211=m
> >   CONFIG_CFG80211_WEXT=y
> >   CONFIG_MAC80211=m
> >
> >
> > Possibly you should be enabling the battery eventually since
> > Chromebooks have these too:
> >   CONFIG_BATTERY_SBS=m
> >
> > You're enabling the adc, but not what's hooked up to it:
> >   CONFIG_SENSORS_NTC_THERMISTOR=m
> >
> > The eMMC that ships on Chromebooks has more than 8 partitions, so you
> > probably should have this:
> >   CONFIG_MMC_BLOCK_MINORS=16
> >
> > There's a light sensor on most ARM Chromebooks:
> >   CONFIG_SENSORS_ISL29018=m
> >
> >
> >
> > All of the above could be in followup patches, so:
> >
> > Tested-by: Doug Anderson <dianders@chromium.org>
> > Reviewed-by: Doug Anderson <dianders@chromium.org>
> 
> Gave this a go on my board farm as well, it looks better than before

Sounds good. I will take into fixes for 3.16 and will send out to arm-soc soon.

> for sure. Boot logs are at:
> http://arm-soc.lixom.net/bootlogs/misc/v3.16-rc4-360-g1501776
> 
> There are still some issues to resolve but this is an improvement so
> let's pick it up and fix with new patches on top.
> 
Sure.

Thanks,
Kukjin

> Some of the new warnings are:
> 
> [WARN] [    0.785066] usb@12000000 supply vdd33 not found, using dummy regulator
> [WARN] [    0.791071] usb@12000000 supply vdd10 not found, using dummy regulator
> [WARN] [    0.998658] usb@12400000 supply vdd33 not found, using dummy regulator
> [WARN] [    1.004049] usb@12400000 supply vdd10 not found, using dummy regulator
> [WARN] [    1.673277] 10060000.tmu supply vtmu not found, using dummy regulator
> [WARN] [    1.685873] 10064000.tmu supply vtmu not found, using dummy regulator
> [WARN] [    1.706262] 10068000.tmu supply vtmu not found, using dummy regulator
> [WARN] [    1.720076] 1006c000.tmu supply vtmu not found, using dummy regulator
> [WARN] [    1.733957] 100a0000.tmu supply vtmu not found, using dummy regulator
> 
> On snow there is also the below. The L2C might be fixed on -next, it
> needs to be checked for.
> 
> [ERR] [    0.000000] L2C: failed to init: -19
> [ERR] [    2.118115] cros-ec-i2c-tunnel cros-ec-i2c-tunnel.2: Couldn't
> read remote-bus property
> [ERR] [    2.726727] max98095 7-0011: ASoC: mux Linein Mux has no paths
> [ERR] [    2.731092] max98095 7-0011: ASoC: mux External MIC has no paths
> 
> [WARN] [    2.125843] cros-ec-i2c-tunnel: probe of
> cros-ec-i2c-tunnel.2 failed with error -22
> [WARN] [    2.138322] tps65090 104-0048: No cache defaults, reading back from HW
> [WARN] [    2.296011] tps65090-charger tps65090-charger: Unable to get
> charger irq = -22
> [WARN] [    2.313705] tps65090-charger: probe of tps65090-charger
> failed with error -22
> 
> 
> 
> -Olof

  parent reply	other threads:[~2014-07-15  1:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 10:22 [PATCH 1/1] ARM: exynos_defconfig: Update exynos_defconfig Sachin Kamat
2014-07-14  1:48 ` Kukjin Kim
2014-07-14 11:43 ` Arun Kumar K
2014-07-14 16:47 ` Doug Anderson
2014-07-14 18:50   ` Olof Johansson
2014-07-14 19:24     ` Doug Anderson
2014-07-17 21:30       ` Javier Martinez Canillas
2014-07-15  1:28     ` Kukjin Kim [this message]
2014-07-15  1:46       ` Olof Johansson
2014-07-15  4:31     ` Sachin Kamat
2014-07-15  8:25       ` Naveen Krishna Ch
2014-07-15 10:47       ` Vivek Gautam
2014-07-15  4:18   ` Sachin Kamat

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='020e01cf9fcc$1c91dda0$55b598e0$@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=dianders@chromium.org \
    --cc=javier.martinez@collabora.co.uk \
    --cc=khilman@linaro.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sachin.kamat@samsung.com \
    --cc=spk.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox