Re: [linux-yocto] [PATCH 0/1] power/intel update for 3.17
-Original Message- From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- boun...@yoctoproject.org] On Behalf Of Bruce Ashfield Sent: Monday, November 03, 2014 8:15 AM To: Tom Zanussi; linux-yocto@yoctoproject.org Subject: Re: [linux-yocto] [PATCH 0/1] power/intel update for 3.17 On 14-11-03 10:38 AM, Tom Zanussi wrote: This adds X86_INTEL_PSTATE to the intel power feature. Boot-tested on both nuc and crownbay-noemgd. Please pull into linux-yocto-3.17. The following changes since commit 229ce533868773f201f9ab36e2b4248b381309ec: meta: bump kver to v3.17.1 (2014-10-15 10:09:49 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/3.17-power- pstate http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=t zanussi/3.17-power-pstate Thanks Tom. This is merged, update your meta SRCREVs to take advantage of the functionality. Bruce Hi Bruce, I do not see the change online yet. http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.17/log/?h=meta Can you check whether the commit has been pushed upstream? Thanks, Nitin Tom Zanussi (1): meta: Enable native P state management for power/intel meta/cfg/kernel-cache/features/power/intel.cfg | 1 + 1 file changed, 1 insertion(+) -- ___ 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] serial, 8250_dw: fix linux-yocto merge build issue since v3.10.48
On 10/7/14, 11:39 PM, Ong Boon Leong boon.leong@intel.com wrote:
There is an build issue in following merge-point:
Merge tag 'v3.10.48' into standard/base
60a9d9fc565e4503dbb8705803e83d906afc4ad2
For 8250_dw.c: dw8250_handle_irq() requires the following line
to be restored in order to build successfully.
Signed-off-by: Ong Boon Leong boon.leong@intel.com
I have seen this issue, and I also came up with the exact same fix on my
end.
Acked-By: Nitin A Kamble nitin.a.kam...@intel.com
Nitin
---
drivers/tty/serial/8250/8250_dw.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/tty/serial/8250/8250_dw.c
b/drivers/tty/serial/8250/8250_dw.c
index 36fe9d9..5caf10e 100644
--- a/drivers/tty/serial/8250/8250_dw.c
+++ b/drivers/tty/serial/8250/8250_dw.c
@@ -217,6 +217,7 @@ static unsigned int dw8250_serial_in32(struct
uart_port *p, int offset)
static int dw8250_handle_irq(struct uart_port *p)
{
+ struct dw8250_data *d = p-private_data;
unsigned int iir = p-serial_in(p, UART_IIR);
if (serial8250_handle_irq(p, iir)) {
--
1.7.9.5
--
___
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 0/3] [3.14][dev] meta: Add .scc file for tunnelcreek SoC
For the series: ACKED-BY: Nitin A Kamble nitin.a.kam...@intel.com -Original Message- From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- boun...@yoctoproject.org] On Behalf Of Max Eliaser Sent: Wednesday, September 03, 2014 1:48 PM To: linux-yocto@yoctoproject.org Subject: [linux-yocto] [PATCH 0/3] [3.14][dev] meta: Add .scc file for tunnelcreek SoC Hello list, This series adds a .scc file for the tunnelcreek SoC, similar to the existing baytrail one. The scc file is also included by default in intel-core2-32. This also has the effect of adding the GMA500 DRM driver to intel-core2-32. This, in turn, breaks intel-core2-32 on the FRI2. While the series includes a patch to build the driver as a kernel module, the actual work of blacklisting the gma500_gfx driver on FRI2 has not been done. This series closes bug 6619. [1] This is for the meta branch of linux-yocto 3.14. Regards, -Max Eliaser [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=6619 The following changes since commit 8f553f77e0ad3c9c200d3ecc4ffb59bccc56997a: meta: Create kernel config and scc for CRIU (2014-08-28 15:23:21 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib meliaser/3.14-meta- tunnelcreek-scc http://git.yoctoproject.org/cgit.cgi/linux-yocto- contrib/log/?h=meliaser/3.14-meta-tunnelcreek-scc Max Eliaser (3): soc: tunnelcreek: create tunnelcreek scc intel-common: intel-core-32: use tunnelcreek.scc drm-gma500: build GMA500 DRM driver as kernel module .../kernel-cache/bsp/intel-common/intel-core2-32.scc | 4 +--- .../kernel- cache/features/drm-gma500/drm-gma500.cfg | 2 +- .../features/soc/tunnelcreek/tunnelcreek.scc | 20 3 files changed, 22 insertions(+), 4 deletions(-) create mode 100644 meta/cfg/kernel-cache/features/soc/tunnelcreek/tunnelcreek.scc -- 1.8.3.2 -- ___ 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 00/28][3.10] Baytrail LPSS I/O feature backport
-Original Message- From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- boun...@yoctoproject.org] On Behalf Of rebecca.swee.fun.ch...@intel.com Sent: Thursday, August 28, 2014 3:52 AM To: linux-yocto@yoctoproject.org Subject: [linux-yocto] [PATCH 00/28][3.10] Baytrail LPSS I/O feature backport From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com Hi all, Here is a series of patches that I've cherry-picked from mainline kernel into linux-yocto-3.10. These patches are Baytrail PCI mode LPSS I/O features. The patches consists of PWM, DMA, UART, USB device mode, I2C, and SPI device drivers. These patches was in valleyisland-io-1.0 currently. I will then rebase the valleyisland-io feature branch to reduce the maintenance effort in feature branch. Hi Rebecca, Will the older commit keep working after your rebase? If not, then you may want to create a new feature branch. Nitin To help you in review process, one of the patch is actually pending to mainline and it is now queuing in linux-next git repo. The patch that I mentioned is: e4f08d7 spi/pxa2xx-pci: Add common clock framework support in PCI glue layer while the other patches are confirmed picked from mainline. This series of patches had been built and tested on Bakersports, and MinnowBoard MAX. Please review the series of patches and merge them into linux-yocto-3.10 standard/base branch for feature enabling purposes. Thanks in advance Rebecca The following changes since commit aa677a2d02677ec92d59a8c36d001cf2f5cf3260: usb/core: fix merge issue (2014-06-16 12:24:47 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib rebeccas/baytrail-backport- features http://git.yoctoproject.org/cgit.cgi/linux-yocto- contrib/log/?h=rebeccas/baytrail-backport-features Adrian Hunter (1): mmc: sdhci: Allow for irq being shared Alan Cox (1): pwm: lpss: Add support for PCI devices Alan Stern (1): usb: gadget: don't fail when DMA isn't present Andy Shevchenko (2): dmaengine: dw: introduce dwc_dostart_first_queued() helper dmaengine: dw: don't perform DMA when dmaengine_submit is called Antonio Ospite (1): spi/pxa2xx: fix runtime PM enabling order Chew, Chiau Ee (8): ACPI / LPSS: Add Intel BayTrail ACPI mode PWM dma: dw: Add suspend and resume handling for PCI mode DW_DMAC. i2c: designware-pci: add 10-bit addressing mode functionality for BYT I2C i2c: designware-pci: set ideal HCNT, LCNT and SDA hold time value spi/pxa2xx-pci: Add PCI mode support for BayTrail LPSS SPI spi/pxa2xx: change default supported DMA burst size to 1 spi/pxa2xx: fix incorrect SW mode chipselect setting for BayTrail LPSS SPI spi/pxa2xx-pci: Add common clock framework support in PCI glue layer Felipe Balbi (1): usb: gadget: udc-core: move sysfs_notify() to a workqueue H Hartley Sweeten (1): pwm: Add sysfs interface Heikki Krogerus (3): serial: 8250_dma: check the result of TX buffer mapping serial: 8250: don't change the fifo trigger level when using dma serial: 8250_pci: add support for Intel BayTrail Jingoo Han (2): spi: remove DEFINE_PCI_DEVICE_TABLE macro spi: pxa2xx: remove unnecessary OOM messages Loic Poulain (1): 8250_dw: Support all baudrates on baytrail Maurice Petallo (2): mmc: sdhci: Preset value not supported in Baytrail eMMC mmc: sdhci: add DDR50 1.8V mode support for BayTrail eMMC Controller Mika Westerberg (3): pwm: add support for Intel Low Power Subsystem PWM i2c: designware-pci: Add Baytrail PCI IDs spi/pxa2xx: Prevent DMA from transferring too many bytes Thierry Reding (1): pwm: lpss: Fix const qualifier and sparse warnings Documentation/ABI/testing/sysfs-class-pwm | 79 +++ Documentation/pwm.txt | 37 +++ drivers/acpi/acpi_lpss.c | 11 + drivers/dma/TODO | 1 - drivers/dma/dw/core.c | 38 ++-- drivers/dma/dw/pci.c | 33 +++ drivers/i2c/busses/i2c-designware-pcidrv.c | 66 +- drivers/mmc/host/sdhci-acpi.c | 4 +- drivers/mmc/host/sdhci-pci.c | 3 +- drivers/mmc/host/sdhci.c | 4 +- drivers/pwm/Kconfig| 14 ++ drivers/pwm/Makefile | 2 + drivers/pwm/core.c | 25 +- drivers/pwm/pwm-lpss.c | 282 +++ drivers/pwm/sysfs.c| 352 + drivers/spi/Kconfig| 2 +- drivers/spi/spi-dw-pci.c | 2 +- drivers/spi/spi-pxa2xx-dma.c | 18 +- drivers/spi/spi-pxa2xx-pci.c | 97 ++-- drivers/spi/spi-pxa2xx.c | 28 ++- drivers/spi/spi-topcliff-pch.c | 2 +-
Re: [linux-yocto] [PATCH 0/1] meta: update valleyisland scc to merge new feature branch
Hi Rebecca, As this will be changing the kernel version as well. This change brings in the risk of further delay for the valleyland BSP with the meta-intel 1.6.1 release. How much validation have you done with this change? As some components from SDK image are sensitive to the kernel version. Validation of the sdk image is minimum for pushing this in. Nitin -Original Message- From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- boun...@yoctoproject.org] On Behalf Of rebecca.swee.fun.ch...@intel.com Sent: Tuesday, June 17, 2014 9:55 PM To: linux-yocto@yoctoproject.org Subject: [linux-yocto] [PATCH 0/1] meta: update valleyisland scc to merge new feature branch From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com Hi all, Valley Island I/O feature branch was recently rebased to new version and I would like to push this patch into meta branch so that we can merge the new feature branch with standard/base. This patch is about updating the scc file of Valley Island BSP to merge valleyisland-io-2.0 instead of valleyisland-io-1.0. Please help to merge into linux-yocto-3.10 meta branch. Hope that this will be merge in soon so that I could update the meta branch SRCREV in kernel recipe under meta-intel. After the update for meta-intel are all in place, I will inform Bruce again to remove the old feature branch. Thanks in advance. Regards Rebecca The following changes since commit 199943142f7e0a283240246ee6c02f4376b315f0: meta: bump kver to v3.10.43 (2014-06-16 00:34:31 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib rebeccas/meta-dev http://git.yoctoproject.org/cgit.cgi/linux-yocto- contrib/log/?h=rebeccas/meta-dev Chang Rebecca Swee Fun (1): meta: update valleyisland scc to merge feature branch meta/cfg/kernel-cache/features/valleyisland-io/valleyisland-io-pci.scc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 1.9.1 -- ___ 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] Back-porting a new driver to Yocto kernel(s)..and device firmware
On 6/18/2014 4:24 PM, Allan, Bruce W wrote: We have a new hardware crypto device driver currently out for RFC on the linux-crypto mailing list and would like to back-port it to the Yocto Linux kernels once it is committed upstream. What is the process for getting it into the current dev kernel as well as linux-yocto-3.10 and linux-yocto-3.14? I’ve already done the back-port to the three Yocto Linux kernels and found that just 1 or 2 (depending on the kernel) other patches would also be needed. Is back-porting these patches also allowed as long as they do no harm to anything else? Hi Bruce, The right way is to push these backported patches in the respective stable kernel trees. If that is not working, then the patches can be pushed in the linux-yocto kernel repositories as features. The device also requires a firmware component which has already been committed to the upstream linux-firmware repository. How does this get into Yocto? Then there may not be any thing done for the linux-firmware, as we always try to be up to date with upstream. If you need automatic loading of some modules, then you nay need to add configuration for that to BSPs. Which hardware is this feature for? Possibly we already has a BSP for that hardware, otherwise a new BSP can be created. Nitin Thanks, Bruce Allan. -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 5/5] mei.cfg: configure Intel MEI driver as module
On 5/16/2014 6:58 AM, Ong, Boon Leong wrote: --- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg +++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg @@ -1,4 +1,4 @@ CONFIG_STAGING=y CONFIG_WATCHDOG_CORE=y CONFIG_INTEL_MEI=y The CONFIG_INTEL_MEI also need to be converted to module. I realize that there is no CONFIG_INTEL_MEI_TXE which is meant for BayTrail. mei.scc is added in meta-intel/common/recipes-kernel/linux/linux-yocto_3.10.bbappend with comment for NUC valleyisland. So, I think this is a miss for Baytrail case. I notice that the feature CONFIG_INTEL_MEI_TXE is not in the standard/base branch, so it should not be enabledin a common way. And need to be enabled only with the patches which enable this functionality. Nitin Ya, agree that we should make all of the following configs as module. CONFIG_INTEL_MEI=m CONFIG_INTEL_MEI_ME=m CONFIG_INTEL_MEI_TXE=m I am curious why etc/modprobe.d/blacklist is needed if these are kernel module and the user should have the wisdom to know whether its Romley platform has the correct ME firmware or not. Adding the blacklist will reject any Romley platform with correct ME firmware to load the kernel altogether. + -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/5] [linux-yocto-3.10] Update meta for Romley platform configuration
On 5/15/2014 12:22 PM, wei.sern.c...@intel.com wrote: From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series targetting linux-yocto-3.10:meta branch. This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from romley. 2. Start using ktypes/standard/standard.scc for romley platforms to align with YP1.6 Intel common kernel. 3. Add back RTC configuration for romley after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for romley after changing from common-pc-64.scc to standard.scc. 5. Due to not all platform's BIOS comes ready with AMT/MEI firmware. So will change The issue here is not of missing firmware, but of broken MEI firmware on the target. It is actually a hardware/fimware issue which we are trying to deal with in the OS. CONFIG_INTEL_MEI_ME from built-in driver to as module driver. This will then make possible for appending this driver on /etc/modprobe.d/blacklist to allow Romley to reboot without issue. ( Will place a note on the README to mention that user has to append on /etc/modprobe.d/blacklist to make the reboot happened ). This need be done in a custon recipe for the BSP, instead of mentioning in the README. For this patch series, I have done below:- 1. Build smoothly and boot test on romley. 2. Boot test on Romley via USB drive and SATA. 3. Confirm all the IO drivers are loaded propperly. 4. Confirm reboot issue is solved. Did just converting to modules solved the issue? Or blacklisting of the MEI module was also needed? Thanks, Nitin Thanks. Regards, Chan Wei Sern The following changes since commit d07bc7ba4ff00ddcd77db1026a63c327b81a35d8: meta: crystalforest: included USB HID configuration (2014-05-12 16:47:35 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/romley-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9/romley-common-meta Sreeju Selvaraj (4): meta: romley: removed using of common-pc-64.scc meta: romley: added power management meta: romley: included USB HID Configuration meta: romley: included RTC configuration Sreeju Slevaraj (1): mei.cfg: configure Intel MEI driver as module meta/cfg/kernel-cache/bsp/romley/romley-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/romley/romley-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/romley/romley.cfg|4 meta/cfg/kernel-cache/bsp/romley/romley.scc|3 +++ meta/cfg/kernel-cache/features/amt/mei/mei.cfg |2 +- 5 files changed, 9 insertions(+), 4 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/5] meta: romley: removed using of common-pc-64.scc
On 5/15/2014 12:22 PM, wei.sern.c...@intel.com wrote: From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Removed using of bsp/common-pc-64/common-pc-64.scc from romley-preempt-rt.scc and romley-standard.scc Added ktypes/standard/standard.scc for romley-standard.scc This is because we are migrating the BSP to use intel-common. Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com Acked-By: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/romley/romley-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/romley/romley-standard.scc |3 +-- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/romley/romley-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/romley/romley-preempt-rt.scc index 1ecdbbc..ad0a5e7 100644 --- a/meta/cfg/kernel-cache/bsp/romley/romley-preempt-rt.scc +++ b/meta/cfg/kernel-cache/bsp/romley/romley-preempt-rt.scc @@ -4,7 +4,6 @@ define KARCH x86_64 # no new branch required, re-use the ktypes/preempt-rt/preempt-rt.scc branch include ktypes/preempt-rt/preempt-rt.scc -include bsp/common-pc-64/common-pc-64.scc include romley.scc # default policy for preempt-rt kernels diff --git a/meta/cfg/kernel-cache/bsp/romley/romley-standard.scc b/meta/cfg/kernel-cache/bsp/romley/romley-standard.scc index 113ac8c..fcf4a99 100644 --- a/meta/cfg/kernel-cache/bsp/romley/romley-standard.scc +++ b/meta/cfg/kernel-cache/bsp/romley/romley-standard.scc @@ -2,7 +2,6 @@ define KMACHINE romley define KTYPE standard define KARCH x86_64 -include bsp/common-pc-64/common-pc-64-standard.scc -branch romley +include ktypes/standard/standard.scc include romley.scc -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 2/5] meta: romley: added power management
On 5/15/2014 12:22 PM, wei.sern.c...@intel.com wrote: From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Since migrating this BSP to use intel-common, we need to add configuration required for power management Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com Acked-By: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/romley/romley.scc |2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/cfg/kernel-cache/bsp/romley/romley.scc b/meta/cfg/kernel-cache/bsp/romley/romley.scc index c4d1c4f..9967407 100644 --- a/meta/cfg/kernel-cache/bsp/romley/romley.scc +++ b/meta/cfg/kernel-cache/bsp/romley/romley.scc @@ -8,6 +8,8 @@ include features/hugetlb/hugetlb.scc include features/ixgbe/ixgbe.scc include features/igb/igb.scc +# generic power management +include features/power/intel.scc include features/latencytop/latencytop.scc include features/profiling/profiling.scc -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 4/5] meta: romley: included RTC configuration
On 5/15/2014 12:22 PM, wei.sern.c...@intel.com wrote: From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Since migrating this BSP to use intel-common, we need to add RTC configuration to enable real time clock. Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com Acked-By: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/romley/romley.scc |1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/bsp/romley/romley.scc b/meta/cfg/kernel-cache/bsp/romley/romley.scc index 9967407..3020fd8 100644 --- a/meta/cfg/kernel-cache/bsp/romley/romley.scc +++ b/meta/cfg/kernel-cache/bsp/romley/romley.scc @@ -11,6 +11,7 @@ include features/igb/igb.scc # generic power management include features/power/intel.scc +include cfg/timer/rtc.scc include features/latencytop/latencytop.scc include features/profiling/profiling.scc -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 3/5] meta: romley: included USB HID Configuration
On 5/15/2014 12:22 PM, wei.sern.c...@intel.com wrote: From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Since migrating this BSP to use intel-common, we need to add the configuration required to enable USB HID Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com Acked-By: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/romley/romley.cfg |4 1 file changed, 4 insertions(+) diff --git a/meta/cfg/kernel-cache/bsp/romley/romley.cfg b/meta/cfg/kernel-cache/bsp/romley/romley.cfg index 28f6d71..3b5a7b9 100644 --- a/meta/cfg/kernel-cache/bsp/romley/romley.cfg +++ b/meta/cfg/kernel-cache/bsp/romley/romley.cfg @@ -59,3 +59,7 @@ CONFIG_BLK_DEV_INITRD=y CONFIG_RD_GZIP=y CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_ISO8859_1=y + +# USB HID Support +CONFIG_USB_HID=y +CONFIG_USB_HIDDEV=y -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 5/5] mei.cfg: configure Intel MEI driver as module
On 5/15/2014 12:22 PM, wei.sern.c...@intel.com wrote: From: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Changing the flag of this CONFIG_INTEL_MEI_ME from built-in to as module driver. As not all BIOS comes ready with AMT/MEI firmware. Signed-off-by: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com --- meta/cfg/kernel-cache/features/amt/mei/mei.cfg |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg index 313084b..3088128 100644 --- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg +++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg @@ -1,4 +1,4 @@ CONFIG_STAGING=y CONFIG_WATCHDOG_CORE=y CONFIG_INTEL_MEI=y The CONFIG_INTEL_MEI also need to be converted to module. Thanks, Nitin -CONFIG_INTEL_MEI_ME=y +CONFIG_INTEL_MEI_ME=m -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] pruning of unused branches from linux-yocto-3.14 kernel repository
Hi Bruce, As most of the BSPs from meta-intel layer are using the standard/base for KBRANCH, these kernel branches from the linux-yocto-3.14 repository are not needed anymore, and can be deleted to reduce the branch count. Darren, Tom, Do you see any of these branches used anywhere else? standard/common-pc-64/chiefriver standard/common-pc-64/crystalforest standard/common-pc-64/jasperforest standard/common-pc-64/mohonpeak standard/common-pc-64/rangeley standard/common-pc-64/romley standard/common-pc-64/sugarbay standard/common-pc/atom-pc standard/crownbay standard/emenlow standard/fri2 standard/preempt-rt/base standard/sys940x standard/tiny/fri2 Bruce, If there is no objection you can proceed with deleting of these branches from the L-Y v3.14 kernel repository. Thanks, Nitin -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] pruning of unused branches from linux-yocto-3.14 kernel repository
On 5/13/2014 2:54 PM, Bruce Ashfield wrote: On 14-05-13 01:06 PM, Kamble, Nitin A wrote: Hi Bruce, As most of the BSPs from meta-intel layer are using the standard/base for KBRANCH, these kernel branches from the linux-yocto-3.14 repository are not needed anymore, and can be deleted to reduce the branch count. I'll delete the old intel BSP branches, but as I just replied, -rt/base will stay. Bruce Thanks Bruce, Nitin Darren, Tom, Do you see any of these branches used anywhere else? standard/common-pc-64/chiefriver standard/common-pc-64/crystalforest standard/common-pc-64/jasperforest standard/common-pc-64/mohonpeak standard/common-pc-64/rangeley standard/common-pc-64/romley standard/common-pc-64/sugarbay standard/common-pc/atom-pc standard/crownbay standard/emenlow standard/fri2 standard/preempt-rt/base standard/sys940x standard/tiny/fri2 Bruce, If there is no objection you can proceed with deleting of these branches from the L-Y v3.14 kernel repository. Thanks, Nitin -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration
On 5/12/2014 3:20 PM, wei.sern.c...@intel.com wrote: From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from haswell-wc,crystalforest and mohonpeak. 2. Start using ktypes/standard/standard.scc for meta-ISG platforms. 3. Add back RTC configuration for crystalforest after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for crystalforest after changing from common-pc-64.scc to standard.scc. All the commits in this pull requests are well contained, and should not affect other BSPs. Still the common kernel may get affected, and other BSPs using the common kernel need to validated these changes. Wei Sern, Have you done any validation with other BSPs using the same kernel? Nitin Please help to pull this patch into linux-yocto-3.10:meta branch. Thanks. Regards, Chan Wei Sern The following changes since commit 617c6158c3d5b931f0d6131e0b0a7b374c792599: mei.cfg: enable Intel chipsets (2014-05-05 09:46:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/intel-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9/intel-common-meta Chan Wei Sern (2): meta: haswell-wc: removed using of common-pc-64.scc meta: mohonpeak: removed using of common-pc-64.scc Sreeju Slevaraj (3): meta: crystalforest: removed using of common-pc-64.scc meta: crystalforest: included RTC configuration meta: crystalforest: included USB HID configuration .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc|2 +- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc|1 - 7 files changed, 8 insertions(+), 6 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration
On 5/12/2014 9:05 AM, Kamble, Nitin A wrote: On 5/12/2014 3:20 PM, wei.sern.c...@intel.com wrote: From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from haswell-wc,crystalforest and mohonpeak. 2. Start using ktypes/standard/standard.scc for meta-ISG platforms. 3. Add back RTC configuration for crystalforest after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for crystalforest after changing from common-pc-64.scc to standard.scc. All the commits in this pull requests are well contained, and should not affect other BSPs. Still the common kernel may get affected, and other BSPs using the common kernel need to validated these changes. Wei Sern, Have you done any validation with other BSPs using the same kernel? The somewhat disruption changes here are for v3.10 kernel for intel-corei7-64 BSP, and we do not have any 64 bit non-ISG BSP in meta-intel using the v3.10 kernel as default. so I am not much nervous about these changes to common kernel now. For all the commits from the pull request: Acked-By: Nitin A Kamble nitin.a.kam...@intel.com Chan, Can you mention the kernel repository version in the pull request next time? This time, it was not clear weather these commits were for v3.10 kernel repo or v3.14 kernel repo. Thanks, Nitin Nitin Please help to pull this patch into linux-yocto-3.10:meta branch. Thanks. Regards, Chan Wei Sern The following changes since commit 617c6158c3d5b931f0d6131e0b0a7b374c792599: mei.cfg: enable Intel chipsets (2014-05-05 09:46:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/intel-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9/intel-common-meta Chan Wei Sern (2): meta: haswell-wc: removed using of common-pc-64.scc meta: mohonpeak: removed using of common-pc-64.scc Sreeju Slevaraj (3): meta: crystalforest: removed using of common-pc-64.scc meta: crystalforest: included RTC configuration meta: crystalforest: included USB HID configuration .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc |2 +- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc |1 - 7 files changed, 8 insertions(+), 6 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/1] meta: enable USB features for Mohonpeak
On 5/9/2014 5:09 AM, rebecca.swee.fun.ch...@intel.com wrote: From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com Added USB host controller driver support for Mohonpeak. This also enable live bootable image to be able to boot through USB devices. Signed-off-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com Acked-By: Nitin A Kamble nitin.a.kam...@intel.com Hi Bruce, If you can pull this in fast, this can be part of the 1.6 meta-intel release. Thanks, Nitin --- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak.scc | 13 + 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak.scc b/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak.scc index a4b6d83..dff0a89 100644 --- a/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak.scc +++ b/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak.scc @@ -7,10 +7,15 @@ include features/power/intel.scc include features/ixgbe/ixgbe.scc include features/igb/igb.scc -# required for Intel DPDK Support +include features/usb/ehci-hcd.scc +include features/usb/xhci-hcd.scc +include features/usb/uhci-hcd.scc +include features/usb/ohci-hcd.scc + +# These features are required for Intel DPDK Support include features/intel-dpdk/intel-dpdk.scc -#These features are required for Intel QAT Software +# These features are required for Intel QAT Software include features/pci-iov/pci-iov.scc include features/pci/pci.scc include features/ciphers/ciphers.scc @@ -18,8 +23,8 @@ include features/crypto/crypto.scc include cfg/efi.scc -#Add smp support +# Add smp support include cfg/smp.scc -#Enable GCC inlining +# Enable GCC inlining include features/inline/inline.scc -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/1] mei.cfg: enable Intel chipsets
-Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Monday, May 05, 2014 6:38 AM To: Kamble, Nitin A; Hart, Darren; linux-yocto@yoctoproject.org Subject: Re: [PATCH 1/1] mei.cfg: enable Intel chipsets On 14-05-02 08:01 PM, Kamble, Nitin A wrote: On 4/25/2014 8:51 AM, Hart, Darren wrote: On 4/24/14, 18:42, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Enable Intel Chipsets in the AMT/MEI driver. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Acked-by: Darren Hart dvh...@linux.intel.com Hi Bruce, Can you pull this fix in the v3.10 kernel repository as well? No problem. I'm doing some -stable updates and will put this on top of them. Thanks Bruce, Let me know when you pull the commit in, I will be firing a build with that. Nitin Cheers, Bruce Thanks, Nitin --- meta/cfg/kernel-cache/features/amt/mei/mei.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg index c1c2ace..313084b 100644 --- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg +++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg @@ -1,3 +1,4 @@ CONFIG_STAGING=y CONFIG_WATCHDOG_CORE=y CONFIG_INTEL_MEI=y +CONFIG_INTEL_MEI_ME=y -- 1.8.1.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/1] mei.cfg: enable Intel chipsets
On 4/25/2014 8:51 AM, Hart, Darren wrote: On 4/24/14, 18:42, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Enable Intel Chipsets in the AMT/MEI driver. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Acked-by: Darren Hart dvh...@linux.intel.com Hi Bruce, Can you pull this fix in the v3.10 kernel repository as well? Thanks, Nitin --- meta/cfg/kernel-cache/features/amt/mei/mei.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg index c1c2ace..313084b 100644 --- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg +++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg @@ -1,3 +1,4 @@ CONFIG_STAGING=y CONFIG_WATCHDOG_CORE=y CONFIG_INTEL_MEI=y +CONFIG_INTEL_MEI_ME=y -- 1.8.1.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/1] meta: smp.scc: increase default NR_CPUS to 64
On 4/10/2014 4:20 AM, boon.leong@intel.com wrote: From: Ong Boon Leong boon.leong@intel.com Change CONFIG_NR_CPUS from 8 to 64 so that platform with processors count more than 8 will be all activited. Acked-By: Nitin A Kamble nitin.a.kam...@intel.com Signed-off-by: Ong Boon Leong boon.leong@intel.com --- meta/cfg/kernel-cache/cfg/smp.cfg |3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/cfg/kernel-cache/cfg/smp.cfg b/meta/cfg/kernel-cache/cfg/smp.cfg index f53b969..2204774 100644 --- a/meta/cfg/kernel-cache/cfg/smp.cfg +++ b/meta/cfg/kernel-cache/cfg/smp.cfg @@ -1,2 +1,5 @@ CONFIG_SMP=y CONFIG_SCHED_SMT=y +# Increase default NR_CPUS from 8 to 64 so that platform with +# more than 8 processors can be all activated at boot time +CONFIG_NR_CPUS=64 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 10/29] usb: dwc3: pci: Enable/disable ulpi phy refclk
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote:
From: Maurice Petallo mauricex.r.peta...@intel.com
Due to power saving purpose, BIOS disabled ulpi phy refclk by default.
Hence, the refclk will only be enabled during device/driver probing.
and disabled during driver removal.
If this commit is not already pushed upstream, I would suggest to
improve the wording
of the commit message here. I will replace the commit message with
something like this.
For the purpose of saving power, BIOS has disabled ulpi phy refclk by
default.
Hence, for the conservation of power, the refclk is enabled only at
the time of
device/driver probing, and is disabled at the time of of driver removal.
Nitin
Signed-off-by: Maurice Petallo mauricex.r.peta...@intel.com
Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com
---
drivers/usb/dwc3/dwc3-pci.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/drivers/usb/dwc3/dwc3-pci.c b/drivers/usb/dwc3/dwc3-pci.c
index 2357c4e..4ebe49a 100644
--- a/drivers/usb/dwc3/dwc3-pci.c
+++ b/drivers/usb/dwc3/dwc3-pci.c
@@ -51,6 +51,10 @@
#define PCI_DEVICE_ID_INTEL_BYT 0x0f37
#define PCI_DEVICE_ID_INTEL_MRFLD 0x119e
+#define DWC3_PCI_GEN_REGRW1 0xa0
+#define DWC3_PCI_GEN_REGRW1_REFCLK_EN(n) (n 0xfffd)
+#define DWC3_PCI_GEN_REGRW1_REFCLK_DIS(n) (n | 0x02)
+
struct dwc3_pci {
struct device *dev;
struct platform_device *dwc3;
@@ -112,6 +116,19 @@ err1:
return ret;
}
+static void dwc3_pci_ulpiphy_refclk(struct pci_dev *pci, int enable)
+{
+ u32 val;
+
+ pci_read_config_dword(pci, DWC3_PCI_GEN_REGRW1, val);
+ if (enable)
+ val = DWC3_PCI_GEN_REGRW1_REFCLK_EN(val);
+ else
+ val = DWC3_PCI_GEN_REGRW1_REFCLK_DIS(val);
+
+ pci_write_config_dword(pci, DWC3_PCI_GEN_REGRW1, val);
+}
+
static int dwc3_pci_probe(struct pci_dev *pci,
const struct pci_device_id *id)
{
@@ -183,6 +200,9 @@ static int dwc3_pci_probe(struct pci_dev *pci,
goto err3;
}
+ /* enable ulpi phy refclk */
+ dwc3_pci_ulpiphy_refclk(pci, 1);
+
return 0;
err3:
@@ -198,6 +218,9 @@ static void dwc3_pci_remove(struct pci_dev *pci)
{
struct dwc3_pci *glue = pci_get_drvdata(pci);
+ /* disable ulpi phy refclk */
+ dwc3_pci_ulpiphy_refclk(pci, 0);
+
platform_device_unregister(glue-dwc3);
platform_device_unregister(glue-usb2_phy);
platform_device_unregister(glue-usb3_phy);
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 13/29] i2c: designware-pcidrv: Option to set custom HCNT, LCNT and SDA value
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote:
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Provide option to set the HCNT, LCNT and SDA if the target values are known
ahead. Instead of depends on formula to calculate the HCNT and LCNT.
If it is not already pushed upstream, I will reword this commit message too.
I will reword it to something like this:
Provide options to set the HCNT, LCNT and SDA values, if the target
values are known
ahead of time. This will make the boot process more efficient by
avoiding calculation
of the HCNT and LCNT values at runtime.
Nitin
Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com
Signed-off-by: Maurice Petallo mauricex.r.peta...@intel.com
---
drivers/i2c/busses/i2c-designware-pcidrv.c | 55
1 file changed, 55 insertions(+)
diff --git a/drivers/i2c/busses/i2c-designware-pcidrv.c
b/drivers/i2c/busses/i2c-designware-pcidrv.c
index 3599a6b..4f4398f 100644
--- a/drivers/i2c/busses/i2c-designware-pcidrv.c
+++ b/drivers/i2c/busses/i2c-designware-pcidrv.c
@@ -70,6 +70,12 @@ struct dw_pci_controller {
u32 tx_fifo_depth;
u32 rx_fifo_depth;
u32 clk_khz;
+ u32 ss_hcnt;
+ u32 ss_lcnt;
+ u32 fs_hcnt;
+ u32 fs_lcnt;
+ u32 ss_sda;
+ u32 fs_sda;
};
#define INTEL_MID_STD_CFG (DW_IC_CON_MASTER | \
@@ -150,6 +156,12 @@ static struct dw_pci_controller dw_pci_controllers[] = {
.tx_fifo_depth = 32,
.rx_fifo_depth = 32,
.clk_khz = 10,
+ .ss_hcnt= 0x200,
+ .ss_lcnt= 0x200,
+ .fs_hcnt= 0x55,
+ .fs_lcnt= 0x99,
+ .ss_sda = 0x6,
+ .fs_sda = 0x6,
},
[byt_1] = {
.bus_num = 1,
@@ -157,6 +169,12 @@ static struct dw_pci_controller dw_pci_controllers[] = {
.tx_fifo_depth = 32,
.rx_fifo_depth = 32,
.clk_khz = 10,
+ .ss_hcnt= 0x200,
+ .ss_lcnt= 0x200,
+ .fs_hcnt= 0x55,
+ .fs_lcnt= 0x99,
+ .ss_sda = 0x6,
+ .fs_sda = 0x6,
},
[byt_2] = {
.bus_num = 2,
@@ -164,6 +182,12 @@ static struct dw_pci_controller dw_pci_controllers[] = {
.tx_fifo_depth = 32,
.rx_fifo_depth = 32,
.clk_khz = 10,
+ .ss_hcnt= 0x200,
+ .ss_lcnt= 0x200,
+ .fs_hcnt= 0x55,
+ .fs_lcnt= 0x99,
+ .ss_sda = 0x6,
+ .fs_sda = 0x6,
},
[byt_3] = {
.bus_num = 3,
@@ -171,6 +195,12 @@ static struct dw_pci_controller dw_pci_controllers[] = {
.tx_fifo_depth = 32,
.rx_fifo_depth = 32,
.clk_khz = 10,
+ .ss_hcnt= 0x200,
+ .ss_lcnt= 0x200,
+ .fs_hcnt= 0x55,
+ .fs_lcnt= 0x99,
+ .ss_sda = 0x6,
+ .fs_sda = 0x6,
},
[byt_4] = {
.bus_num = 4,
@@ -178,6 +208,12 @@ static struct dw_pci_controller dw_pci_controllers[] = {
.tx_fifo_depth = 32,
.rx_fifo_depth = 32,
.clk_khz = 10,
+ .ss_hcnt= 0x200,
+ .ss_lcnt= 0x200,
+ .fs_hcnt= 0x55,
+ .fs_lcnt= 0x99,
+ .ss_sda = 0x6,
+ .fs_sda = 0x6,
},
[byt_5] = {
.bus_num = 5,
@@ -185,6 +221,12 @@ static struct dw_pci_controller dw_pci_controllers[] = {
.tx_fifo_depth = 32,
.rx_fifo_depth = 32,
.clk_khz = 10,
+ .ss_hcnt= 0x200,
+ .ss_lcnt= 0x200,
+ .fs_hcnt= 0x55,
+ .fs_lcnt= 0x99,
+ .ss_sda = 0x6,
+ .fs_sda = 0x6,
},
[byt_6] = {
.bus_num = 6,
@@ -192,6 +234,12 @@ static struct dw_pci_controller dw_pci_controllers[] = {
.tx_fifo_depth = 32,
.rx_fifo_depth = 32,
.clk_khz = 10,
+ .ss_hcnt= 0x200,
+ .ss_lcnt= 0x200,
+ .fs_hcnt= 0x55,
+ .fs_lcnt= 0x99,
+ .ss_sda = 0x6,
+ .fs_sda = 0x6,
},
};
static struct i2c_algorithm i2c_dw_algo = {
@@ -315,7 +363,14 @@ static int i2c_dw_pci_probe(struct pci_dev *pdev,
I2C_FUNC_SMBUS_BYTE_DATA |
Re: [linux-yocto] [PATCH 14/29] spi/pxa2xx-pci: Add support for Intel BYT SPI
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote:
From: Chew, Chiau Ee chiau.ee.c...@intel.com
The pxa2xx pci glue layer only support CE4100 SPI port
by default. To add BYT SPI port support, we make it a
generic PCI glue layer by renaming ce4100_xxx to
pxa2xx_spi_xxx.
This commit is created in reference to Mika's commit
during kernel-3.5 development, as below:
spi/pxa2xx-pci: convert to use pxa2xx-spi core
spi/pxa2xx-pci: add support for different PCI port types
spi/pxa2xx-pci: add support for ValleyView2 SPI
For upstreaming keeping commits small and concise helps a lot.
As a suggestion, for the upstreaming effort this commit can be broken
down into these 3 separate commits again.
Nitin
Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com
Signed-off-by: Maurice Petallo mauricex.r.peta...@intel.com
---
drivers/spi/Kconfig |5 ++-
drivers/spi/spi-pxa2xx-pci.c | 85 ++
2 files changed, 74 insertions(+), 16 deletions(-)
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 92775c5..f3fecc4 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -337,7 +337,10 @@ config SPI_PXA2XX
additional documentation can be found a Documentation/spi/pxa2xx.
config SPI_PXA2XX_PCI
- def_tristate SPI_PXA2XX PCI
+ tristate PCI glue for PXA2xx SSP SPI master
+ depends on SPI_PXA2XX PCI
+ help
+ This enables using PXA2xx SPI controller via PCI interface.
config SPI_RSPI
tristate Renesas RSPI controller
diff --git a/drivers/spi/spi-pxa2xx-pci.c b/drivers/spi/spi-pxa2xx-pci.c
index 74bc187..974d4fe 100644
--- a/drivers/spi/spi-pxa2xx-pci.c
+++ b/drivers/spi/spi-pxa2xx-pci.c
@@ -7,10 +7,48 @@
#include linux/of_device.h
#include linux/module.h
#include linux/spi/pxa2xx_spi.h
+#include linux/clk.h
-static int ce4100_spi_probe(struct pci_dev *dev,
+enum {
+ PORT_CE4100,
+ PORT_BYT,
+};
+
+struct pxa2xx_spi_pci_config {
+ enum pxa_ssp_type type;
+ int num_cs;
+ int bus_num;
+ int tx_slave_id;
+ int tx_chan_id;
+ int rx_slave_id;
+ int rx_chan_id;
+};
+
+static struct pxa2xx_spi_pci_config spi_pci_configs[] = {
+ [PORT_CE4100] = {
+ .type = PXA25x_SSP,
+ .num_cs = -1,
+ .bus_num = -1,
+ .tx_slave_id = -1,
+ .tx_chan_id = -1,
+ .rx_slave_id = -1,
+ .rx_chan_id = -1,
+ },
+ [PORT_BYT] = {
+ .type = LPSS_SSP,
+ .num_cs = 1,
+ .bus_num = 0,
+ .tx_slave_id = 0,
+ .tx_chan_id = 0,
+ .rx_slave_id = 1,
+ .rx_chan_id = 1,
+ },
+};
+
+static int pxa2xx_spi_probe(struct pci_dev *dev,
const struct pci_device_id *ent)
{
+ struct pxa2xx_spi_pci_config *c;
struct platform_device_info pi;
int ret;
struct platform_device *pdev;
@@ -25,8 +63,16 @@ static int ce4100_spi_probe(struct pci_dev *dev,
if (ret)
return ret;
+
+ c = spi_pci_configs[ent-driver_data];
+
memset(spi_pdata, 0, sizeof(spi_pdata));
- spi_pdata.num_chipselect = dev-devfn;
+ spi_pdata.num_chipselect = (c-num_cs = 0) ? c-num_cs : dev-devfn;
+ spi_pdata.tx_slave_id = c-tx_slave_id;
+ spi_pdata.tx_chan_id = c-tx_chan_id;
+ spi_pdata.rx_slave_id = c-rx_slave_id;
+ spi_pdata.rx_chan_id = c-rx_chan_id;
+ spi_pdata.enable_dma = c-rx_slave_id = 0 c-tx_slave_id = 0;
ssp = spi_pdata.ssp;
ssp-phys_base = pci_resource_start(dev, 0);
@@ -35,9 +81,15 @@ static int ce4100_spi_probe(struct pci_dev *dev,
dev_err(dev-dev, failed to ioremap() registers\n);
return -EIO;
}
+ ssp-clk = devm_clk_get(dev-dev, NULL);
+ if (IS_ERR(ssp-clk)) {
+ dev_err(dev-dev, failed to get clock\n);
+ return PTR_ERR(ssp-clk);
+ }
+
ssp-irq = dev-irq;
- ssp-port_id = dev-devfn;
- ssp-type = PXA25x_SSP;
+ ssp-port_id = (c-bus_num = 0) ? c-bus_num : dev-devfn;
+ ssp-type = c-type;
memset(pi, 0, sizeof(pi));
pi.parent = dev-dev;
@@ -55,28 +107,31 @@ static int ce4100_spi_probe(struct pci_dev *dev,
return 0;
}
-static void ce4100_spi_remove(struct pci_dev *dev)
+static void pxa2xx_spi_remove(struct pci_dev *dev)
{
struct platform_device *pdev = pci_get_drvdata(dev);
platform_device_unregister(pdev);
}
-static DEFINE_PCI_DEVICE_TABLE(ce4100_spi_devices) = {
- { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x2e6a) },
+static DEFINE_PCI_DEVICE_TABLE(pxa2xx_spi_devices) = {
+ { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x2e6a),
+ .driver_data = PORT_CE4100 },
+ { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x0f0e),
+ .driver_data = PORT_BYT },
{ },
};
-MODULE_DEVICE_TABLE(pci,
Re: [linux-yocto] [PATCH 15/29] spi/pxa2xx: Fix BYT ACPI mode SPI DMA transfer failure at low speeds
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote: From: Chew, Chiau Ee chiau.ee.c...@intel.com BYT ACPI mode SPI not read/writing correctly at low speeds using DMA mode. Fix the issue by changing DMA SRC_MSIZE and DEST_MSIZE of SPI FIFO side from 16 to 32. I think a bit of explanation is needed here, why changing the sizes from 16 to 32 fixes the issue. Also I will correct grammatical errors in the commit message. As these commits logs go in public tree, and stay there forever, it is important, to not leave any grammatical mistakes in the commit logs. Nitin Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com Signed-off-by: Maurice Petallo mauricex.r.peta...@intel.com --- drivers/spi/spi-pxa2xx-dma.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/spi-pxa2xx-dma.c b/drivers/spi/spi-pxa2xx-dma.c index 3c0b551..79515ed 100644 --- a/drivers/spi/spi-pxa2xx-dma.c +++ b/drivers/spi/spi-pxa2xx-dma.c @@ -385,7 +385,7 @@ int pxa2xx_spi_set_dma_burst_and_threshold(struct chip_data *chip, * otherwise we use the default. Also we use the default FIFO * thresholds for now. */ - *burst_code = chip_info ? chip_info-dma_burst_size : 16; + *burst_code = chip_info ? chip_info-dma_burst_size : 32; *threshold = SSCR1_RxTresh(RX_THRESH_DFLT) | SSCR1_TxTresh(TX_THRESH_DFLT); -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 18/29] pwm: add support for Intel Low Power Subsystem PWM
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote:
From: Mika Westerberg mika.westerb...@linux.intel.com
Add support for Intel Low Power I/O subsystem PWM controllers found on some
newer intel chipsets.
Signed-off-by: Mika Westerberg mika.westerb...@linux.intel.com
This patch is pulled from Mika's git tree previousy. The git
tree is no longer accessible now.
This git tree status information is not useful in the commit message.
You can include it
in the pull request email, and drop it from the commit message here.
Nitin
Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com
Signed-off-by: Maurice Petallo mauricex.r.peta...@intel.com
---
drivers/pwm/Kconfig| 10 +++
drivers/pwm/Makefile |1 +
drivers/pwm/pwm-lpss.c | 183
3 files changed, 194 insertions(+)
create mode 100644 drivers/pwm/pwm-lpss.c
diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig
index 14a9122..f2b0948 100644
--- a/drivers/pwm/Kconfig
+++ b/drivers/pwm/Kconfig
@@ -87,6 +87,16 @@ config PWM_LPC32XX
To compile this driver as a module, choose M here: the module
will be called pwm-lpc32xx.
+config PWM_LPSS
+ tristate Intel LPSS PWM support
+ depends on ACPI
+ help
+ Generic PWM framework driver for Intel Low Power Subsystem PWM
+ controller.
+
+ To compile this driver as a module, choose M here: the module
+ will be called pwm-lpio.
+
config PWM_MXS
tristate Freescale MXS PWM support
depends on ARCH_MXS OF
diff --git a/drivers/pwm/Makefile b/drivers/pwm/Makefile
index 5aa815f..6a5e723 100644
--- a/drivers/pwm/Makefile
+++ b/drivers/pwm/Makefile
@@ -5,6 +5,7 @@ obj-$(CONFIG_PWM_BFIN) += pwm-bfin.o
obj-$(CONFIG_PWM_IMX) += pwm-imx.o
obj-$(CONFIG_PWM_JZ4740) += pwm-jz4740.o
obj-$(CONFIG_PWM_LPC32XX) += pwm-lpc32xx.o
+obj-$(CONFIG_PWM_LPSS) += pwm-lpss.o
obj-$(CONFIG_PWM_MXS) += pwm-mxs.o
obj-$(CONFIG_PWM_PUV3)+= pwm-puv3.o
obj-$(CONFIG_PWM_PXA) += pwm-pxa.o
diff --git a/drivers/pwm/pwm-lpss.c b/drivers/pwm/pwm-lpss.c
new file mode 100644
index 000..fb3548c
--- /dev/null
+++ b/drivers/pwm/pwm-lpss.c
@@ -0,0 +1,183 @@
+/*
+ * Intel Low Power Subsystem PWM controller driver
+ *
+ * Copyright (C) 2013, Intel Corporation
+ * Author: Mika Westerberg mika.westerb...@linux.intel.com
+ *
+ * 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 linux/acpi.h
+#include linux/clk.h
+#include linux/device.h
+#include linux/kernel.h
+#include linux/module.h
+#include linux/pwm.h
+#include linux/platform_device.h
+
+#define PWM0x
+#define PWM_ENABLE BIT(31)
+#define PWM_SW_UPDATE BIT(30)
+#define PWM_BASE_UNIT_SHIFT8
+#define PWM_BASE_UNIT_MASK 0x0000
+#define PWM_ON_TIME_DIV_MASK 0x00ff
+
+struct pwm_lpss_chip {
+ struct pwm_chip chip;
+ void __iomem *regs;
+ struct clk *clk;
+};
+
+static inline struct pwm_lpss_chip *to_lpwm(struct pwm_chip *chip)
+{
+ return container_of(chip, struct pwm_lpss_chip, chip);
+}
+
+static void pwm_lpss_set_state(struct pwm_lpss_chip *lpwm, bool enable)
+{
+ u32 ctrl;
+
+ ctrl = readl(lpwm-regs + PWM);
+ if (enable)
+ ctrl |= PWM_ENABLE;
+ else
+ ctrl = ~PWM_ENABLE;
+ writel(ctrl, lpwm-regs + PWM);
+}
+
+static int pwm_lpss_config(struct pwm_chip *chip, struct pwm_device *pwm,
+ int duty_ns, int period_ns)
+{
+ struct pwm_lpss_chip *lpwm = to_lpwm(chip);
+ u8 base_unit_hi, base_unit_lo, on_time_div;
+ unsigned long c = clk_get_rate(lpwm-clk);
+ unsigned long hz, cycle_cnt;
+ u32 ctrl;
+
+ hz = 10UL / period_ns;
+
+ /*
+* There is no duty cycle resolution if base_unit value is higher
+* than 128.
+*/
+ base_unit_hi = (hz * 256) / c;
+ if (base_unit_hi 128)
+ return -EINVAL;
+
+ base_unit_lo = (hz * 65536) / c;
+ cycle_cnt = base_unit_hi ? 256 / base_unit_hi : 256;
+
+ if (duty_ns = 0)
+ duty_ns = 1;
+
+ on_time_div = cycle_cnt / (period_ns / duty_ns);
+
+ ctrl = readl(lpwm-regs + PWM);
+ ctrl = ~(PWM_BASE_UNIT_MASK | PWM_ON_TIME_DIV_MASK);
+ ctrl |= (base_unit_hi | base_unit_lo) PWM_BASE_UNIT_SHIFT;
+ ctrl |= on_time_div;
+ /* request PWM to update on next cycle */
+ ctrl |= PWM_SW_UPDATE;
+ writel(ctrl, lpwm-regs + PWM);
+
+ return 0;
+}
+
+static int pwm_lpss_enable(struct pwm_chip *chip, struct pwm_device *pwm)
+{
+ struct pwm_lpss_chip *lpwm = to_lpwm(chip);
+
+ clk_prepare_enable(lpwm-clk);
+ pwm_lpss_set_state(lpwm, true);
+ return 0;
+}
+
+static void
Re: [linux-yocto] [PATCH 23/29] x86/byt: Fix device name string for clkdev registration
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote: From: Maurice Petallo mauricex.r.peta...@intel.com Use BYT DMA PCI domain:bus:slot.func identification as device name input during clkdev registration. Signed-off-by: Maurice Petallo mauricex.r.peta...@intel.com --- arch/x86/platform/byt/byt-board.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/platform/byt/byt-board.c b/arch/x86/platform/byt/byt-board.c index be4ed4d..e94a377 100644 --- a/arch/x86/platform/byt/byt-board.c +++ b/arch/x86/platform/byt/byt-board.c @@ -47,7 +47,7 @@ static int byt_clk_setup(void) if (IS_ERR(clk)) return PTR_ERR(clk); - clk_register_clkdev(clk, hclk, dw_dmac.0); + clk_register_clkdev(clk, hclk, :00:1e.0); Such kind of hard-coded constant addresses are not well received for upstreaming. Can this address instead be deduced at runtime? Nitin clk = clk_register_fixed_rate(NULL, spi_clk, lpss_clk, 0, 5000); if (IS_ERR(clk)) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 26/29] pinctrl-baytrail: unmap interrupt when free the gpio pin
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote: From: Chew, Kean Ho kean.ho.c...@intel.com In to_irq() callback, we create the hwirq to linux irq mapping for the requested GPIO pin. Hence, we unamp typo: unamp/unmap the mapping when the gpio pin is being released. Signed-off-by: Chew, Kean Ho kean.ho.c...@intel.com Signed-off-by: Chew, Chiau Ee chiau.ee.c...@intel.com Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com --- drivers/pinctrl/pinctrl-baytrail.c |3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/pinctrl/pinctrl-baytrail.c b/drivers/pinctrl/pinctrl-baytrail.c index c0ef8e2..554e279 100644 --- a/drivers/pinctrl/pinctrl-baytrail.c +++ b/drivers/pinctrl/pinctrl-baytrail.c @@ -177,11 +177,14 @@ static void byt_gpio_free(struct gpio_chip *chip, unsigned offset) struct byt_gpio *vg = to_byt_gpio(chip); void __iomem *reg = byt_gpio_reg(vg-chip, offset, BYT_CONF0_REG); u32 value; + unsigned int virq; /* clear interrupt triggering */ value = readl(reg); value = ~(BYT_TRIG_POS | BYT_TRIG_NEG | BYT_TRIG_LVL); writel(value, reg); + virq = irq_find_mapping(vg-domain, offset); + irq_dispose_mapping(virq); pm_runtime_put(vg-pdev-dev); } -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 29/29] i2c: i801: Enable BYT SMBUS support
On 4/7/2014 8:18 AM, rebecca.swee.fun.ch...@intel.com wrote:
From: Chang, Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
Add PCI ID of BYT SMBUS.
Signed-off-by: Chew, Kean Ho kean.ho.c...@intel.com
Signed-off-by: Maurice Petallo mauricex.r.peta...@intel.com
Signed-off-by: Chang, Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
---
drivers/i2c/busses/Makefile |2 +-
drivers/i2c/busses/i2c-i801.c |2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/Makefile b/drivers/i2c/busses/Makefile
index f35b079..5bbf680 100644
--- a/drivers/i2c/busses/Makefile
+++ b/drivers/i2c/busses/Makefile
@@ -12,7 +12,6 @@ obj-$(CONFIG_I2C_ALI15X3) += i2c-ali15x3.o
obj-$(CONFIG_I2C_AMD756) += i2c-amd756.o
obj-$(CONFIG_I2C_AMD756_S4882)+= i2c-amd756-s4882.o
obj-$(CONFIG_I2C_AMD8111) += i2c-amd8111.o
-obj-$(CONFIG_I2C_I801) += i2c-i801.o
obj-$(CONFIG_I2C_ISCH)+= i2c-isch.o
obj-$(CONFIG_I2C_ISMT)+= i2c-ismt.o
obj-$(CONFIG_I2C_NFORCE2) += i2c-nforce2.o
@@ -41,6 +40,7 @@ obj-$(CONFIG_I2C_DESIGNWARE_PLATFORM) +=
i2c-designware-platform.o
i2c-designware-platform-objs := i2c-designware-platdrv.o
obj-$(CONFIG_I2C_DESIGNWARE_PCI) += i2c-designware-pci.o
i2c-designware-pci-objs := i2c-designware-pcidrv.o
+obj-$(CONFIG_I2C_I801) += i2c-i801.o
Can you explain in the commit log, why this line is moved in the Makefile?
Nitin
obj-$(CONFIG_I2C_EG20T) += i2c-eg20t.o
obj-$(CONFIG_I2C_GPIO)+= i2c-gpio.o
obj-$(CONFIG_I2C_HIGHLANDER) += i2c-highlander.o
diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
index 8763b22..b667b2b 100644
--- a/drivers/i2c/busses/i2c-i801.c
+++ b/drivers/i2c/busses/i2c-i801.c
@@ -175,6 +175,7 @@
#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS1 0x8d7e
#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS2 0x8d7f
#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_SMBUS0x9c22
+#define PCI_DEVICE_ID_INTEL_BYT_SMBUS 0x0f12
struct i801_mux_config {
char *gpio_chip;
@@ -792,6 +793,7 @@ static DEFINE_PCI_DEVICE_TABLE(i801_ids) = {
{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801CA_3) },
{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801DB_3) },
{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801EB_3) },
+ { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BYT_SMBUS) },
{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ESB_4) },
{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_16) },
{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH7_17) },
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 00/29] Create new feature branch for Valley Island BSP
On 4/7/2014 8:17 AM, rebecca.swee.fun.ch...@intel.com wrote: From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com Hi all, Here is a request to create feature branch to host Valley Island PCI enumerated LPSS I/O device drivers. We expect the patch series to be removed over time. This will give us time to stage a working code while we are working on up-stream commits to mainline and eventually back-port them into LTS/LTSI. As per previous internal discussion, we think that feature branch is a right approach for ISG. This new branch is named: isg-1.0 with -1.0 suffix as the initial version of this feature branch. This feature branch was branched out from linux-yocto-3.10 standard/base at the commit: 3e0a296fae952d8d93eb0f96566bf6d4a978c8ee minnowboard-keys: Bind MinnowBoard buttons to arrow keys This branch was built tested to ensure no merge issues during build time. The PCI enumerated I/O drivers are sanity tested by checking dmesg, lspci -k and lsmod. Please help to create a new branch named isg-1.0 in linux-yocto-3.10 and pull the entire patch series into the feature branch. Thanks. Rebecca Hi Rebecca, I have sent my review feedback by email to many of the commits. The commits which did not get feedback from me, are already in good shape. Thanks, Nitin The following changes since commit 3e0a296fae952d8d93eb0f96566bf6d4a978c8ee: minnowboard-keys: Bind MinnowBoard buttons to arrow keys (2014-02-12 00:08:25 -0500) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib rebeccas/isg-1.0 http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=rebeccas/isg-1.0 Alan Stern (1): usb: gadget: don't fail when DMA isn't present Chang, Rebecca Swee Fun (1): i2c: i801: Enable BYT SMBUS support Chew, Chiau Ee (14): x86/Kconfig: add PCI dependency for CONFIG_X86_INTEL_LPSS x86/byt: enable board file for BYT LPSS PCI mode dma: dw: Fix Intel MID DMA driver and Designware DMA driver loading sequence dma: dw: Implement suspend/resume callbacks serial: 8250_dw: Added support for 1M, 2M, 3M and 4M exat baud rate i2c: designware-pci: Add support for Intel BayTrail LPSS I2C i2c: designware-pcidrv: Add 10-bit addressing mode functionality i2c: designware-pcidrv: Option to set custom HCNT, LCNT and SDA value spi/pxa2xx-pci: Add support for Intel BYT SPI spi/pxa2xx: Fix BYT ACPI mode SPI DMA transfer failure at low speeds sdhc: acpi: Fix SDCARD card detection failure pwm: lpss: Enable BYT PCI mode PWM pwm: lpss: Fix base_unit calculation ACPI / LPSS: Add BYT ACPI mode PWM Chew, Kean Ho (5): mmc: sdhci: Force BYT SDCARD host to run with SDR25 mode pinctrl-baytrail: add function mux checking in gpio pin request pinctrl-baytrail: unmap interrupt when free the gpio pin pinctrl-baytrail: enable platform device in the absent of ACPI enumeration pinctrl-baytrail: setup IOAPIC interrupt for GPIO clusters on non-ACPI system Felipe Balbi (1): usb: gadget: udc-core: move sysfs_notify() to a workqueue H Hartley Sweeten (1): pwm: Add sysfs interface Heikki Krogerus (2): serial: 8250: don't change the fifo trigger level when using dma serial: 8250_pci: add support for Intel BayTrail Maurice Petallo (3): usb: dwc3: pci: Enable/disable ulpi phy refclk x86/byt: Fix device name string for clkdev registration mmc: sdhci: Fix continuous warning prints in ISR if shared interrupt Mika Westerberg (1): pwm: add support for Intel Low Power Subsystem PWM Documentation/ABI/testing/sysfs-class-pwm | 79 +++ Documentation/pwm.txt | 37 +++ arch/x86/Kconfig | 11 +- arch/x86/platform/Makefile |3 + arch/x86/platform/byt/Makefile |1 + arch/x86/platform/byt/byt-board.c | 84 +++ drivers/acpi/acpi_lpss.c | 11 + drivers/dma/Makefile |2 +- drivers/dma/dw/pci.c | 36 +++ drivers/i2c/busses/Makefile|2 +- drivers/i2c/busses/i2c-designware-pcidrv.c | 126 +- drivers/i2c/busses/i2c-i801.c |2 + drivers/mmc/host/sdhci-acpi.c |7 +- drivers/mmc/host/sdhci-pci.c |3 +- drivers/mmc/host/sdhci.c | 17 +- drivers/pinctrl/Kconfig| 19 +- drivers/pinctrl/Makefile |1 + drivers/pinctrl/pinctrl-baytrail-dev.c | 159 + drivers/pinctrl/pinctrl-baytrail.c | 76 +- drivers/pwm/Kconfig| 21 ++ drivers/pwm/Makefile |3 + drivers/pwm/core.c | 25 +- drivers/pwm/pwm-lpss-pci.c | 118 ++ drivers/pwm/pwm-lpss.c | 186 +++ drivers/pwm/pwm-lpss.h | 19 ++
Re: [linux-yocto] [PATCH 0/1] a fix for v3.10 LTSI branch
-Original Message- From: Hart, Darren Sent: Monday, March 31, 2014 1:34 PM To: Kamble, Nitin A; Ashfield, Bruce (Wind River); linux- yo...@yoctoproject.org Subject: Re: [PATCH 0/1] a fix for v3.10 LTSI branch On 3/31/14, 13:24, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com I was noticing emenlow BSP failing to boot since LTSI was integrated in the v3.10 kernel. After debugging I found out that kernel code was doing an invalid memory access, causing kernel panic. Here is the fix for the issue, which I am also pushing to the upstream v3.10 LTSI kernel repository. Is this a backport from mainline? If so, it needs the cherry-pick ID. If not, this needs to go upstream first and then back to 3.10 stable (which LTSI will pick up). If neither of these seems like the right approach to you - what did you have in mind and why? This is not a backport. But I am planning to send it to LTSI upstream. As you say this will be back ported, once it goes upstream in the LTSI repo. Nitin Thanks, -- Darren Hart Yocto Project - Linux Kernel Intel Open Source Technology Center -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/1] a fix for v3.10 LTSI branch
On 3/31/2014 2:01 PM, Hart, Darren wrote: On 3/31/14, 13:56, Kamble, Nitin A nitin.a.kam...@intel.com wrote: -Original Message- From: Hart, Darren Sent: Monday, March 31, 2014 1:34 PM To: Kamble, Nitin A; Ashfield, Bruce (Wind River); linux- yo...@yoctoproject.org Subject: Re: [PATCH 0/1] a fix for v3.10 LTSI branch On 3/31/14, 13:24, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com I was noticing emenlow BSP failing to boot since LTSI was integrated in the v3.10 kernel. After debugging I found out that kernel code was doing an invalid memory access, causing kernel panic. Here is the fix for the issue, which I am also pushing to the upstream v3.10 LTSI kernel repository. Is this a backport from mainline? If so, it needs the cherry-pick ID. If not, this needs to go upstream first and then back to 3.10 stable (which LTSI will pick up). If neither of these seems like the right approach to you - what did you have in mind and why? This is not a backport. But I am planning to send it to LTSI upstream. As you say this will be back ported, once it goes upstream in the LTSI repo. Please do not send it to LTSI. LTSI is not a development target. LTSI tracks stable and gets new features *from mainline* that stable cannot. Please send this to lkml with the stable line included (see the stable-kernel-rules.txt). This should get picked up into the LTSI release as a matter of course after it lands in 3.10 stable. Got it. I pulled the trigger for LTSI ML too fast then. I will post it on LKML for 3.10 stable now. Thanks for the clarification. Nitin -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH v2 12/17] media-platform: A feature for platform media devices
-Original Message- From: Hart, Darren Sent: Monday, December 09, 2013 8:32 AM To: Kamble, Nitin A Cc: bruce.ashfi...@windriver.com; linux-yocto@yoctoproject.org Subject: Re: [PATCH v2 12/17] media-platform: A feature for platform media devices On Fri, 2013-12-06 at 21:51 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Create a feature fragment for enabling platform media devices. This one seems like it might be incomplete. The first option enables a block of other options, but only DEINTERLACE was enabled of the entire block. This isn't Nitin's doing, it's just what was in the media.cfg blob I tossed over the over the wall to him. Hrm. I don't see any dependencies on DEINTERLACE from other drivers... but it is a generic deinterlacing driver for V4L... which seems to me to be something we would want in general... while the others, not so much. So... OK, I guess it's the right way to go... despite looking a bit odd. I had similar feeling while creating this fragment. I also tried to avoid creating this. Putting it in the media.cfg was not working well, because it was enabling some of the unwanted media drivers without asking. Thanks, Nitin Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Reviewed-by: Darren Hart dvh...@linux.intel.com --- meta/cfg/kernel-cache/features/media/media-platform.cfg | 5 + meta/cfg/kernel-cache/features/media/media-platform.scc | 6 ++ 2 files changed, 11 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/media-platform.cfg create mode 100644 meta/cfg/kernel-cache/features/media/media-platform.scc diff --git a/meta/cfg/kernel-cache/features/media/media-platform.cfg b/meta/cfg/kernel-cache/features/media/media-platform.cfg new file mode 100644 index 000..31b53bd --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media-platform.cfg @@ -0,0 +1,5 @@ +# +# Media Platform Configuration +# +CONFIG_V4L_MEM2MEM_DRIVERS=y +CONFIG_VIDEO_MEM2MEM_DEINTERLACE=m diff --git a/meta/cfg/kernel-cache/features/media/media-platform.scc b/meta/cfg/kernel-cache/features/media/media-platform.scc new file mode 100644 index 000..474406c --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media-platform.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Platform Media devices +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware media-platform.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 2/2] common-pc-64: add kernel CONFIG options for sugarbay platform
-Original Message- From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- boun...@yoctoproject.org] On Behalf Of Darren Hart Sent: Tuesday, September 24, 2013 12:21 PM To: Development list for the linux-yocto*.git Linux kernel repositories Subject: Re: [linux-yocto] [PATCH 2/2] common-pc-64: add kernel CONFIG options for sugarbay platform On Tue, 2013-09-24 at 18:23 +, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Add these Kernel driver config options for Sugarbay platform. - i915 graphics - 8250 serial port - usb webcam drivers - generic power management support to enable proper suspend/resume Fixes Bug: [YOCTO #5117] Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc | 13 + 1 file changed, 13 insertions(+) diff --git a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc index c841875..e98a254 100644 --- a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc +++ b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc @@ -13,3 +13,16 @@ include features/usb/touchscreen-composite.scc include features/intel-e1/intel-e100.scc include features/intel-e1/intel-e1.scc include features/scsi/cdrom.scc + +# generic power management +include features/power/intel.scc + +# serial port +include cfg/8250.scc + +# webcam +include features/usb/usb-uvcvideo +include features/media/v4l2 + Please use the explicit path (including the .scc) Updated the commit in the contrib branch to use the full path with .scc. Thanks, Nitin +# sugarbay graphics +include features/i915/i915.scc -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ 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] meta: add genericx86 BSP
-Original Message- From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- boun...@yoctoproject.org] On Behalf Of Bruce Ashfield Sent: Friday, September 13, 2013 9:56 AM To: Development list for the linux-yocto*.git Linux kernel repositories Subject: Re: [linux-yocto] [PATCH] meta: add genericx86 BSP On 13-09-13 12:03 PM, Darren Hart wrote: This is not being added, we're using common-pc. What is pending is my update to the common-pc and common-pc-64 BSPs which Paul G. provided some feedback for and I updated the branch which is ready to be pulled here: git://git.yoctoproject.org/linux-yocto-contrib dvhart/3.10/meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=dvhart /3.10/meta This should be all that is outstanding for genericx86/common-pc in linux-yocto currently. Aha. My misunderstanding, it got a bit muddy in the middle. As you can see in your inbox, I've merged these, pushed them out and sent the pull request for the SRCREV update. Darren, Does this impact other BSPs? Or in other words does this demand srcrev updates for other BSPs? Thanks, Nitin Bruce -- Darren On Fri, 2013-09-13 at 09:12 -0400, Bruce Ashfield wrote: ping again. I still haven't seen an updated, an reposted merge of this with common- pc. Did my mail client manage to drop it ? Bruce On Mon, Sep 9, 2013 at 2:06 PM, Bruce Ashfield bruce.ashfi...@gmail.com wrote: On Wed, Aug 21, 2013 at 4:17 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: On 13-08-21 01:33 PM, Darren Hart wrote: On Wed, 2013-08-21 at 17:57 +0100, Ross Burton wrote: This BSP aims at supporting a broad range of Intel platforms, from Atom up to Xeon. As such the kernel includes a range of drivers, and the corresponding machine configuration in meta-yocto-bsp includes a range of user-space drivers. Signed-off-by: Ross Burton ross.bur...@intel.com --- .../bsp/genericx86/genericx86-standard.scc | 28 1 file changed, 28 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/genericx86/genericx86-standard.scc diff --git a/meta/cfg/kernel-cache/bsp/genericx86/genericx86-standard.scc b/meta/cfg/kernel-cache/bsp/genericx86/genericx86-standard.scc new file mode 100644 index 000..94d8ca7 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/genericx86/genericx86- standard.sc +++ c @@ -0,0 +1,28 @@ +define KMACHINE genericx86 +define KTYPE standard +define KARCH i386 + +# TODO: long-term move away from common-pc? +include bsp/common-pc/common-pc-standard.scc +branch atom-pc + +include cfg/x86.scc +include cfg/boot-live.scc + +include features/power/intel.scc + +# Ideally all of these below would be modules instead of built-in. + +# common-pc brings in the other USB controllers include +features/usb/xhci-hcd.scc And should really bring this one in too... Agreed! + +# Intel ethernet, old and new Intel wireless. +include features/rfkill/rfkill.scc include +features/intel-e1/intel-e1.scc +include features/iwlwifi/iwlwifi.scc include +features/iwlegacy/iwlegacy.scc + +# Intel Gen and GMA500. common-pc provides Vesa framebuffer. +include features/i915/i915.scc +include features/drm-gma500/drm-gma500.scc +include features/drm-gma500/drm-gma3600.scc This is really a fairly small change. Any reason this shouldn't just be an update to common-pc? Is there a conceptual difference here? I'd like to see them just merge. They are both targeting a similar set of commodity hardware platforms. Sure, qemux86 will pick these up as well, but as qemu gains more functionality we can use more and more of the options. ping. Did we collectively slip on this ? I was just trying to debug a serial 8250 issue, and realized that none of the generic x86 parts have merged. Bruce Cheers, Bruce ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto -- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end ___ 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 3/3] emgd-1.18 fix build issues with v3.8 kernel
-Original Message-
From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto-
boun...@yoctoproject.org] On Behalf Of Bruce Ashfield
Sent: Wednesday, July 03, 2013 9:01 PM
To: Development list for the linux-yocto*.git Linux kernel repositories
Subject: Re: [linux-yocto] [PATCH 3/3] emgd-1.18 fix build issues with v3.8
kernel
On Tue, Jul 2, 2013 at 3:51 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble nitin.a.kam...@intel.com
These changes are done according to these existing commits in the v3.8
tree
b0071efe827f68cf173e1a8868b70618e9aca7d7
760285e7e7ab282c25b5e90816f7c47000557f4f
56550d94cbaeaa195cb98c95d012b301cbd65a8d
314e51b9851b4f4e8ab302243ff5a6fc6147f379
a69ac9ea85d87b57166a1c017c5019447b854a68
Can you tweak this header with short hashes and short logs ? That way on a
glance, we can get a feel for what you are adapting to ?
All of the changes look good to me. A resend of just a pull request with that
tweaked header and I'll get this merged.
Bruce
Hi Bruce,
The commit is tweaked as requested. I am not pushing the pull request again,
as these patches are huge.
So instead you can just pull from here:
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=nitin/emgd-1.18
Thanks,
Nitin
Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com
---
drivers/gpu/drm/emgd/emgd/drm/emgd_connector.c | 2 +-
drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c| 3 +--
drivers/gpu/drm/emgd/emgd/drm/emgd_fb.c | 10 +-
drivers/gpu/drm/emgd/emgd/drm/emgd_interface.c | 2 +-
drivers/gpu/drm/emgd/emgd/drm/emgd_mmap.c | 2 +-
drivers/gpu/drm/emgd/emgd/drm/emgd_test_pvrsrv.c| 2 +-
drivers/gpu/drm/emgd/pvr/services4/srvkm/env/linux/mmap.c | 2 +-
drivers/gpu/drm/emgd/pvr/services4/srvkm/env/linux/module.c | 2 +-
drivers/gpu/drm/emgd/pvr/services4/srvkm/env/linux/osfunc.c | 2 +-
9 files changed, 13 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/emgd/emgd/drm/emgd_connector.c
b/drivers/gpu/drm/emgd/emgd/drm/emgd_connector.c
index b62c2ca..6aa461a 100644
--- a/drivers/gpu/drm/emgd/emgd/drm/emgd_connector.c
+++ b/drivers/gpu/drm/emgd/emgd/drm/emgd_connector.c
@@ -299,7 +299,7 @@ static int emgd_connector_set_property(struct
drm_connector *connector,
/* Set the property value to the new one. This doesn't actually
change
* anything on the HW. */
- ret = drm_connector_property_set_value(connector, property,
value);
+ ret = drm_object_property_set_value(connector-base,
+ property, value);
if (ret) {
return ret;
}
diff --git a/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c
b/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c
index 58927c6..21f1c41 100755
--- a/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c
+++ b/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c
@@ -2372,7 +2372,7 @@ irqreturn_t emgd_driver_irq_handler(int irq,
void *arg) } /* emgd_driver_irq_handler() */
-static int __devinit emgd_pci_probe(struct pci_dev *pdev,
+static int emgd_pci_probe(struct pci_dev *pdev,
const struct pci_device_id *ent) {
if (PCI_FUNC(pdev-devfn)) {
@@ -2503,7 +2503,6 @@ static struct drm_driver driver = {
.irq_postinstall= emgd_driver_irq_postinstall,
.irq_uninstall = emgd_driver_irq_uninstall,
.irq_handler= emgd_driver_irq_handler,
- .reclaim_buffers= drm_core_reclaim_buffers,
#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,37)
.get_map_ofs= drm_core_get_map_ofs,
.get_reg_ofs= drm_core_get_reg_ofs,
diff --git a/drivers/gpu/drm/emgd/emgd/drm/emgd_fb.c
b/drivers/gpu/drm/emgd/emgd/drm/emgd_fb.c
index 8683477..6bd3a47 100644
--- a/drivers/gpu/drm/emgd/emgd/drm/emgd_fb.c
+++ b/drivers/gpu/drm/emgd/emgd/drm/emgd_fb.c
@@ -41,7 +41,7 @@
#include linux/module.h
#endif
#include drmP.h
-#include drm.h
+#include uapi/drm/drm.h
#include drm_crtc.h
#include drm_crtc_helper.h
#include drm_fb_helper.h
@@ -539,7 +539,7 @@ static void create_connector_properties(struct
drm_device *dev,
continue;
}
- drm_connector_attach_property(drm_connector, new_prop,
current_value);
+ drm_object_attach_property(drm_connector-base,
+ new_prop, current_value);
emgd_connector-properties[num_of_properties++] = new_prop;
}
@@ -646,12 +646,12 @@ static void create_connectors(struct drm_device
*dev,
#if 0
-drm_connector_attach_property(connector-base,
+drm_object_attach_property(connector-base,
dev-mode_config.scaling_mode_property,
DRM_MODE_SCALE_FULLSCREEN);
-
Re: [linux-yocto] v3.8 kernel recipes in meta-intel
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, March 05, 2013 8:41 AM
To: Kamble, Nitin A
Cc: linux-yocto@yoctoproject.org
Subject: Re: v3.8 kernel recipes in meta-intel
On 13-03-05 11:39 AM, Kamble, Nitin A wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, March 05, 2013 8:37 AM
To: Kamble, Nitin A
Cc: linux-yocto@yoctoproject.org
Subject: Re: v3.8 kernel recipes in meta-intel
On 13-03-05 11:33 AM, Kamble, Nitin A wrote:
Hi Bruce,
I am seeing some unexpected behavior of the v3.8 kernel bits.
Here is what I am trying to do.
Something is up with your linux-yocto clone:
Hi Bruce,
This is not with the local repo. As you can see the SRC_URI it is
pointing to the Upstream repo.
By local, I meant the repository the fetcher creates. That commit ID is valid
in
the upstream repository, so there's nothing I can say about why it isn't in
the
clone that is presented for building.
Bruce
Bruce,
I tried doing bitbake cleanall for the linux-yocto recipe. And it removed
my local copy,
and in the next build, it did take lot of time to clone it. But still the same
build error.
I wonder why the same commit topic branch is working for emenlow-noemgd BSP
and does not working for emenlow? The only relevant difference I see here is
SRCURI.
Nitin
Nitin
git show b170394a475b96ecc92cbc9e4b002bed0a9f69c5
commit b170394a475b96ecc92cbc9e4b002bed0a9f69c5
Author: Tom Zanussi tom.zanu...@intel.com
Date: Fri Oct 5 11:35:26 2012 -0500
perf annotate: replace 'expand' with equivalent sed expression
We don't have 'expand' in our userspace so we need to accomplish the
same thing using 'sed', which we do have.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
index 07aaeea..ff162ae 100644
--- a/tools/perf/util/annotate.c
+++ b/tools/perf/util/annotate.c
@@ -826,7 +826,7 @@ fallback:
snprintf(command, sizeof(command),
%s %s%s --start-address=0x%016 PRIx64
--stop-address=0x%016 PRIx64
- -d %s %s -C %s|grep -v %s|expand,
+ -d %s %s -C %s|grep -v %s|sed 's/\t//g',
objdump_path ? objdump_path : objdump,
disassembler_style ? -M : ,
disassembler_style ? disassembler_style : ,
git branch --contains b170394a475b96ecc92cbc9e4b002bed0a9f69c5
standard/arm-versatile-926ejs
standard/base
standard/beagleboard
standard/ck
standard/common-pc-64/base
standard/common-pc-64/chiefriver
standard/common-pc-64/crystalforest
standard/common-pc-64/jasperforest
standard/common-pc-64/rangeley
standard/common-pc-64/romley
standard/common-pc-64/sugarbay
standard/common-pc/atom-pc
standard/common-pc/base
standard/crownbay
standard/edf
standard/emenlow
standard/fri2
standard/fsl-mpc8315e-rdb
standard/mti-malta32
standard/mti-malta64
standard/preempt-rt/base
standard/preempt-rt/fri2
standard/preempt-rt/qemuppc
standard/preempt-rt/routerstationpro
standard/qemuppc
standard/routerstationpro
standard/sys940x
standard/tiny/base
standard/tiny/common-pc
standard/tiny/fri2
Whereas the tree you have locally doesn't have the commit at all.
Bruce
I am seeing this build error:
ERROR: Function failed: do_validate_branches (see
/srv/home/nitin/build-test-bsps/build-emenlow/tmp/work/emenlow-
poky-li
nux/linux-
yocto/3.8+gitAUTOINC+c2ed0f16fdec628242a682897d5d86df4547cf2
4_b170394a475b96ecc9
2cbc9e4b002bed0a9f69c5-r4.0/temp/log.do_validate_branches.3414 for
further information)
ERROR: Logfile of failure stored in:
/srv/home/nitin/build-test-bsps/build-emenlow/tmp/work/emenlow-
poky-li
nux/linux-
yocto/3.8+gitAUTOINC+c2ed0f16fdec628242a682897d5d86df4547cf2
4_b170394a475b96ecc92cbc9e4b002bed0a9f69c5-
r4.0/temp/log.do_validate_b
ranches.3414
Log data follows:
| DEBUG: Executing shell function do_validate_branches
| error: no such commit b170394a475b96ecc92cbc9e4b002bed0a9f69c5
This is with the master branches of poky oecore + v3.8 bbappends
in the meta-intel layer.
* poky.git : master: commit
93ec7b4d1550e07caec86e2998d0f94a01c7e785
* meta-intel.git : master: commit
4ffe40409f8cd0f354a7488113ef888b42867033
And this is my v3.8 bbappend in the meta-intel
meta-emenlow/recipes-kernel/linux/linux-yocto_3.8.bbappend :
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
COMPATIBLE_MACHINE_emenlow = emenlow
KMACHINE_emenlow = emenlow
KBRANCH_emenlow = standard/emenlow
KERNEL_FEATURES_emenlow_append = features/drm
Re: [linux-yocto] [meta branch v3 01/12] meta: relocate git-merge of emgd branch
-Original Message- From: Zanussi, Tom Sent: Thursday, January 17, 2013 1:55 PM To: Kamble, Nitin A Cc: bruce.ashfi...@windriver.com; Hart, Darren; linux- yo...@yoctoproject.org Subject: Re: [meta branch v3 01/12] meta: relocate git-merge of emgd branch On Wed, 2013-01-16 at 11:23 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Move git-merge of emgd branch out from the bsp area and into the features area Just a minor nit - can you please proofread for obvious typos like below before submitting? Thanks Tom for catching this, and sorry for I missing these typos. I have corrected these from all the commit messages on the contrib branch. Nitin This change avoids getting emged sources unnecessarily included in the ^ noemgd bsp kernel sources. This addresses this bug/feature rquest: ^^ Thanks, Tom [YOCTO #2268] Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../bsp/crownbay/crownbay-standard.scc |2 -- .../kernel-cache/bsp/emenlow/emenlow-standard.scc |2 -- meta/cfg/kernel-cache/bsp/fri2/fri2-standard.scc |2 -- .../kernel-cache/bsp/sys940x/sys940x-standard.scc |2 -- .../kernel-cache/features/drm-emgd/drm-emgd.scc|1 + 5 files changed, 1 insertions(+), 8 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/crownbay/crownbay-standard.scc b/meta/cfg/kernel-cache/bsp/crownbay/crownbay-standard.scc index 3db03de..9fe4776 100644 --- a/meta/cfg/kernel-cache/bsp/crownbay/crownbay-standard.scc +++ b/meta/cfg/kernel-cache/bsp/crownbay/crownbay-standard.scc @@ -5,8 +5,6 @@ define KARCH i386 include ktypes/standard branch crownbay -git merge emgd-1.14 - include crownbay.scc # default policy for standard kernels diff --git a/meta/cfg/kernel-cache/bsp/emenlow/emenlow-standard.scc b/meta/cfg/kernel-cache/bsp/emenlow/emenlow-standard.scc index a2094ef..3526a18 100644 --- a/meta/cfg/kernel-cache/bsp/emenlow/emenlow-standard.scc +++ b/meta/cfg/kernel-cache/bsp/emenlow/emenlow-standard.scc @@ -5,8 +5,6 @@ define KARCH i386 include ktypes/standard branch emenlow -git merge emgd-1.14 - include emenlow.scc # default policy for standard kernels diff --git a/meta/cfg/kernel-cache/bsp/fri2/fri2-standard.scc b/meta/cfg/kernel-cache/bsp/fri2/fri2-standard.scc index fc47a2e..029eafa 100644 --- a/meta/cfg/kernel-cache/bsp/fri2/fri2-standard.scc +++ b/meta/cfg/kernel-cache/bsp/fri2/fri2-standard.scc @@ -5,8 +5,6 @@ define KARCH i386 include ktypes/standard branch fri2 -git merge emgd-1.14 - include fri2.scc # Extra fri2 configs above the minimal defined in fri2.scc diff --git a/meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc b/meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc index 3149a3e..7b21cbc 100644 --- a/meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc +++ b/meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc @@ -5,8 +5,6 @@ define KARCH i386 include ktypes/standard branch sys940x -git merge emgd-1.14 - include sys940x.scc include cfg/efi-ext.scc diff --git a/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd.scc b/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd.scc index 672ee2e..01bcec8 100644 --- a/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd.scc +++ b/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd.scc @@ -1 +1,2 @@ kconf hardware drm-emgd.cfg +git merge emgd-1.14 ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
