diff mbox

[1/1] ARM: exynos_defconfig: Update exynos_defconfig

Message ID 1404901353-14806-1-git-send-email-sachin.kamat@samsung.com (mailing list archive)
State New, archived
Headers show

Commit Message

Sachin Kamat July 9, 2014, 10:22 a.m. UTC 
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(-)

Comments

Kim Kukjin July 14, 2014, 1:48 a.m. UTC | #1 
Sachin Kamat wrote:
> 
+ Some guys who has updated DT files for exynos SoCs.

> 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.
> 
Please test your boards with this update then anything, please let me know.

Thanks,
Kukjin


> Signed-off-by: Sachin Kamat <sachin.kamat@samsung.com>
> ---
>  arch/arm/configs/exynos_defconfig |   56 +++++++++++++++++++++++++++++++------
>  1 file changed, 48 insertions(+), 8 deletions(-)
> 
> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
> index e07a227ec0db..fc7d1683bf67 100644
> --- a/arch/arm/configs/exynos_defconfig
> +++ b/arch/arm/configs/exynos_defconfig
> @@ -8,15 +8,17 @@ CONFIG_MODULE_UNLOAD=y
>  # CONFIG_BLK_DEV_BSG is not set
>  CONFIG_PARTITION_ADVANCED=y
>  CONFIG_ARCH_EXYNOS=y
> -CONFIG_S3C_LOWLEVEL_UART_PORT=3
> -CONFIG_S3C24XX_PWM=y
> -CONFIG_ARCH_EXYNOS5=y
> -CONFIG_MACH_EXYNOS4_DT=y
> +CONFIG_ARCH_EXYNOS3=y
> +CONFIG_EXYNOS5420_MCPM=y
>  CONFIG_SMP=y
> +CONFIG_BIG_LITTLE=y
> +CONFIG_BL_SWITCHER=y
> +CONFIG_BL_SWITCHER_DUMMY_IF=y
>  CONFIG_NR_CPUS=8
>  CONFIG_PREEMPT=y
>  CONFIG_AEABI=y
>  CONFIG_HIGHMEM=y
> +CONFIG_CMA=y
>  CONFIG_ZBOOT_ROM_TEXT=0x0
>  CONFIG_ZBOOT_ROM_BSS=0x0
>  CONFIG_ARM_APPENDED_DTB=y
> @@ -24,6 +26,7 @@ CONFIG_ARM_ATAG_DTB_COMPAT=y
>  CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200
> init=/linuxrc mem=256M"
>  CONFIG_VFP=y
>  CONFIG_NEON=y
> +CONFIG_PM_RUNTIME=y
>  CONFIG_NET=y
>  CONFIG_PACKET=y
>  CONFIG_UNIX=y
> @@ -34,6 +37,8 @@ CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
>  CONFIG_DEVTMPFS=y
>  CONFIG_DEVTMPFS_MOUNT=y
>  CONFIG_PROC_DEVICETREE=y
> +CONFIG_DMA_CMA=y
> +CONFIG_CMA_SIZE_MBYTES=64
>  CONFIG_BLK_DEV_LOOP=y
>  CONFIG_BLK_DEV_CRYPTOLOOP=y
>  CONFIG_BLK_DEV_RAM=y
> @@ -66,11 +71,22 @@ CONFIG_I2C=y
>  CONFIG_I2C_MUX=y
>  CONFIG_I2C_ARB_GPIO_CHALLENGE=y
>  CONFIG_I2C_EXYNOS5=y
> +CONFIG_I2C_CROS_EC_TUNNEL=y
> +CONFIG_SPI=y
> +CONFIG_SPI_S3C64XX=y
>  CONFIG_I2C_S3C2410=y
>  CONFIG_DEBUG_GPIO=y
> +CONFIG_POWER_SUPPLY=y
> +CONFIG_CHARGER_TPS65090=y
>  # CONFIG_HWMON is not set
> +CONFIG_THERMAL=y
> +CONFIG_EXYNOS_THERMAL=y
> +CONFIG_EXYNOS_THERMAL_CORE=y
> +CONFIG_WATCHDOG=y
> +CONFIG_S3C2410_WATCHDOG=y
>  CONFIG_MFD_CROS_EC=y
>  CONFIG_MFD_CROS_EC_I2C=y
> +CONFIG_MFD_CROS_EC_SPI=y
>  CONFIG_MFD_MAX77686=y
>  CONFIG_MFD_MAX8997=y
>  CONFIG_MFD_SEC_CORE=y
> @@ -80,6 +96,7 @@ CONFIG_REGULATOR_FIXED_VOLTAGE=y
>  CONFIG_REGULATOR_GPIO=y
>  CONFIG_REGULATOR_MAX8997=y
>  CONFIG_REGULATOR_MAX77686=y
> +CONFIG_REGULATOR_S2MPA01=y
>  CONFIG_REGULATOR_S2MPS11=y
>  CONFIG_REGULATOR_S5M8767=y
>  CONFIG_REGULATOR_TPS65090=y
> @@ -88,28 +105,50 @@ CONFIG_FB_MODE_HELPERS=y
>  CONFIG_FB_SIMPLE=y
>  CONFIG_EXYNOS_VIDEO=y
>  CONFIG_EXYNOS_MIPI_DSI=y
> -CONFIG_EXYNOS_DP=y
>  CONFIG_FRAMEBUFFER_CONSOLE=y
>  CONFIG_FONTS=y
>  CONFIG_FONT_7x14=y
>  CONFIG_LOGO=y
> +CONFIG_SOUND=y
> +CONFIG_SND=y
> +CONFIG_SND_SOC=y
> +CONFIG_SND_SOC_SAMSUNG=y
> +CONFIG_SND_SOC_SNOW=y
>  CONFIG_USB=y
> +CONFIG_USB_XHCI_HCD=y
>  CONFIG_USB_EHCI_HCD=y
>  CONFIG_USB_EHCI_EXYNOS=y
> +CONFIG_USB_OHCI_HCD=y
> +CONFIG_USB_OHCI_EXYNOS=y
>  CONFIG_USB_STORAGE=y
>  CONFIG_USB_DWC3=y
> -CONFIG_USB_PHY=y
> -CONFIG_SAMSUNG_USB2PHY=y
> -CONFIG_SAMSUNG_USB3PHY=y
> +CONFIG_USB_HSIC_USB3503=y
>  CONFIG_MMC=y
>  CONFIG_MMC_SDHCI=y
>  CONFIG_MMC_SDHCI_S3C=y
> +CONFIG_MMC_SDHCI_S3C_DMA=y
>  CONFIG_MMC_DW=y
>  CONFIG_MMC_DW_IDMAC=y
>  CONFIG_MMC_DW_EXYNOS=y
>  CONFIG_RTC_CLASS=y
> +CONFIG_RTC_DRV_MAX77686=y
> +CONFIG_RTC_DRV_S5M=y
>  CONFIG_RTC_DRV_S3C=y
> +CONFIG_DMADEVICES=y
> +CONFIG_PL330_DMA=y
>  CONFIG_COMMON_CLK_MAX77686=y
> +CONFIG_COMMON_CLK_S2MPS11=y
> +CONFIG_EXYNOS_IOMMU=y
> +CONFIG_IIO=y
> +CONFIG_EXYNOS_ADC=y
> +CONFIG_PWM=y
> +CONFIG_PWM_SAMSUNG=y
> +CONFIG_PHY_EXYNOS5250_SATA=y
> +CONFIG_PHY_SAMSUNG_USB2=y
> +CONFIG_PHY_EXYNOS4210_USB2=y
> +CONFIG_PHY_EXYNOS4X12_USB2=y
> +CONFIG_PHY_EXYNOS5250_USB2=y
> +CONFIG_PHY_EXYNOS5_USBDRD=y
>  CONFIG_EXT2_FS=y
>  CONFIG_EXT3_FS=y
>  CONFIG_EXT4_FS=y
> @@ -123,6 +162,7 @@ CONFIG_NLS_CODEPAGE_437=y
>  CONFIG_NLS_ASCII=y
>  CONFIG_NLS_ISO8859_1=y
>  CONFIG_PRINTK_TIME=y
> +CONFIG_DEBUG_FS=y
>  CONFIG_MAGIC_SYSRQ=y
>  CONFIG_DEBUG_KERNEL=y
>  CONFIG_DETECT_HUNG_TASK=y
> --
> 1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Arun Kumar K July 14, 2014, 11:43 a.m. UTC | #2 
Tested-by: Arun Kumar K <arun.kk@samsung.com>

on Samsung chromebook boards : Snow, pit and pi.

Regards
Arun

On Wed, Jul 9, 2014 at 3:52 PM, 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(-)
>
> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
> index e07a227ec0db..fc7d1683bf67 100644
> --- a/arch/arm/configs/exynos_defconfig
> +++ b/arch/arm/configs/exynos_defconfig
> @@ -8,15 +8,17 @@ CONFIG_MODULE_UNLOAD=y
>  # CONFIG_BLK_DEV_BSG is not set
>  CONFIG_PARTITION_ADVANCED=y
>  CONFIG_ARCH_EXYNOS=y
> -CONFIG_S3C_LOWLEVEL_UART_PORT=3
> -CONFIG_S3C24XX_PWM=y
> -CONFIG_ARCH_EXYNOS5=y
> -CONFIG_MACH_EXYNOS4_DT=y
> +CONFIG_ARCH_EXYNOS3=y
> +CONFIG_EXYNOS5420_MCPM=y
>  CONFIG_SMP=y
> +CONFIG_BIG_LITTLE=y
> +CONFIG_BL_SWITCHER=y
> +CONFIG_BL_SWITCHER_DUMMY_IF=y
>  CONFIG_NR_CPUS=8
>  CONFIG_PREEMPT=y
>  CONFIG_AEABI=y
>  CONFIG_HIGHMEM=y
> +CONFIG_CMA=y
>  CONFIG_ZBOOT_ROM_TEXT=0x0
>  CONFIG_ZBOOT_ROM_BSS=0x0
>  CONFIG_ARM_APPENDED_DTB=y
> @@ -24,6 +26,7 @@ CONFIG_ARM_ATAG_DTB_COMPAT=y
>  CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200 init=/linuxrc mem=256M"
>  CONFIG_VFP=y
>  CONFIG_NEON=y
> +CONFIG_PM_RUNTIME=y
>  CONFIG_NET=y
>  CONFIG_PACKET=y
>  CONFIG_UNIX=y
> @@ -34,6 +37,8 @@ CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
>  CONFIG_DEVTMPFS=y
>  CONFIG_DEVTMPFS_MOUNT=y
>  CONFIG_PROC_DEVICETREE=y
> +CONFIG_DMA_CMA=y
> +CONFIG_CMA_SIZE_MBYTES=64
>  CONFIG_BLK_DEV_LOOP=y
>  CONFIG_BLK_DEV_CRYPTOLOOP=y
>  CONFIG_BLK_DEV_RAM=y
> @@ -66,11 +71,22 @@ CONFIG_I2C=y
>  CONFIG_I2C_MUX=y
>  CONFIG_I2C_ARB_GPIO_CHALLENGE=y
>  CONFIG_I2C_EXYNOS5=y
> +CONFIG_I2C_CROS_EC_TUNNEL=y
> +CONFIG_SPI=y
> +CONFIG_SPI_S3C64XX=y
>  CONFIG_I2C_S3C2410=y
>  CONFIG_DEBUG_GPIO=y
> +CONFIG_POWER_SUPPLY=y
> +CONFIG_CHARGER_TPS65090=y
>  # CONFIG_HWMON is not set
> +CONFIG_THERMAL=y
> +CONFIG_EXYNOS_THERMAL=y
> +CONFIG_EXYNOS_THERMAL_CORE=y
> +CONFIG_WATCHDOG=y
> +CONFIG_S3C2410_WATCHDOG=y
>  CONFIG_MFD_CROS_EC=y
>  CONFIG_MFD_CROS_EC_I2C=y
> +CONFIG_MFD_CROS_EC_SPI=y
>  CONFIG_MFD_MAX77686=y
>  CONFIG_MFD_MAX8997=y
>  CONFIG_MFD_SEC_CORE=y
> @@ -80,6 +96,7 @@ CONFIG_REGULATOR_FIXED_VOLTAGE=y
>  CONFIG_REGULATOR_GPIO=y
>  CONFIG_REGULATOR_MAX8997=y
>  CONFIG_REGULATOR_MAX77686=y
> +CONFIG_REGULATOR_S2MPA01=y
>  CONFIG_REGULATOR_S2MPS11=y
>  CONFIG_REGULATOR_S5M8767=y
>  CONFIG_REGULATOR_TPS65090=y
> @@ -88,28 +105,50 @@ CONFIG_FB_MODE_HELPERS=y
>  CONFIG_FB_SIMPLE=y
>  CONFIG_EXYNOS_VIDEO=y
>  CONFIG_EXYNOS_MIPI_DSI=y
> -CONFIG_EXYNOS_DP=y
>  CONFIG_FRAMEBUFFER_CONSOLE=y
>  CONFIG_FONTS=y
>  CONFIG_FONT_7x14=y
>  CONFIG_LOGO=y
> +CONFIG_SOUND=y
> +CONFIG_SND=y
> +CONFIG_SND_SOC=y
> +CONFIG_SND_SOC_SAMSUNG=y
> +CONFIG_SND_SOC_SNOW=y
>  CONFIG_USB=y
> +CONFIG_USB_XHCI_HCD=y
>  CONFIG_USB_EHCI_HCD=y
>  CONFIG_USB_EHCI_EXYNOS=y
> +CONFIG_USB_OHCI_HCD=y
> +CONFIG_USB_OHCI_EXYNOS=y
>  CONFIG_USB_STORAGE=y
>  CONFIG_USB_DWC3=y
> -CONFIG_USB_PHY=y
> -CONFIG_SAMSUNG_USB2PHY=y
> -CONFIG_SAMSUNG_USB3PHY=y
> +CONFIG_USB_HSIC_USB3503=y
>  CONFIG_MMC=y
>  CONFIG_MMC_SDHCI=y
>  CONFIG_MMC_SDHCI_S3C=y
> +CONFIG_MMC_SDHCI_S3C_DMA=y
>  CONFIG_MMC_DW=y
>  CONFIG_MMC_DW_IDMAC=y
>  CONFIG_MMC_DW_EXYNOS=y
>  CONFIG_RTC_CLASS=y
> +CONFIG_RTC_DRV_MAX77686=y
> +CONFIG_RTC_DRV_S5M=y
>  CONFIG_RTC_DRV_S3C=y
> +CONFIG_DMADEVICES=y
> +CONFIG_PL330_DMA=y
>  CONFIG_COMMON_CLK_MAX77686=y
> +CONFIG_COMMON_CLK_S2MPS11=y
> +CONFIG_EXYNOS_IOMMU=y
> +CONFIG_IIO=y
> +CONFIG_EXYNOS_ADC=y
> +CONFIG_PWM=y
> +CONFIG_PWM_SAMSUNG=y
> +CONFIG_PHY_EXYNOS5250_SATA=y
> +CONFIG_PHY_SAMSUNG_USB2=y
> +CONFIG_PHY_EXYNOS4210_USB2=y
> +CONFIG_PHY_EXYNOS4X12_USB2=y
> +CONFIG_PHY_EXYNOS5250_USB2=y
> +CONFIG_PHY_EXYNOS5_USBDRD=y
>  CONFIG_EXT2_FS=y
>  CONFIG_EXT3_FS=y
>  CONFIG_EXT4_FS=y
> @@ -123,6 +162,7 @@ CONFIG_NLS_CODEPAGE_437=y
>  CONFIG_NLS_ASCII=y
>  CONFIG_NLS_ISO8859_1=y
>  CONFIG_PRINTK_TIME=y
> +CONFIG_DEBUG_FS=y
>  CONFIG_MAGIC_SYSRQ=y
>  CONFIG_DEBUG_KERNEL=y
>  CONFIG_DETECT_HUNG_TASK=y
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Doug Anderson July 14, 2014, 4:47 p.m. UTC | #3 
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>


> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
> index e07a227ec0db..fc7d1683bf67 100644
> --- a/arch/arm/configs/exynos_defconfig
> +++ b/arch/arm/configs/exynos_defconfig
> @@ -8,15 +8,17 @@ CONFIG_MODULE_UNLOAD=y
>  # CONFIG_BLK_DEV_BSG is not set
>  CONFIG_PARTITION_ADVANCED=y
>  CONFIG_ARCH_EXYNOS=y
> -CONFIG_S3C_LOWLEVEL_UART_PORT=3
> -CONFIG_S3C24XX_PWM=y
> -CONFIG_ARCH_EXYNOS5=y
> -CONFIG_MACH_EXYNOS4_DT=y
> +CONFIG_ARCH_EXYNOS3=y
> +CONFIG_EXYNOS5420_MCPM=y
>  CONFIG_SMP=y
> +CONFIG_BIG_LITTLE=y
> +CONFIG_BL_SWITCHER=y
> +CONFIG_BL_SWITCHER_DUMMY_IF=y
>  CONFIG_NR_CPUS=8
>  CONFIG_PREEMPT=y
>  CONFIG_AEABI=y
>  CONFIG_HIGHMEM=y
> +CONFIG_CMA=y
>  CONFIG_ZBOOT_ROM_TEXT=0x0
>  CONFIG_ZBOOT_ROM_BSS=0x0
>  CONFIG_ARM_APPENDED_DTB=y
> @@ -24,6 +26,7 @@ CONFIG_ARM_ATAG_DTB_COMPAT=y
>  CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200 init=/linuxrc mem=256M"
>  CONFIG_VFP=y
>  CONFIG_NEON=y
> +CONFIG_PM_RUNTIME=y
>  CONFIG_NET=y
>  CONFIG_PACKET=y
>  CONFIG_UNIX=y
> @@ -34,6 +37,8 @@ CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
>  CONFIG_DEVTMPFS=y
>  CONFIG_DEVTMPFS_MOUNT=y
>  CONFIG_PROC_DEVICETREE=y
> +CONFIG_DMA_CMA=y
> +CONFIG_CMA_SIZE_MBYTES=64
>  CONFIG_BLK_DEV_LOOP=y
>  CONFIG_BLK_DEV_CRYPTOLOOP=y
>  CONFIG_BLK_DEV_RAM=y
> @@ -66,11 +71,22 @@ CONFIG_I2C=y
>  CONFIG_I2C_MUX=y
>  CONFIG_I2C_ARB_GPIO_CHALLENGE=y
>  CONFIG_I2C_EXYNOS5=y
> +CONFIG_I2C_CROS_EC_TUNNEL=y
> +CONFIG_SPI=y
> +CONFIG_SPI_S3C64XX=y
>  CONFIG_I2C_S3C2410=y
>  CONFIG_DEBUG_GPIO=y
> +CONFIG_POWER_SUPPLY=y
> +CONFIG_CHARGER_TPS65090=y
>  # CONFIG_HWMON is not set
> +CONFIG_THERMAL=y
> +CONFIG_EXYNOS_THERMAL=y
> +CONFIG_EXYNOS_THERMAL_CORE=y
> +CONFIG_WATCHDOG=y
> +CONFIG_S3C2410_WATCHDOG=y
>  CONFIG_MFD_CROS_EC=y
>  CONFIG_MFD_CROS_EC_I2C=y
> +CONFIG_MFD_CROS_EC_SPI=y
>  CONFIG_MFD_MAX77686=y
>  CONFIG_MFD_MAX8997=y
>  CONFIG_MFD_SEC_CORE=y
> @@ -80,6 +96,7 @@ CONFIG_REGULATOR_FIXED_VOLTAGE=y
>  CONFIG_REGULATOR_GPIO=y
>  CONFIG_REGULATOR_MAX8997=y
>  CONFIG_REGULATOR_MAX77686=y
> +CONFIG_REGULATOR_S2MPA01=y
>  CONFIG_REGULATOR_S2MPS11=y
>  CONFIG_REGULATOR_S5M8767=y
>  CONFIG_REGULATOR_TPS65090=y
> @@ -88,28 +105,50 @@ CONFIG_FB_MODE_HELPERS=y
>  CONFIG_FB_SIMPLE=y
>  CONFIG_EXYNOS_VIDEO=y
>  CONFIG_EXYNOS_MIPI_DSI=y
> -CONFIG_EXYNOS_DP=y
>  CONFIG_FRAMEBUFFER_CONSOLE=y
>  CONFIG_FONTS=y
>  CONFIG_FONT_7x14=y
>  CONFIG_LOGO=y
> +CONFIG_SOUND=y
> +CONFIG_SND=y
> +CONFIG_SND_SOC=y
> +CONFIG_SND_SOC_SAMSUNG=y
> +CONFIG_SND_SOC_SNOW=y
>  CONFIG_USB=y
> +CONFIG_USB_XHCI_HCD=y
>  CONFIG_USB_EHCI_HCD=y
>  CONFIG_USB_EHCI_EXYNOS=y
> +CONFIG_USB_OHCI_HCD=y
> +CONFIG_USB_OHCI_EXYNOS=y
>  CONFIG_USB_STORAGE=y
>  CONFIG_USB_DWC3=y
> -CONFIG_USB_PHY=y
> -CONFIG_SAMSUNG_USB2PHY=y
> -CONFIG_SAMSUNG_USB3PHY=y
> +CONFIG_USB_HSIC_USB3503=y
>  CONFIG_MMC=y
>  CONFIG_MMC_SDHCI=y
>  CONFIG_MMC_SDHCI_S3C=y
> +CONFIG_MMC_SDHCI_S3C_DMA=y
>  CONFIG_MMC_DW=y
>  CONFIG_MMC_DW_IDMAC=y
>  CONFIG_MMC_DW_EXYNOS=y
>  CONFIG_RTC_CLASS=y
> +CONFIG_RTC_DRV_MAX77686=y
> +CONFIG_RTC_DRV_S5M=y
>  CONFIG_RTC_DRV_S3C=y
> +CONFIG_DMADEVICES=y
> +CONFIG_PL330_DMA=y
>  CONFIG_COMMON_CLK_MAX77686=y
> +CONFIG_COMMON_CLK_S2MPS11=y
> +CONFIG_EXYNOS_IOMMU=y
> +CONFIG_IIO=y

optional: You could probably =m this (and the ADC).  Better to test
the =m case I think and there's no strong need for this to be in the
kernel.

> +CONFIG_EXYNOS_ADC=y
> +CONFIG_PWM=y
> +CONFIG_PWM_SAMSUNG=y
> +CONFIG_PHY_EXYNOS5250_SATA=y
> +CONFIG_PHY_SAMSUNG_USB2=y
> +CONFIG_PHY_EXYNOS4210_USB2=y
> +CONFIG_PHY_EXYNOS4X12_USB2=y
> +CONFIG_PHY_EXYNOS5250_USB2=y
> +CONFIG_PHY_EXYNOS5_USBDRD=y
>  CONFIG_EXT2_FS=y
>  CONFIG_EXT3_FS=y
>  CONFIG_EXT4_FS=y
> @@ -123,6 +162,7 @@ CONFIG_NLS_CODEPAGE_437=y
>  CONFIG_NLS_ASCII=y
>  CONFIG_NLS_ISO8859_1=y
>  CONFIG_PRINTK_TIME=y
> +CONFIG_DEBUG_FS=y
>  CONFIG_MAGIC_SYSRQ=y
>  CONFIG_DEBUG_KERNEL=y
>  CONFIG_DETECT_HUNG_TASK=y
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Olof Johansson July 14, 2014, 6:50 p.m. UTC | #4 
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
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.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Doug Anderson July 14, 2014, 7:24 p.m. UTC | #5 
To comment on the snow failures that I know about:

On Mon, Jul 14, 2014 at 11:50 AM, Olof Johansson <olof@lixom.net> wrote:
> [ERR] [    2.118115] cros-ec-i2c-tunnel cros-ec-i2c-tunnel.2: Couldn't
> read remote-bus property

Known issue.  The i2c-tunnel is not present on snow.  This will be
fixed once we send up <http://crosreview.com/173927>.  Work for that
is tracked in <http://crbug.com/391797>.  The errors is harmless and
just annoying till then.


> [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

I have resent the patch to fix this 4 times with no avail.  I'm
getting a little tired of reposting.  I figure that I'll wait another
month and try again--maybe the charger subsystem will be in better
hands by then.

Until the charger fix lands then the charger in tps65090 will not be
functional, but this isn't a terrible burden on the rest of the
system.  It's hard to tell if your battery is plugged in but otherwise
the EC handles charging.


-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Kim Kukjin July 15, 2014, 1:28 a.m. UTC | #6 
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

--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Olof Johansson July 15, 2014, 1:46 a.m. UTC | #7 
On Mon, Jul 14, 2014 at 6:28 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> 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.

3.16 is regressions-only now, so this is 3.17 material now.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Sachin Kamat July 15, 2014, 4:18 a.m. UTC | #8 
Hi Doug,

On Mon, Jul 14, 2014 at 10:17 PM, 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.

I have left them out for now in the hope that they would soon get
obsoleted by the
latest patchset migrating to generic CPUFreq driver. I will send a
second round of
update around rc-7 based on the drivers prevalent then.

>
> 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.

My plan was to include only basic things which are currently
functional in the first
round and then enable CPUFreq, DRM and PMIC (for 5420/5800) in the second round
(based on the merge status). Display/panel/bridge related patches are
not yet merged
and enabling hdmi, etc. would give errors as regulator is not
available. Again a second
round material.

>
> I would strongly suggest PREMPT_VOLUNTARY=y for now (again in a
> separate patch).

OK.

>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

OK.

>
> ...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

OK. I would need someone to test these though.

>
>
> Possibly you should be enabling the battery eventually since
> Chromebooks have these too:
>   CONFIG_BATTERY_SBS=m

Sure.

>
> You're enabling the adc, but not what's hooked up to it:
>   CONFIG_SENSORS_NTC_THERMISTOR=m

OK.

>
> The eMMC that ships on Chromebooks has more than 8 partitions, so you
> probably should have this:
>   CONFIG_MMC_BLOCK_MINORS=16

OK.

>
> There's a light sensor on most ARM Chromebooks:
>   CONFIG_SENSORS_ISL29018=m

OK.

>
>
>
> All of the above could be in followup patches, so:
>
> Tested-by: Doug Anderson <dianders@chromium.org>
> Reviewed-by: Doug Anderson <dianders@chromium.org>

Thanks for your review and testing.

<snip>

>> +CONFIG_COMMON_CLK_S2MPS11=y
>> +CONFIG_EXYNOS_IOMMU=y
>> +CONFIG_IIO=y
>
> optional: You could probably =m this (and the ADC).  Better to test
> the =m case I think and there's no strong need for this to be in the
> kernel.

OK.
Sachin Kamat July 15, 2014, 4:31 a.m. UTC | #9 
On Tue, Jul 15, 2014 at 12:20 AM, Olof Johansson <olof@lixom.net> 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:

<snip>

> Gave this a go on my board farm as well, it looks better than before
> 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.

Thanks for your review and testing.

>
> 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

Vivek had submitted patches for the same [1].
Vivek, any updates?

[1] https://lkml.org/lkml/2014/6/25/363

> [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

I think similar patches as with USB are required here.
Naveen, comments?
Naveen Krishna Ch July 15, 2014, 8:25 a.m. UTC | #10 
Hello Sachin,

On 15 July 2014 10:01, Sachin Kamat <spk.linux@gmail.com> wrote:
> On Tue, Jul 15, 2014 at 12:20 AM, Olof Johansson <olof@lixom.net> 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:
>
> <snip>
>
>> Gave this a go on my board farm as well, it looks better than before
>> 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.
>
> Thanks for your review and testing.
>
>>
>> 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
>
> Vivek had submitted patches for the same [1].
> Vivek, any updates?
>
> [1] https://lkml.org/lkml/2014/6/25/363
>
>> [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
>
> I think similar patches as with USB are required here.
> Naveen, comments?

The "vtmu" regulator supply is required only for one of the Exynos4412
based boards.
There is a TODO in the driver for the same.

This warning can be ignored for Exynos5 based platforms.

>
> --
> Regards,
> Sachin.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Vivek Gautam July 15, 2014, 10:47 a.m. UTC | #11 
On Tue, Jul 15, 2014 at 10:01 AM, Sachin Kamat <spk.linux@gmail.com> wrote:
> On Tue, Jul 15, 2014 at 12:20 AM, Olof Johansson <olof@lixom.net> 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:
>
> <snip>
>
>> Gave this a go on my board farm as well, it looks better than before
>> 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.
>
> Thanks for your review and testing.
>
>>
>> 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
>
> Vivek had submitted patches for the same [1].
> Vivek, any updates?
>
> [1] https://lkml.org/lkml/2014/6/25/363

Well, these messages are coming out of DWC3, where VDD3.3 and VDD1.0
regulators are expected.
These regulator right now are required by smdk5250, and on boards on
which the USB Vdd regulators are not
enabled by default. On peach and snow, this will just be a warning and
we will go ahead with the probe.

To add the required dt entry for these regulators is in my TODO list,
but on snow and peach there's no regression
due to unavailability of these, since the required regulator supplies
are enabled by default.

[snip]
Javier Martinez Canillas July 17, 2014, 9:30 p.m. UTC | #12 
Hello,

On 07/14/2014 09:24 PM, Doug Anderson wrote:
> 
>> [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
> 
> I have resent the patch to fix this 4 times with no avail.  I'm
> getting a little tired of reposting.  I figure that I'll wait another
> month and try again--maybe the charger subsystem will be in better
> hands by then.

FYI, Sebastian Reichel has applied [0] Doug's patch.

Best regards,
Javier

[0]:
https://git.kernel.org/cgit/linux/kernel/git/sre/linux-power-supply.git/commit/?h=dev&id=5a3effdc8877132fd12f97fea0d4756614b911c7
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
index e07a227ec0db..fc7d1683bf67 100644
--- a/arch/arm/configs/exynos_defconfig
+++ b/arch/arm/configs/exynos_defconfig
@@ -8,15 +8,17 @@  CONFIG_MODULE_UNLOAD=y
 # CONFIG_BLK_DEV_BSG is not set
 CONFIG_PARTITION_ADVANCED=y
 CONFIG_ARCH_EXYNOS=y
-CONFIG_S3C_LOWLEVEL_UART_PORT=3
-CONFIG_S3C24XX_PWM=y
-CONFIG_ARCH_EXYNOS5=y
-CONFIG_MACH_EXYNOS4_DT=y
+CONFIG_ARCH_EXYNOS3=y
+CONFIG_EXYNOS5420_MCPM=y
 CONFIG_SMP=y
+CONFIG_BIG_LITTLE=y
+CONFIG_BL_SWITCHER=y
+CONFIG_BL_SWITCHER_DUMMY_IF=y
 CONFIG_NR_CPUS=8
 CONFIG_PREEMPT=y
 CONFIG_AEABI=y
 CONFIG_HIGHMEM=y
+CONFIG_CMA=y
 CONFIG_ZBOOT_ROM_TEXT=0x0
 CONFIG_ZBOOT_ROM_BSS=0x0
 CONFIG_ARM_APPENDED_DTB=y
@@ -24,6 +26,7 @@  CONFIG_ARM_ATAG_DTB_COMPAT=y
 CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200 init=/linuxrc mem=256M"
 CONFIG_VFP=y
 CONFIG_NEON=y
+CONFIG_PM_RUNTIME=y
 CONFIG_NET=y
 CONFIG_PACKET=y
 CONFIG_UNIX=y
@@ -34,6 +37,8 @@  CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
 CONFIG_DEVTMPFS=y
 CONFIG_DEVTMPFS_MOUNT=y
 CONFIG_PROC_DEVICETREE=y
+CONFIG_DMA_CMA=y
+CONFIG_CMA_SIZE_MBYTES=64
 CONFIG_BLK_DEV_LOOP=y
 CONFIG_BLK_DEV_CRYPTOLOOP=y
 CONFIG_BLK_DEV_RAM=y
@@ -66,11 +71,22 @@  CONFIG_I2C=y
 CONFIG_I2C_MUX=y
 CONFIG_I2C_ARB_GPIO_CHALLENGE=y
 CONFIG_I2C_EXYNOS5=y
+CONFIG_I2C_CROS_EC_TUNNEL=y
+CONFIG_SPI=y
+CONFIG_SPI_S3C64XX=y
 CONFIG_I2C_S3C2410=y
 CONFIG_DEBUG_GPIO=y
+CONFIG_POWER_SUPPLY=y
+CONFIG_CHARGER_TPS65090=y
 # CONFIG_HWMON is not set
+CONFIG_THERMAL=y
+CONFIG_EXYNOS_THERMAL=y
+CONFIG_EXYNOS_THERMAL_CORE=y
+CONFIG_WATCHDOG=y
+CONFIG_S3C2410_WATCHDOG=y
 CONFIG_MFD_CROS_EC=y
 CONFIG_MFD_CROS_EC_I2C=y
+CONFIG_MFD_CROS_EC_SPI=y
 CONFIG_MFD_MAX77686=y
 CONFIG_MFD_MAX8997=y
 CONFIG_MFD_SEC_CORE=y
@@ -80,6 +96,7 @@  CONFIG_REGULATOR_FIXED_VOLTAGE=y
 CONFIG_REGULATOR_GPIO=y
 CONFIG_REGULATOR_MAX8997=y
 CONFIG_REGULATOR_MAX77686=y
+CONFIG_REGULATOR_S2MPA01=y
 CONFIG_REGULATOR_S2MPS11=y
 CONFIG_REGULATOR_S5M8767=y
 CONFIG_REGULATOR_TPS65090=y
@@ -88,28 +105,50 @@  CONFIG_FB_MODE_HELPERS=y
 CONFIG_FB_SIMPLE=y
 CONFIG_EXYNOS_VIDEO=y
 CONFIG_EXYNOS_MIPI_DSI=y
-CONFIG_EXYNOS_DP=y
 CONFIG_FRAMEBUFFER_CONSOLE=y
 CONFIG_FONTS=y
 CONFIG_FONT_7x14=y
 CONFIG_LOGO=y
+CONFIG_SOUND=y
+CONFIG_SND=y
+CONFIG_SND_SOC=y
+CONFIG_SND_SOC_SAMSUNG=y
+CONFIG_SND_SOC_SNOW=y
 CONFIG_USB=y
+CONFIG_USB_XHCI_HCD=y
 CONFIG_USB_EHCI_HCD=y
 CONFIG_USB_EHCI_EXYNOS=y
+CONFIG_USB_OHCI_HCD=y
+CONFIG_USB_OHCI_EXYNOS=y
 CONFIG_USB_STORAGE=y
 CONFIG_USB_DWC3=y
-CONFIG_USB_PHY=y
-CONFIG_SAMSUNG_USB2PHY=y
-CONFIG_SAMSUNG_USB3PHY=y
+CONFIG_USB_HSIC_USB3503=y
 CONFIG_MMC=y
 CONFIG_MMC_SDHCI=y
 CONFIG_MMC_SDHCI_S3C=y
+CONFIG_MMC_SDHCI_S3C_DMA=y
 CONFIG_MMC_DW=y
 CONFIG_MMC_DW_IDMAC=y
 CONFIG_MMC_DW_EXYNOS=y
 CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_MAX77686=y
+CONFIG_RTC_DRV_S5M=y
 CONFIG_RTC_DRV_S3C=y
+CONFIG_DMADEVICES=y
+CONFIG_PL330_DMA=y
 CONFIG_COMMON_CLK_MAX77686=y
+CONFIG_COMMON_CLK_S2MPS11=y
+CONFIG_EXYNOS_IOMMU=y
+CONFIG_IIO=y
+CONFIG_EXYNOS_ADC=y
+CONFIG_PWM=y
+CONFIG_PWM_SAMSUNG=y
+CONFIG_PHY_EXYNOS5250_SATA=y
+CONFIG_PHY_SAMSUNG_USB2=y
+CONFIG_PHY_EXYNOS4210_USB2=y
+CONFIG_PHY_EXYNOS4X12_USB2=y
+CONFIG_PHY_EXYNOS5250_USB2=y
+CONFIG_PHY_EXYNOS5_USBDRD=y
 CONFIG_EXT2_FS=y
 CONFIG_EXT3_FS=y
 CONFIG_EXT4_FS=y
@@ -123,6 +162,7 @@  CONFIG_NLS_CODEPAGE_437=y
 CONFIG_NLS_ASCII=y
 CONFIG_NLS_ISO8859_1=y
 CONFIG_PRINTK_TIME=y
+CONFIG_DEBUG_FS=y
 CONFIG_MAGIC_SYSRQ=y
 CONFIG_DEBUG_KERNEL=y
 CONFIG_DETECT_HUNG_TASK=y