Re: [linux-yocto] [PATCH 0/1] Fix i915 merge

[Sullivan, California L]

It looks like the new kernel tools don't like the KERNEL_FEATURES variable 
being empty. The base and -rt kernels add features/netfilter/netfilter.scc, and 
features/debug/printk.scc is added to all QEMU machines in linux-yocto.inc so 
it hasn't been hit before.

Adding anything to the KERNEL_FEATURES variable allowed me to built -tiny 
successfully for intel-quark.

---
Cal

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Monday, August 22, 2016 12:06 PM
To: Sullivan, California L; linux-yocto@yoctoproject.org
Cc: Ernst, Eric
Subject: Re: [PATCH 0/1][linux-yocto] Fix i915 merge

On 2016-08-22 2:20 PM, Sullivan, California L wrote:
> Hmm, the patches apply directly just fine. Preempt-rt has a few specific
> changes, but tiny has a zero diff for i915. I'm not sure why the default
> merge strategy isn't working.
>
> In any case, using 'git merge strategy=resolve' seems to work, we get
> the expected diff, and preempt-rt compiles again. Tiny compiles with the

I can do that, but would have preferred a fixed up pull request, since
-Xours always works as well, but isn't necessarily the right thing.

I'll take care of the update, and if it is still broken, feel free to
fire off more patches.

> old kernel tools. Tiny appears to not like the new kernel tools, as
> do_kernel_metadata fails until I revert back to old tools even with old
> SRCREVs, but I'll leave that for another time.

I just built tiny for qemux86 with no issues:

NOTE: Executing SetScene Tasks



NOTE: Executing RunQueue Tasks



WARNING: linux-yocto-tiny-4.4.18+gitAUTOINC+6a12efcabe_0a0c93f29c-r0
do_kernel_configcheck: [kernel config]: specified values did not make it
into the kernel's final configuration:





-- CONFIG_TINY_RCU -



Config: CONFIG_TINY_RCU



From:
/home/bruce/poky/build/tmp/work-shared/qemux86/kernel-source/.kernel-meta/configs/standard/tiny/ktypes/tiny/tiny.cfg


Requested value:  CONFIG_TINY_RCU=y



Actual value:







Config 'TINY_RCU' has the following conditionals:



   !PREEMPT && !SMP (value: "n")



Dependency values are:



   PREEMPT [y] y [y] SMP [y]







-- CONFIG_BASE_SMALL -



Config: CONFIG_BASE_SMALL



From:
/home/bruce/poky/build/tmp/work-shared/qemux86/kernel-source/.kernel-meta/configs/standard/tiny/ktypes/tiny/tiny.cfg


Requested value:  CONFIG_BASE_SMALL=1



Actual value: CONFIG_BASE_SMALL=0







Config 'BASE_SMALL' has the following conditionals:



   BASE_FULL (value: "y")



!BASE_FULL (value: "n")



Dependency values are:



   1 [1] 0 [0] BASE_FULL [y]











NOTE: Tasks Summary: Attempted 453 tasks of which 387 didn't need to be
rerun and all succeeded.






Summary: There were 5 WARNING messages shown.



Bruce

>
> ---
> Cal
>
> On 08/19/2016 09:24 PM, Bruce Ashfield wrote:
>> On 2016-08-19 11:35 PM, California Sullivan wrote:
>>> Eric, Bruce, please make sure my strategy with this fix is sane before
>>> merging.
>> Looks sane to me, if it gets things building .. that's good enough
>> for now. We can always apply more patches.
>>
>>> If it is, please apply it to standard/intel/base and merge into all the
>>> other intel branches.
>> I put this onto standard/intel/base and merged it into
>> standard/intel/bxt-rebase.
>>
>> But I'm getting drm conflicts when I merged standard/intel/base into
>> standard/preempt-rt/intel/base and standard/tiny/intel/base. So we need
>> to look at those branches and identify what is missing (since I already
>> have the same 4.4.18 and drm content merged to it already).
>>
>> Bruce
>>
>>> Thanks,
>>> Cal Sullivan
>>>
>>> California Sullivan (1):
>>>   drm/i915: Fix i915 merge with v4.4.16
>>>
>>>  drivers/gpu/drm/i915/i915_reg.h   |  2 ++
>>>  drivers/gpu/drm/i915/intel_dp.c   | 11 +--
>>>  drivers/gpu/drm/i915/intel_dp_link_training.c | 26 
>>> ++
>>>  drivers/gpu/drm/i915/intel_drv.h  |  2 --
>>>  4 files changed, 9 insertions(+), 32 deletions(-)
>>>
>>
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 1/3] features: Fix dependencies and =m vs =y discrepancies for corei7

[Sullivan, California L]

On 08/20/2016 08:45 PM, Wold, Saul wrote:
> On Fri, 2016-08-19 at 20:40 -0700, California Sullivan wrote:
>> I missed these in my first pass. This should fix the remaining
>> warnings
>> that occur with the intel-corei7-64 configurations. The ISDN
>> configurations might need to be broken out into their own feature but
>> for now just enable them as dependencies for BT_CMTP.
>>
>> Signed-off-by: California Sullivan 
>> ---
>>  features/bluetooth/bluetooth.cfg   | 7 ++-
>>  features/ieee802154/ieee802154.cfg | 2 +-
>>  2 files changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/features/bluetooth/bluetooth.cfg
>> b/features/bluetooth/bluetooth.cfg
>> index fefb357..67d3f52 100644
>> --- a/features/bluetooth/bluetooth.cfg
>> +++ b/features/bluetooth/bluetooth.cfg
>> @@ -1,5 +1,10 @@
>> +# Dependencies
>> +CONFIG_ISDN=y
>> +CONFIG_ISDN_CAPI=m
>> +
>> +# Features
>>  CONFIG_BT=y
>> -CONFIG_BT_6LOWPAN=y
>> +CONFIG_BT_6LOWPAN=m
>>  CONFIG_BT_RFCOMM=m
>>  CONFIG_BT_RFCOMM_TTY=y
>>  CONFIG_BT_BNEP=m
>> diff --git a/features/ieee802154/ieee802154.cfg
>> b/features/ieee802154/ieee802154.cfg
>> index bd6c214..518adf0 100644
>> --- a/features/ieee802154/ieee802154.cfg
>> +++ b/features/ieee802154/ieee802154.cfg
>> @@ -1,2 +1,2 @@
>>  CONFIG_IEEE802154=y
>> -CONFIG_IEEE802154_6LOWPAN=y
>> +CONFIG_IEEE802154_6LOWPAN=m
>> -- 
> Do we also need a 6lowpan feature scc file?
>
> Sau!

We have a 6lowpan feature. Right now its a minimal configuration to
satisfy those two CONFIGs,  and is included in their features'
respective .scc files. We could have those 6LOWPAN CONFIGs in the
6lowpan feature, but then we would need the 6lowpan feature to depend on
these two features and add it everywhere one of these two features are
used. I think this way is cleaner, but if you prefer it the other way
its a simple change.

---
Cal

>
>> 2.5.5
>>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 0/1] Fix i915 merge

[Sullivan, California L]

Hmm, the patches apply directly just fine. Preempt-rt has a few specific
changes, but tiny has a zero diff for i915. I'm not sure why the default
merge strategy isn't working.

In any case, using 'git merge strategy=resolve' seems to work, we get
the expected diff, and preempt-rt compiles again. Tiny compiles with the
old kernel tools. Tiny appears to not like the new kernel tools, as
do_kernel_metadata fails until I revert back to old tools even with old
SRCREVs, but I'll leave that for another time.

---
Cal

On 08/19/2016 09:24 PM, Bruce Ashfield wrote:
> On 2016-08-19 11:35 PM, California Sullivan wrote:
>> Eric, Bruce, please make sure my strategy with this fix is sane before
>> merging.
> Looks sane to me, if it gets things building .. that's good enough
> for now. We can always apply more patches.
>
>> If it is, please apply it to standard/intel/base and merge into all the
>> other intel branches.
> I put this onto standard/intel/base and merged it into 
> standard/intel/bxt-rebase.
>
> But I'm getting drm conflicts when I merged standard/intel/base into
> standard/preempt-rt/intel/base and standard/tiny/intel/base. So we need
> to look at those branches and identify what is missing (since I already
> have the same 4.4.18 and drm content merged to it already).
>
> Bruce
>
>> Thanks,
>> Cal Sullivan
>>
>> California Sullivan (1):
>>   drm/i915: Fix i915 merge with v4.4.16
>>
>>  drivers/gpu/drm/i915/i915_reg.h   |  2 ++
>>  drivers/gpu/drm/i915/intel_dp.c   | 11 +--
>>  drivers/gpu/drm/i915/intel_dp_link_training.c | 26 
>> ++
>>  drivers/gpu/drm/i915/intel_drv.h  |  2 --
>>  4 files changed, 9 insertions(+), 32 deletions(-)
>>
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 5/6] [UPSTREAMED] acpi: add support for configfs

[Sullivan, California L]

In an allmodconfig build I found that configfs (CONFIG_ACPI_CONFIGFS=m
introduced in this patch) fails to compile on both standard/intel/base
and standard/intel/bxt-rebase branches.
Sebastien, could you look into what it takes to fix this?

Thanks,
Cal Sullivan

On 07/11/2016 03:35 PM, Sebastien Boeuf wrote:
> From: Octavian Purdila 
>
> Register the ACPI subsystem with configfs.
>
> Patch slightly modified because of cherry-pick conflict
> in Makefile.
>
> Signed-off-by: Octavian Purdila 
> Signed-off-by: Sebastien Boeuf 
>
> Conflicts:
>   drivers/acpi/Makefile
> ---
>  Documentation/ABI/testing/configfs-acpi |  7 +
>  MAINTAINERS |  1 +
>  drivers/acpi/Kconfig|  9 ++
>  drivers/acpi/Makefile   |  1 +
>  drivers/acpi/configfs.c | 53 
> +
>  5 files changed, 71 insertions(+)
>  create mode 100644 Documentation/ABI/testing/configfs-acpi
>  create mode 100644 drivers/acpi/configfs.c
>
> diff --git a/Documentation/ABI/testing/configfs-acpi 
> b/Documentation/ABI/testing/configfs-acpi
> new file mode 100644
> index 000..17b19dc
> --- /dev/null
> +++ b/Documentation/ABI/testing/configfs-acpi
> @@ -0,0 +1,7 @@
> +What:/config/acpi
> +Date:July 2016
> +KernelVersion:   4.8
> +Contact: linux-a...@vger.kernel.org
> +Description:
> + This represents the ACPI subsystem entry point directory. It
> + contains sub-groups corresponding to ACPI configurable options.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index be51c13..278c0f4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -279,6 +279,7 @@ F:include/linux/acpi.h
>  F:   include/acpi/
>  F:   Documentation/acpi/
>  F:   Documentation/ABI/testing/sysfs-bus-acpi
> +F:   Documentation/ABI/testing/configfs-acpi
>  F:   drivers/pci/*acpi*
>  F:   drivers/pci/*/*acpi*
>  F:   drivers/pci/*/*/*acpi*
> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> index 1741c68..daa9c90 100644
> --- a/drivers/acpi/Kconfig
> +++ b/drivers/acpi/Kconfig
> @@ -516,4 +516,13 @@ config BXT_WC_PMIC_OPREGION
>  
>  endif
>  
> +config ACPI_CONFIGFS
> + tristate "ACPI configfs support"
> + select CONFIGFS_FS
> + default n
> + help
> +   Select this option to enable support for ACPI configuration from
> +   userspace. The configurable ACPI groups will be visible under
> +   /config/acpi, assuming configfs is mounted under /config.
> +
>  endif# ACPI
> diff --git a/drivers/acpi/Makefile b/drivers/acpi/Makefile
> index ad48a9e..dcccf2e 100644
> --- a/drivers/acpi/Makefile
> +++ b/drivers/acpi/Makefile
> @@ -97,5 +97,6 @@ obj-$(CONFIG_PMIC_OPREGION) += pmic/intel_pmic.o
>  obj-$(CONFIG_CRC_PMIC_OPREGION) += pmic/intel_pmic_crc.o
>  obj-$(CONFIG_XPOWER_PMIC_OPREGION) += pmic/intel_pmic_xpower.o
>  obj-$(CONFIG_BXT_WC_PMIC_OPREGION) += pmic/intel_pmic_bxtwc.o
> +obj-$(CONFIG_ACPI_CONFIGFS)  += configfs.o
>  
>  video-objs   += acpi_video.o video_detect.o
> diff --git a/drivers/acpi/configfs.c b/drivers/acpi/configfs.c
> new file mode 100644
> index 000..44a72ff
> --- /dev/null
> +++ b/drivers/acpi/configfs.c
> @@ -0,0 +1,53 @@
> +/*
> + * ACPI configfs support
> + *
> + * Copyright (c) 2015 Intel Corporation
> + *
> + * This program is free software; you can redistribute it and/or modify it
> + * under the terms of the GNU General Public License version 2 as published 
> by
> + * the Free Software Foundation.
> + */
> +
> +#include 
> +#include 
> +#include 
> +#include 
> +
> +static struct config_item_type acpi_root_group_type = {
> + .ct_owner = THIS_MODULE,
> +};
> +
> +static struct configfs_subsystem acpi_configfs = {
> + .su_group = {
> + .cg_item = {
> + .ci_namebuf = "acpi",
> + .ci_type = _root_group_type,
> + },
> + },
> + .su_mutex = __MUTEX_INITIALIZER(acpi_configfs.su_mutex),
> +};
> +
> +static int __init acpi_configfs_init(void)
> +{
> + int ret;
> + struct config_group *root = _configfs.su_group;
> +
> + config_group_init(root);
> +
> + ret = configfs_register_subsystem(_configfs);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> +module_init(acpi_configfs_init);
> +
> +static void __exit acpi_configfs_exit(void)
> +{
> + configfs_unregister_subsystem(_configfs);
> +}
> +module_exit(acpi_configfs_exit);
> +
> +MODULE_AUTHOR("Octavian Purdila ");
> +MODULE_DESCRIPTION("ACPI configfs support");
> +MODULE_LICENSE("GPL v2");

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [yocto-kernel-cache] [PATCH] Fix bitbake warnings on build

[Sullivan, California L]

Ack'd. It looks like we need this for 4.4 and master as well.

Thanks,
Cal

On 06/27/2016 12:14 AM, rebecca.swee.fun.ch...@intel.com wrote:
> From: Rebecca Chang Swee Fun 
>
> Hi Bruce,
>
> With a build test run on Intel Common BSP, some warning messages poped
> out about actual value set is not matched with requested value on
> CONFIG_GPIO_GENERIC.
>
> This can be resolved by setting CONFIG_GPIO_GENERIC_PLATFORM=y
> since CONFIG_GPIO_GENERIC is tristate selected by 
> CONFIG_GPIO_GENERIC_PLATFORM.
>
> This is only targetted to fix on yocto-4.1 branch.
>
> Please review and feedback if you have any. Thank you!
>
> Regards,
> Rebecca
>
> Rebecca Chang Swee Fun (1):
>   broxton: set CONFIG_GPIO_GENERIC_PLATFORM instead of
> CONFIG_GPIO_GENERIC
>
>  features/soc/broxton/broxton.cfg | 1 +
>  1 file changed, 1 insertion(+)
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 0/4] mmc backports for linux-yocto-4.4 standard/base and standard/intel

[Sullivan, California L]

It looks like "mmc: sdhci-pci: Remove MMC_CAP_BUS_WIDTH_TEST for Intel
controller" was brought in by the 4.4.12 update. Drop that one and they
should apply.

Thanks,
Cal


On 06/03/2016 09:17 AM, Bruce Ashfield wrote:
> On 2016-06-02 11:08 PM, California Sullivan wrote:
>> Hi Bruce,
>>
>> This set of backports solves some issues we are seeing with mmc on
>> Broxton-based boards. I also tested the updated kernel on a
>> MinnowBoard Turbot and found no additional errors.
>>
>> These commits can also be pulled from
>> git://git.yoctoproject.org/linux-yocto-contrib branch clsulliv/standard/base
> Are the patches on the branch different than the patches to the list ?
> I grabbed the patches in email, and I have rejects with "already applied
> changes".
>
> Maybe standard/base changed since you made the series ? If you could double
> check and let me know, that would be great.
>
> Bruce
>
>> Thanks,
>> Cal Sullivan
>>
>> Adrian Hunter (4):
>>mmc: block: Always switch back to main area after RPMB access
>>mmc: block: Pause re-tuning while switched to the RPMB partition
>>mmc: core: Add a facility to "pause" re-tuning
>>mmc: sdhci-pci: Remove MMC_CAP_BUS_WIDTH_TEST for Intel controller
>>
>>   drivers/mmc/card/block.c  | 19 ++-
>>   drivers/mmc/core/host.c   | 24 
>>   drivers/mmc/host/sdhci-pci-core.c |  5 +
>>   include/linux/mmc/host.h  |  4 
>>   4 files changed, 47 insertions(+), 5 deletions(-)
>>
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [yocto-kernel-cache][PATCHv2 0/4] Enable kernel configuration for Skylake

[Sullivan, California L]

Ack'd. Please merge quickly.

Thanks,
Cal

On 04/29/2016 02:02 AM, chun.weng@intel.com wrote:
> From: Ong Chun Weng 
>
> Hi, 
>
> These patch is to enable the kernel configuration for Skylake. 
> And these patch is tested on Saddlebrook platform.
>
> Please review and merge into yocto-kernel-cache branch yocto-4.4.
>
> Thanks,
> Chun Weng
>
> Ong Chun Weng (4):
>   features: soc: enable configurations for skylake.
>   intel-pinctrl: enable pinctrl driver for skylake
>   intel-common-drivers: enable OSS Support
>   intel-common: enable support for skylake in intel common bsp
>
>  bsp/intel-common/intel-common-drivers.scc |  3 +++
>  bsp/intel-common/intel-core2-32.scc   |  1 +
>  bsp/intel-common/intel-corei7-64.scc  |  1 +
>  features/intel-pinctrl/intel-pinctrl.cfg  |  2 ++
>  features/soc/skylake/skylake.cfg  | 21 +
>  features/soc/skylake/skylake.scc  | 12 
>  6 files changed, 40 insertions(+)
>  create mode 100644 features/soc/skylake/skylake.cfg
>  create mode 100644 features/soc/skylake/skylake.scc
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [yocto-kernel-cache][PATCH 0/6] Enable kernel configuration for Skylake

[Sullivan, California L]

An overarching problem with this patch series is that the commit format
isn't correct.
The general commit format is:

area/modified: What the commit does

Explanation of why this commit is needed/wanted.

Signed-off-by: Your Name 

One-line commit messages should be avoided, and I don't think your
patches will be accepted without a signoff!

Thanks,
Cal

On 04/27/2016 09:24 PM, chun.weng@intel.com wrote:
> From: Ong Chun Weng 
>
> These patch is to enable the kernel configuration for Skylake. 
> And these patch is tested on Saddlebrook platform.
>
> Please review and merge into yocto-kernel-cache branch yocto-4.4.
>
> Thanks,
> Chun Weng
>
> Ong Chun Weng (6):
>   features: soc: enable configurations for skylake
>   intel-pinctrl: enable pinctrl driver for skylake
>   intel-common: add support for more driver features for 32-bit system
>   intel-common-drivers: enable EG20T platform controller hub
>   intel-common-drivers: enable OSS sound support
>   intel-common: enable support for skylake in intel common bsp
>
>  bsp/intel-common/intel-common-drivers-32.scc | 28 
> 
>  bsp/intel-common/intel-common-drivers.scc|  6 ++
>  bsp/intel-common/intel-core2-32.scc  |  1 +
>  bsp/intel-common/intel-corei7-64.scc |  1 +
>  features/intel-pinctrl/intel-pinctrl.cfg |  2 ++
>  features/soc/skylake/skylake.cfg | 22 ++
>  features/soc/skylake/skylake.scc | 12 
>  7 files changed, 72 insertions(+)
>  create mode 100644 features/soc/skylake/skylake.cfg
>  create mode 100644 features/soc/skylake/skylake.scc
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [yocto-kernel-cache][PATCH 4/6] intel-common-drivers: enable EG20T platform controller hub

[Sullivan, California L]

Minor nitpick: Including this in intel-common-drivers.scc means it will
be included in both 32 and 64 bit BSPs, meaning we no longer need it in
intel-common-drivers-32.scc.

---
Cal

On 04/27/2016 09:24 PM, chun.weng@intel.com wrote:
> From: Ong Chun Weng 
>
> ---
>  bsp/intel-common/intel-common-drivers.scc | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/bsp/intel-common/intel-common-drivers.scc 
> b/bsp/intel-common/intel-common-drivers.scc
> index 9beef28..f03e794 100644
> --- a/bsp/intel-common/intel-common-drivers.scc
> +++ b/bsp/intel-common/intel-common-drivers.scc
> @@ -12,6 +12,9 @@ kconf hardware bsp/common-pc/common-pc-eth.cfg
>  kconf hardware bsp/common-pc/common-pc-gfx.cfg
>  kconf hardware bsp/common-pc/common-pc-wifi.cfg
>  
> +# Platform Controller Hun EG20T
> +include features/eg20t/eg20t.scc
> +
>  # PCI
>  include features/pci/pci.scc
>  

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [yocto-kernel-cache][PATCH 1/6] features: soc: enable configurations for skylake

[Sullivan, California L]

What is the rational for CONFIG_DRM_LOAD_EDID_FIRMWARE=y? From my
understanding it is to manually load monitor information for monitors
that don't provide it itself. If my understanding is correct this option
shouldn't be necessary for general Skylake enabling.

---
Cal

On 04/27/2016 09:24 PM, chun.weng@intel.com wrote:
> From: Ong Chun Weng 
>
> ---
>  features/soc/skylake/skylake.cfg | 22 ++
>  features/soc/skylake/skylake.scc | 12 
>  2 files changed, 34 insertions(+)
>  create mode 100644 features/soc/skylake/skylake.cfg
>  create mode 100644 features/soc/skylake/skylake.scc
>
> diff --git a/features/soc/skylake/skylake.cfg 
> b/features/soc/skylake/skylake.cfg
> new file mode 100644
> index 000..5e09436
> --- /dev/null
> +++ b/features/soc/skylake/skylake.cfg
> @@ -0,0 +1,22 @@
> +CONFIG_CPU_IDLE=y
> +CONFIG_MFD_INTEL_LPSS=m
> +CONFIG_MFD_INTEL_LPSS_ACPI=m
> +CONFIG_MFD_INTEL_LPSS_PCI=m
> +CONFIG_INTEL_IDMA64=m
> +CONFIG_GPIO_LYNXPOINT=m
> +CONFIG_USB_EHCI_PCI=y
> +CONFIG_POWERCAP=y
> +CONFIG_INTEL_RAPL=m
> +CONFIG_INTEL_POWERCLAMP=m
> +CONFIG_HWMON=y
> +CONFIG_SENSORS_I5500=m
> +CONFIG_DRM_LOAD_EDID_FIRMWARE=y
> +CONFIG_SND_HDA_I915=y
> +CONFIG_SND_SOC_INTEL_SKL_RT286_MACH=m
> +CONFIG_SND_SOC_INTEL_SST=m
> +CONFIG_SND_SOC_INTEL_SST_ACPI=m
> +CONFIG_SND_DYNAMIC_MINORS=y
> +CONFIG_NETCONSOLE=y
> +CONFIG_BT_HCIUART=m
> +CONFIG_BT_HCIUART_INTEL=y
> +CONFIG_INTEL_MEI_TXE=m
> diff --git a/features/soc/skylake/skylake.scc 
> b/features/soc/skylake/skylake.scc
> new file mode 100644
> index 000..bc59f22
> --- /dev/null
> +++ b/features/soc/skylake/skylake.scc
> @@ -0,0 +1,12 @@
> +# skylake.scc
> +#
> +# Features and devices found on the Skylake SoCs
> +#
> +
> +# Enable I2C Support
> +include features/i2c/i2c.scc
> +
> +# Enable mac 80211 + WLAN support
> +include features/mac80211/mac80211.scc
> +
> +kconf hardware skylake.cfg

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [yocto-kernel-cache][PATCH 3/6] intel-common: add support for more driver features for 32-bit system

[Sullivan, California L]

I don't think this patch is necessary, as other than sound these options
are all in intel-common-drivers.scc.
intel-common-drivers-32.scc should be limited to 32-bit specific features.

---
Cal

On 04/27/2016 09:24 PM, chun.weng@intel.com wrote:
> From: Ong Chun Weng 
>
> Enable features that supported by Skylake in 32-bit intel common BSP.
>
> ---
>  bsp/intel-common/intel-common-drivers-32.scc | 28 
> 
>  1 file changed, 28 insertions(+)
>
> diff --git a/bsp/intel-common/intel-common-drivers-32.scc 
> b/bsp/intel-common/intel-common-drivers-32.scc
> index 7fcddb7..db5fb41 100644
> --- a/bsp/intel-common/intel-common-drivers-32.scc
> +++ b/bsp/intel-common/intel-common-drivers-32.scc
> @@ -3,3 +3,31 @@
>  # Common drivers and technologies to enable intel-common 32bit derived BSPs.
>  #
>  include features/eg20t/eg20t.scc
> +
> +include features/power/intel.scc
> +
> +# OSS sound support
> +include cfg/sound.scc
> +
> +# Enable options for xhci (USB 3.0)
> +include features/usb/xhci-hcd.scc
> +
> +# Enable options for ehci (USB 2.0)
> +include features/usb/ehci-hcd.scc
> +
> +# Coretemp support for Intel platforms
> +include features/thermal/coretemp.scc
> +
> +# Intel High Definition Audio Support
> +include features/sound/snd_hda_intel.scc
> +
> +include features/intel-e1/intel-e1.scc
> +
> +# Enable iwlwifi support
> +include features/iwlwifi/iwlwifi.scc
> +
> +# Bluetooth
> +include features/bluetooth/bluetooth.scc
> +
> +# Enable options for the Intel Management Engine Interface include
> +features/amt/mei/mei.scc


-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 1/1] drm/i915/skl: Fix DMC load on Skylake J0 and K0

[Sullivan, California L]

Hi Bruce,

This is for 4.4 and master.

Thanks,
Cal

On 03/29/2016 10:56 AM, Bruce Ashfield wrote:
> This is for 4.4 or 4.1 ? .. or both ?
>
> Bruce
>
> On 2016-03-28 5:15 PM, California Sullivan wrote:
>> NUC6 (Skylake) graphics firmware fails to load without this patch.
>>
>> From: Mat Martineau 
>>
>> commit a41c8882592fb80458959b10e37632ce030b68ca upstream.
>>
>> The driver does not load firmware for unknown steppings, so these new
>> steppings must be added to the list.
>>
>> Cc: Rodrigo Vivi 
>> Signed-off-by: Mat Martineau 
>> Reviewed-by: Rodrigo Vivi 
>> Signed-off-by: Rodrigo Vivi 
>> Link: 
>> http://patchwork.freedesktop.org/patch/msgid/1454023163-25469-1-git-send-email-mathew.j.martin...@linux.intel.com
>> Signed-off-by: California Sullivan 
>> ---
>>   drivers/gpu/drm/i915/intel_csr.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_csr.c 
>> b/drivers/gpu/drm/i915/intel_csr.c
>> index 9e530a7..fc28c51 100644
>> --- a/drivers/gpu/drm/i915/intel_csr.c
>> +++ b/drivers/gpu/drm/i915/intel_csr.c
>> @@ -180,7 +180,8 @@ struct stepping_info {
>>   static const struct stepping_info skl_stepping_info[] = {
>>  {'A', '0'}, {'B', '0'}, {'C', '0'},
>>  {'D', '0'}, {'E', '0'}, {'F', '0'},
>> -{'G', '0'}, {'H', '0'}, {'I', '0'}
>> +{'G', '0'}, {'H', '0'}, {'I', '0'},
>> +{'J', '0'}, {'K', '0'}
>>   };
>>
>>   static struct stepping_info bxt_stepping_info[] = {
>>
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH v2 00/12] intel-common: add intel-developer-drivers.scc to preempt-rt BSPS

[Sullivan, California L]

On 02/12/2016 07:48 PM, Paul Gortmaker wrote:
> [[PATCH v2 00/12] intel-common: add intel-developer-drivers.scc to preempt-rt 
> BSPS] On 12/02/2016 (Fri 17:42) California Sullivan wrote:
>
>> Since we include the developer ktype we should include developer drivers.
>>
>> Signed-off-by: California Sullivan 
>> ---
>>  bsp/intel-common/intel-core2-32-preempt-rt.scc  | 1 +
>>  bsp/intel-common/intel-corei7-64-preempt-rt.scc | 1 +
>>  2 files changed, 2 insertions(+)
>>
>> diff --git a/bsp/intel-common/intel-core2-32-preempt-rt.scc 
>> b/bsp/intel-common/intel-core2-32-preempt-rt.scc
>> index 08c2ba4..b9be439 100644
>> --- a/bsp/intel-common/intel-core2-32-preempt-rt.scc
>> +++ b/bsp/intel-common/intel-core2-32-preempt-rt.scc
>> @@ -5,4 +5,5 @@ define KARCH i386
>>  include ktypes/preempt-rt/preempt-rt.scc
>>  include intel-common-drivers.scc
>>  include intel-common-drivers-32.scc
>> +include intel-developer-drivers.scc
> I can't tell for sure, because all patches came out with the bogus
> number of 00/12, but mutt shows this patch ahead of the patch that
> actually created intel-developer-drivers.scc ; it has to be after
> or you'll break bisection.
>
> P.
> --
Yeap, I borked the numbering when adding v2 to the subject line. Sorry
about that.

---
Cal

>
>>  include intel-core2-32.scc
>> diff --git a/bsp/intel-common/intel-corei7-64-preempt-rt.scc 
>> b/bsp/intel-common/intel-corei7-64-preempt-rt.scc
>> index 386931c..bee6bba 100644
>> --- a/bsp/intel-common/intel-corei7-64-preempt-rt.scc
>> +++ b/bsp/intel-common/intel-corei7-64-preempt-rt.scc
>> @@ -4,4 +4,5 @@ define KARCH x86_64
>>  
>>  include ktypes/preempt-rt/preempt-rt.scc
>>  include intel-common-drivers.scc
>> +include intel-developer-drivers.scc
>>  include intel-corei7-64.scc
>> -- 
>> 2.5.0
>>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs

[Sullivan, California L]

On 02/07/2016 03:21 PM, Paul Gortmaker wrote:
> [[linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs] On 04/02/2016 (Thu 
> 16:25) California Sullivan wrote:
>
>> These options default to !EXPERT. Since we removed EXPERT from base,
>> these became enabled, adding functionality and size that we do not need.
> I wonder about the "do not need" part.  Nothing is more annoying than
> booting up something and then finding a USB keyboard isn't working
> because of some missing HID driver.  I am guessing that is the logic
> behind the !EXPERT default.
>
> Maybe we want to eat the size increase for standard users and toss the
> is not set values into tiny.cfg for those who are really keen on size?
>
> P.
> --
Funny you should say this. Somebody on the BSP team ran into this just
yesterday!
I agree with you. I'll remove this for v2 and probably send in a
standalone patch that enables more HIDs in base.

---
Cal Sullivan

>> Signed-off-by: California Sullivan 
>> ---
>>  ktypes/base/base.cfg | 11 +++
>>  1 file changed, 11 insertions(+)
>>
>> diff --git a/ktypes/base/base.cfg b/ktypes/base/base.cfg
>> index 30a3f77..f716fb3 100644
>> --- a/ktypes/base/base.cfg
>> +++ b/ktypes/base/base.cfg
>> @@ -791,6 +791,17 @@ CONFIG_WATCHDOG=y
>>  #
>>  # HID Devices
>>  #
>> +# CONFIG_HID_A4TECH is not set
>> +# CONFIG_HID_APPLE is not set
>> +# CONFIG_HID_BELKIN is not set
>> +# CONFIG_HID_CHERRY is not set
>> +# CONFIG_HID_CHICONY is not set
>> +# CONFIG_HID_CYPRESS is not set
>> +# CONFIG_HID_EZKEY is not set
>> +# CONFIG_HID_KENSINGTON is not set
>> +# CONFIG_HID_LOGITECH is not set
>> +# CONFIG_HID_MICROSOFT is not set
>> +# CONFIG_HID_MONTEREY is not set
>>  
>>  #
>>  # USB support
>> -- 
>> 2.5.0
>>
>> -- 
>> ___
>> linux-yocto mailing list
>> linux-yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/linux-yocto

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL

[Sullivan, California L]

On 02/07/2016 03:17 PM, Paul Gortmaker wrote:
> [[linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL] 
> On 04/02/2016 (Thu 16:25) California Sullivan wrote:
>
>> DEBUG_KERNEL should not be in the base ktype, as a production kernel
>> may not necessarily want any debug turned on. EMBEDDED is also removed,
>> as EMBEDDED selects EXPERT which selects DEBUG_KERNEL.
>>
>> Signed-off-by: California Sullivan 
>> ---
>>  ktypes/base/base.cfg | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/ktypes/base/base.cfg b/ktypes/base/base.cfg
>> index 3b8ccd2..30a3f77 100644
>> --- a/ktypes/base/base.cfg
>> +++ b/ktypes/base/base.cfg
>> @@ -33,7 +33,7 @@ CONFIG_INITRAMFS_SOURCE=""
>>  # Resource Groups
>>  #
>>  CONFIG_SYSCTL=y
>> -CONFIG_EMBEDDED=y
>> +# CONFIG_EMBEDDED is not set
> Guessing this is "default n"  [which is also equivalent to no default
> setting at all].  In which case it probably is best to simply not
> specify it at all here.  That will avoid all the extended users getting
> an override warning at kernel config time.
You are are right about the options defaulting to n, but I want it to be
explicit that the base ktype sets them to off.
I believe the kernel_checkconfig task only looks at the last file that
sets a config option. In my testing of the extended ktype, no warning
was issued.

---
Cal
>
>>  CONFIG_KALLSYMS=y
>>  # CONFIG_KALLSYMS_ALL is not set
>>  CONFIG_FUTEX=y
>> @@ -1011,13 +1011,13 @@ CONFIG_NLS_DEFAULT="iso8859-1"
>>  # Kernel hacking
>>  #
>>  CONFIG_MAGIC_SYSRQ=y
>> -CONFIG_DEBUG_KERNEL=y
>> +# CONFIG_DEBUG_KERNEL is not set
> ...same here.
>
> P.
> --
>
>>  # CONFIG_SCHEDSTATS is not set
>>  # CONFIG_DEBUG_SLAB is not set
>>  # CONFIG_DEBUG_SPINLOCK is not set
>>  # CONFIG_DEBUG_KOBJECT is not set
>>  # CONFIG_DEBUG_HIGHMEM is not set
>> -CONFIG_DEBUG_INFO=y
>> +# CONFIG_DEBUG_INFO is not set
>>  
>>  #
>>  # Security options
>> -- 
>> 2.5.0
>>
>> -- 
>> ___
>> linux-yocto mailing list
>> linux-yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/linux-yocto

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in intel-core* bsps

[Sullivan, California L]

On 02/07/2016 03:33 PM, Paul Gortmaker wrote:
> [[linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in 
> intel-core* bsps] On 04/02/2016 (Thu 16:25) California Sullivan wrote:
>
>> Without EXPERT, we hit a select on I2C_I801, forcing it to yes and
>> causing a warning. Set I2C_I801 to yes, and if a bsp wants to build it
>> as a module, it can be done through an extended ktype bsp.
> What exactly was the warning?
>
> P.
> --
>
WARNING: [kernel config]: specified values did not make it into the
kernel's final configuration:

Value requested for CONFIG_I2C_I801 not in final ".config"
Requested value: "CONFIG_I2C_I801=m"
Actual value set: "CONFIG_I2C_I801=y"

---
Cal
>> Signed-off-by: California Sullivan 
>> ---
>>  bsp/haswell-wc/haswell-wc.cfg  | 2 +-
>>  bsp/mohonpeak/mohonpeak.cfg| 2 +-
>>  features/soc/baytrail/baytrail.cfg | 2 +-
>>  3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/bsp/haswell-wc/haswell-wc.cfg b/bsp/haswell-wc/haswell-wc.cfg
>> index 0402847..f2136a8 100644
>> --- a/bsp/haswell-wc/haswell-wc.cfg
>> +++ b/bsp/haswell-wc/haswell-wc.cfg
>> @@ -16,6 +16,6 @@ CONFIG_PM=y
>>  # Platform specific support for the box - LPC, SMBus
>>  CONFIG_LPC_ICH=y
>>  CONFIG_I2C=y
>> -CONFIG_I2C_I801=m
>> +CONFIG_I2C_I801=y
>>  CONFIG_I2C_CHARDEV=y
>>  
>> diff --git a/bsp/mohonpeak/mohonpeak.cfg b/bsp/mohonpeak/mohonpeak.cfg
>> index 87e4d3e..6dd26f4 100644
>> --- a/bsp/mohonpeak/mohonpeak.cfg
>> +++ b/bsp/mohonpeak/mohonpeak.cfg
>> @@ -14,7 +14,7 @@ CONFIG_CHR_DEV_SG=y
>>  
>>  # SMBus Support
>>  CONFIG_I2C=y
>> -CONFIG_I2C_I801=m
>> +CONFIG_I2C_I801=y
>>  CONFIG_I2C_ISMT=m
>>  CONFIG_I2C_CHARDEV=y
>>  
>> diff --git a/features/soc/baytrail/baytrail.cfg 
>> b/features/soc/baytrail/baytrail.cfg
>> index f6dbb9e..0a5e6c1 100644
>> --- a/features/soc/baytrail/baytrail.cfg
>> +++ b/features/soc/baytrail/baytrail.cfg
>> @@ -29,7 +29,7 @@ CONFIG_I2C_DESIGNWARE_PCI=m
>>  CONFIG_I2C_DESIGNWARE_PLATFORM=m
>>  
>>  # SMBus Support
>> -CONFIG_I2C_I801=m
>> +CONFIG_I2C_I801=y
>>  
>>  CONFIG_SPI_PXA2XX=m
>>  
>> -- 
>> 2.5.0
>>
>> -- 
>> ___
>> linux-yocto mailing list
>> linux-yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/linux-yocto

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH] intel_pwm: refactor and use the feature fragment

[Sullivan, California L]

This is only targeted at master/4.4 by the way. In 4.1
CONFIG_PWM_PCA9685 has additional dependencies that we do not want to
enable.

Thanks,
Cal Sullivan

On 01/05/2016 02:04 PM, Sullivan, California L wrote:
> From: California Sullivan <california.l.sulli...@intel.com>
>
> Configure PWMs on Intel platforms as modules and add it to 
> intel-common-drivers.
> Remove PWM configurations from baytrail.cfg since its enabled elsewhere.
>
> Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
> ---
>  bsp/intel-common/intel-common-drivers.scc |  1 +
>  features/pwm/intel_pwm.cfg| 11 ++-
>  features/pwm/intel_pwm.scc|  2 ++
>  features/soc/baytrail/baytrail.cfg|  5 -
>  4 files changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/bsp/intel-common/intel-common-drivers.scc 
> b/bsp/intel-common/intel-common-drivers.scc
> index 7fd0b2f..a7673e7 100644
> --- a/bsp/intel-common/intel-common-drivers.scc
> +++ b/bsp/intel-common/intel-common-drivers.scc
> @@ -65,6 +65,7 @@ include features/thermal/coretemp.scc
>  include features/hugetlb/hugetlb.scc
>  include features/i2c/i2cdev.scc
>  include features/leds/leds.scc
> +include features/pwm/intel_pwm.scc
>  include features/spi/spidev.scc
>  
>  # Miscellaneous
> diff --git a/features/pwm/intel_pwm.cfg b/features/pwm/intel_pwm.cfg
> index 0008a14..6033f08 100644
> --- a/features/pwm/intel_pwm.cfg
> +++ b/features/pwm/intel_pwm.cfg
> @@ -1,6 +1,7 @@
> +# Bay Trail and Braswell PWMs
> +CONFIG_PWM_LPSS=m
> +CONFIG_PWM_LPSS_PCI=m
> +CONFIG_PWM_LPSS_PLATFORM=m
>  
> -CONFIG_PWM_LPSS=y
> -CONFIG_PWM_LPSS_PCI=y
> -CONFIG_PWM_LPSS_PLATFORM=y
> -
> -CONFIG_PWM_PCA9685=y
> +# PWM chip found on Galileo Gen2
> +CONFIG_PWM_PCA9685=m
> diff --git a/features/pwm/intel_pwm.scc b/features/pwm/intel_pwm.scc
> index e0c5337..51a0294 100644
> --- a/features/pwm/intel_pwm.scc
> +++ b/features/pwm/intel_pwm.scc
> @@ -2,4 +2,6 @@
>  define KFEATURE_DESCRIPTION "Enable Intel PWM Devices"
>  define KFEATURE_COMPATIBILITY board
>  
> +include pwm.scc
> +
>  kconf hardware intel_pwm.cfg
> diff --git a/features/soc/baytrail/baytrail.cfg 
> b/features/soc/baytrail/baytrail.cfg
> index 5f809db..f6dbb9e 100644
> --- a/features/soc/baytrail/baytrail.cfg
> +++ b/features/soc/baytrail/baytrail.cfg
> @@ -36,11 +36,6 @@ CONFIG_SPI_PXA2XX=m
>  CONFIG_DW_DMAC=m
>  CONFIG_DW_DMAC_PCI=m
>  
> -# PWM Support
> -CONFIG_PWM=y
> -CONFIG_PWM_LPSS=m
> -CONFIG_PWM_LPSS_PLATFORM=m
> -
>  # USB Device Support
>  CONFIG_USB_DWC3=y
>  CONFIG_USB_DWC3_GADGET=y

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto