[linux-yocto] [linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of __list_lru_init_key
__list_lru_init_key does not exist. We're looking for __list_lru_init as
shown in the patch "26690f5 mm: workingset: fix premature shadow node
shrinking with cgroups".
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
This is for the standard/preempt-rt/base branch. Standard/base is OK.
mm/workingset.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/workingset.c b/mm/workingset.c
index 1856fdb..5e953eb 100644
--- a/mm/workingset.c
+++ b/mm/workingset.c
@@ -493,7 +493,7 @@ static int __init workingset_init(void)
pr_info("workingset: timestamp_bits=%d max_order=%d bucket_order=%u\n",
timestamp_bits, max_order, bucket_order);
- ret = __list_lru_init_key(&__workingset_shadow_nodes, true,
_nodes_key);
+ ret = __list_lru_init(&__workingset_shadow_nodes, true,
_nodes_key);
if (ret)
goto err;
ret = register_shrinker(_shadow_shrinker);
--
2.9.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-kernel-cache][PATCH] features/usb/usb-typec: fix dependencies
Adds dependencies that were missing. In some BSPs, they were satisfied, in others they weren't and caused warnings. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- For yocto-4.9 and newer. features/usb/usb-typec.cfg | 3 +++ features/usb/usb-typec.scc | 2 ++ 2 files changed, 5 insertions(+) diff --git a/features/usb/usb-typec.cfg b/features/usb/usb-typec.cfg index 09b82dc..b23b75e 100644 --- a/features/usb/usb-typec.cfg +++ b/features/usb/usb-typec.cfg @@ -1,2 +1,5 @@ +# Dependencies +CONFIG_INTEL_PMC_IPC=y + # Intel WhiskeyCove PMIC USB Type-C PHY driver CONFIG_TYPEC_WCOVE=m diff --git a/features/usb/usb-typec.scc b/features/usb/usb-typec.scc index 5828e98..a55629a 100644 --- a/features/usb/usb-typec.scc +++ b/features/usb/usb-typec.scc @@ -1,4 +1,6 @@ define KFEATURE_DESCRIPTION "Enable Intel WhiskeyCove PMIC USB Type C PHY driver" define KFEATURE_COMPATIBILITY board +include features/power/intel_pmic.scc + kconf hardware usb-typec.cfg -- 2.9.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-kernel-cache][PATCH v2] common-pc-wifi.cfg: Add CONFIG_BRCMFMAC_PCIE
This is needed for some Broadcomm wifi drivers. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- Actually applies to 4.9, 4.10, and 4.12 this time. It looks like master is missing "b898385 wifi: drop BRCMFMAC_PROTO_MSGBUF, since it is selected" so that should be applied before this patch. bsp/common-pc/common-pc-wifi.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/bsp/common-pc/common-pc-wifi.cfg b/bsp/common-pc/common-pc-wifi.cfg index 14d82b1..7831abe 100644 --- a/bsp/common-pc/common-pc-wifi.cfg +++ b/bsp/common-pc/common-pc-wifi.cfg @@ -24,6 +24,7 @@ CONFIG_BRCMFMAC=m CONFIG_BRCMFMAC_USB=y CONFIG_BRCMFMAC_SDIO=y CONFIG_BRCMFMAC_PROTO_BCDC=y +CONFIG_BRCMFMAC_PCIE=y CONFIG_WEXT_CORE=y CONFIG_WEXT_PROC=y -- 2.9.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-kernel-cache][PATCH] common-pc-wifi.cfg: Add CONFIG_BRCMFMAC_PCIE
This is needed for some Broadcomm wifi drivers. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- This is for yocto-4.9 and newer. bsp/common-pc/common-pc-wifi.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/bsp/common-pc/common-pc-wifi.cfg b/bsp/common-pc/common-pc-wifi.cfg index 272f912..c2f7d38 100644 --- a/bsp/common-pc/common-pc-wifi.cfg +++ b/bsp/common-pc/common-pc-wifi.cfg @@ -20,6 +20,7 @@ CONFIG_BRCMUTIL=m CONFIG_BRCMSMAC=m CONFIG_BRCMFMAC=m CONFIG_BRCMFMAC_USB=y +CONFIG_BRCMFMAC_PCIE=y CONFIG_WEXT_CORE=y CONFIG_WEXT_PROC=y -- 2.9.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [linux-yocto-4.4][PATCH] drivers/usb/dwc3/gadget.c: fix merge
Commit "c813008 usb: dwc3: replace %p with %pK" did not apply correctly
due a previous backport. In the confusion, some error checking was
added back which included a goto whose target didn't exist, causing a
compilation failure.
Fix the issue by reverting the merge and the patch, then manually
applying the intended changes (replacing all instances of %p with %pK in
the affected files).
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
This is for the standard/intel/base branch, which should then be
waterfalled into the other intel branches.
drivers/usb/dwc3/gadget.c | 21 -
1 file changed, 4 insertions(+), 17 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index 192c119..6c369a6 100644
--- a/drivers/usb/dwc3/gadget.c
+++ b/drivers/usb/dwc3/gadget.c
@@ -813,7 +813,7 @@ static void dwc3_prepare_one_trb(struct dwc3_ep *dep,
{
struct dwc3_trb *trb;
- dwc3_trace(trace_dwc3_gadget, "%s: req %p dma %08llx length %d%s%s",
+ dwc3_trace(trace_dwc3_gadget, "%s: req %pK dma %08llx length %d%s%s",
dep->name, req, (unsigned long long) dma,
length, last ? " last" : "",
chain ? " chain" : "");
@@ -1085,14 +1085,14 @@ static int __dwc3_gadget_ep_queue(struct dwc3_ep *dep,
struct dwc3_request *req)
if (!dep->endpoint.desc) {
dwc3_trace(trace_dwc3_gadget,
- "trying to queue request %p to disabled %s\n",
+ "trying to queue request %pK to disabled %s\n",
>request, dep->endpoint.name);
return -ESHUTDOWN;
}
- if (WARN(req->dep != dep, "request %p belongs to '%s'\n",
+ if (WARN(req->dep != dep, "request %pK belongs to '%s'\n",
>request, req->dep->name)) {
- dwc3_trace(trace_dwc3_gadget, "request %p belongs to '%s'\n",
+ dwc3_trace(trace_dwc3_gadget, "request %pK belongs to '%s'\n",
>request, req->dep->name);
return -EINVAL;
}
@@ -1242,19 +1242,6 @@ static int dwc3_gadget_ep_queue(struct usb_ep *ep,
struct usb_request *request,
int ret;
spin_lock_irqsave(>lock, flags);
- if (!dep->endpoint.desc) {
- dev_dbg(dwc->dev, "trying to queue request %p to disabled %s\n",
- request, ep->name);
- ret = -ESHUTDOWN;
- goto out;
- }
-
- if (WARN(req->dep != dep, "request %pK belongs to '%s'\n",
- request, req->dep->name)) {
- ret = -EINVAL;
- goto out;
- }
-
ret = __dwc3_gadget_ep_queue(dep, req);
/*
--
2.9.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-kernel-cache][PATCH] broxton.cfg: Add CONFIG_INTEL_SOC_PMIC_BXTWC
This new option was added iand is a dependency for a number of other PMIC options. Fixes several config warnings. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- This is for the yocto-4.12 branch. features/soc/broxton/broxton.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/features/soc/broxton/broxton.cfg b/features/soc/broxton/broxton.cfg index 446bd54..181b203 100644 --- a/features/soc/broxton/broxton.cfg +++ b/features/soc/broxton/broxton.cfg @@ -19,4 +19,5 @@ CONFIG_GPIO_GENERIC=y CONFIG_GPIO_GENERIC_PLATFORM=y # ACPI operation region support for BXT WhiskeyCove PMIC +CONFIG_INTEL_SOC_PMIC_BXTWC=y CONFIG_BXT_WC_PMIC_OPREGION=y -- 2.9.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH][linux-yocto-4.4] usb: dwc3: ep0: Fix merge
The call to trace_dwc3_prepare_trb() was moved into the
dwc3_ep0_prepare_one_trb() function in patch ecd4ad9ab7 "usb: dwc3: ep0:
add dwc3_ep0_prepare_one_trb()", but it somehow got left behind in the
merge.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
This is intended for standard/intel/base, which then needs merged into
the other Intel branches.
drivers/usb/dwc3/ep0.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/dwc3/ep0.c b/drivers/usb/dwc3/ep0.c
index 0aa0c8c..ed8afa0 100644
--- a/drivers/usb/dwc3/ep0.c
+++ b/drivers/usb/dwc3/ep0.c
@@ -101,8 +101,6 @@ static int dwc3_ep0_start_trans(struct dwc3 *dwc, u8 epnum)
params.param0 = upper_32_bits(dwc->ep0_trb_addr);
params.param1 = lower_32_bits(dwc->ep0_trb_addr);
- trace_dwc3_prepare_trb(dep, trb);
-
ret = dwc3_send_gadget_ep_cmd(dep, DWC3_DEPCMD_STARTTRANSFER, );
if (ret < 0) {
dwc3_trace(trace_dwc3_ep0, "%s STARTTRANSFER failed",
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/3] features/i2c: Support I2C_MUX by default
Some drivers (e.g. INV_MPU6050_I2C) rely on this, and in most cases this gets selected automatically, but in some cases its not and it causes a configcheck warning. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/i2c/i2c.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/features/i2c/i2c.cfg b/features/i2c/i2c.cfg index bcd08a3..be41f4b 100644 --- a/features/i2c/i2c.cfg +++ b/features/i2c/i2c.cfg @@ -1,2 +1,3 @@ CONFIG_I2C=y CONFIG_I2C_HELPER_AUTO=y +CONFIG_I2C_MUX=y -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/3] leds.cfg: Remove CONFIG_LEDS_TRIGGER_CPU
This is incompatible with preempt-rt and would be a mess to fix any other way. If we were to move CONFIG_LEDS_TRIGGER_CPU to a new feature such as leds-full, it would require us to add leds-full to every non-rt BSP wanting leds support, and -rt BSPs would need the feature without it. Setting "# CONFIG_LEDS_TRIGGER_CPU is not set" also doesn't work, as it depends on !PREEMPT_RT_BASE, making it completely unavailable for setting and still giving us a warning in kernel_configcheck. All this option does is allow CPUs to trigger LEDs based on their usage, so it is not a major loss anyway. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/leds/leds.cfg | 2 -- 1 file changed, 2 deletions(-) diff --git a/features/leds/leds.cfg b/features/leds/leds.cfg index 77f5209..78bb13b 100644 --- a/features/leds/leds.cfg +++ b/features/leds/leds.cfg @@ -2,8 +2,6 @@ CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_TRIGGERS=y -CONFIG_LEDS_TRIGGER_CPU=y - CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_ONESHOT=y CONFIG_LEDS_TRIGGER_HEARTBEAT=y -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/3] bsp/intel-quark: Remove bosch-pressure-sensor-i2c
The newer BMP280 IIO driver appears to support the BMP085 chip as well, and the old BMP085 driver cannot be enabled at the same time, giving us configcheck warnings if we try. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-quark.scc | 3 --- 1 file changed, 3 deletions(-) diff --git a/bsp/intel-common/intel-quark.scc b/bsp/intel-common/intel-quark.scc index 573d412..8ca5ef9 100644 --- a/bsp/intel-common/intel-quark.scc +++ b/bsp/intel-common/intel-quark.scc @@ -13,9 +13,6 @@ include cfg/timer/hz_100.scc include features/soc/x1000/x1000.scc include features/usb/serial-all.scc -# Add misc drivers for IoT support -include features/misc/bosch-pressure-sensor-i2c.scc - # This line comes last as it has the final word on # CONFIG values. kconf hardware intel-quark.cfg -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-kernel-cache][PATCH 0/3] Fix remaining kernel_configcheck warnings in Intel BSPs
These are fairly minor changes, but I could use some feedback on the third patch. Although it would be extremely messy, it is possible to keep LEDS_TRIGGER_CPU only for non-preempt-rt BSPs. I just don't know if its worthwhile for such a small functionality that likely goes unused. Patches are targetted for both yocto-4.4 and yocto-4.8. California Sullivan (3): features/i2c: Support I2C_MUX by default bsp/intel-quark: Remove bosch-pressure-sensor-i2c leds.cfg: Remove CONFIG_LEDS_TRIGGER_CPU bsp/intel-common/intel-quark.scc | 3 --- features/i2c/i2c.cfg | 1 + features/leds/leds.cfg | 2 -- 3 files changed, 1 insertion(+), 5 deletions(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 1/1] drm/i915: Fix v4.4.20 -> v4.4.22 i915 merge.
Some patches did not merge cleanly in previous merge, causing build
failures. The i915 changes between 94e5bb30ea and 1fd9c1008d were
reverted and the patches were reapplied as follows, then the results
were squashed.
Commit a554bd7ccf "drm/i915: Fix hpd live status bits for g4x" was
already present before the merge and did not need reapplied or fixing.
Commit af115b1a3a "drm/i915: Only ignore eDP ports that are connected"
was resolved by applying the upstream version of the patch instead of
the version that came from stable. This applied cleanly.
Commit e153f52df9 "drm/i915: Check VBT for port presence in
addition to the strap on VLV/CHV" did not apply cleanly with either the
upstream or stable versions, and had to be fixed manually.
Commit 0da2f8261e "drm/i915: Avoid pointer arithmetic in calculating
plane surface offset" was already present before the merge and did not
need reapplied or fixing.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/i915/intel_bios.c| 39
drivers/gpu/drm/i915/intel_display.c | 1 +
drivers/gpu/drm/i915/intel_dp.c | 6 +++---
drivers/gpu/drm/i915/intel_drv.h | 2 +-
5 files changed, 45 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 6f1e0f1..19819aa 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -3485,6 +3485,7 @@ bool intel_bios_is_port_edp(struct drm_i915_private
*dev_priv, enum port port);
bool intel_bios_is_dsi_present(struct drm_i915_private *dev_priv, enum port
*port);
bool intel_bios_is_port_hpd_inverted(struct drm_i915_private *dev_priv,
enum port port);
+bool intel_bios_is_port_present(struct drm_i915_private *dev_priv, enum port
port);
/* intel_opregion.c */
#ifdef CONFIG_ACPI
diff --git a/drivers/gpu/drm/i915/intel_bios.c
b/drivers/gpu/drm/i915/intel_bios.c
index e72dd9a..8118364 100644
--- a/drivers/gpu/drm/i915/intel_bios.c
+++ b/drivers/gpu/drm/i915/intel_bios.c
@@ -1660,3 +1660,42 @@ intel_bios_is_port_hpd_inverted(struct drm_i915_private
*dev_priv,
return false;
}
+
+/**
+ * intel_bios_is_port_present - is the specified digital port present
+ * @dev_priv: i915 device instance
+ * @port: port to check
+ *
+ * Return true if the device in %port is present.
+ */
+bool intel_bios_is_port_present(struct drm_i915_private *dev_priv, enum port
port)
+{
+ static const struct {
+ u16 dp, hdmi;
+ } port_mapping[] = {
+ [PORT_B] = { DVO_PORT_DPB, DVO_PORT_HDMIB, },
+ [PORT_C] = { DVO_PORT_DPC, DVO_PORT_HDMIC, },
+ [PORT_D] = { DVO_PORT_DPD, DVO_PORT_HDMID, },
+ [PORT_E] = { DVO_PORT_DPE, DVO_PORT_HDMIE, },
+ };
+ int i;
+
+ /* FIXME maybe deal with port A as well? */
+ if (WARN_ON(port == PORT_A) || port >= ARRAY_SIZE(port_mapping))
+ return false;
+
+ if (!dev_priv->vbt.child_dev_num)
+ return false;
+
+ for (i = 0; i < dev_priv->vbt.child_dev_num; i++) {
+ const union child_device_config *p_child =
+ _priv->vbt.child_dev[i];
+ if ((p_child->common.dvo_port == port_mapping[port].dp ||
+p_child->common.dvo_port == port_mapping[port].hdmi) &&
+ (p_child->common.device_type &
(DEVICE_TYPE_TMDS_DVI_SIGNALING |
+
DEVICE_TYPE_DISPLAYPORT_OUTPUT)))
+ return true;
+ }
+
+ return false;
+}
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 8a4a372..70dd990 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -14559,6 +14559,7 @@ static void intel_setup_outputs(struct drm_device *dev)
if (I915_READ(PCH_DP_D) & DP_DETECTED)
intel_dp_init(dev, PCH_DP_D, PORT_D);
} else if (IS_VALLEYVIEW(dev) || IS_CHERRYVIEW(dev)) {
+ bool has_edp, has_port;
/*
* The DP_DETECTED bit is the latched state of the DDC
* SDA pin at boot. However since eDP doesn't require DDC
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 62bd8f7..12bd17f 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -5957,9 +5957,9 @@ fail:
return false;
}
-void
-intel_dp_init(struct drm_device *dev,
- i915_reg_t output_reg, enum port port)
+bool intel_dp_init(struct drm_device *dev,
+ i915_reg_t output_reg,
+ enum port port)
{
struct drm_i915_private *dev_priv = dev->dev_private;
[linux-yocto] [PATCH v2 1/1] drm/i915: Fix v4.4.20 -> v4.4.22 i915 merge.
Portions of commit e153f52df9 "drm/i915: Check VBT for port presence in
addition to the strap on VLV/CHV" were missed in the merge commit,
causing build errors. This patch fixes the issues by reverting the i915
changes in the merge, reapplying the patches and fixing conflicts
where they occur, then squashing the result.
Patches besides e153f52df9 either applied cleanly or were also present
before the merge and did not need fixing.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/i915/intel_bios.c| 39
drivers/gpu/drm/i915/intel_display.c | 1 +
drivers/gpu/drm/i915/intel_dp.c | 6 +++---
drivers/gpu/drm/i915/intel_drv.h | 2 +-
5 files changed, 45 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 6f1e0f1..19819aa 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -3485,6 +3485,7 @@ bool intel_bios_is_port_edp(struct drm_i915_private
*dev_priv, enum port port);
bool intel_bios_is_dsi_present(struct drm_i915_private *dev_priv, enum port
*port);
bool intel_bios_is_port_hpd_inverted(struct drm_i915_private *dev_priv,
enum port port);
+bool intel_bios_is_port_present(struct drm_i915_private *dev_priv, enum port
port);
/* intel_opregion.c */
#ifdef CONFIG_ACPI
diff --git a/drivers/gpu/drm/i915/intel_bios.c
b/drivers/gpu/drm/i915/intel_bios.c
index e72dd9a..8118364 100644
--- a/drivers/gpu/drm/i915/intel_bios.c
+++ b/drivers/gpu/drm/i915/intel_bios.c
@@ -1660,3 +1660,42 @@ intel_bios_is_port_hpd_inverted(struct drm_i915_private
*dev_priv,
return false;
}
+
+/**
+ * intel_bios_is_port_present - is the specified digital port present
+ * @dev_priv: i915 device instance
+ * @port: port to check
+ *
+ * Return true if the device in %port is present.
+ */
+bool intel_bios_is_port_present(struct drm_i915_private *dev_priv, enum port
port)
+{
+ static const struct {
+ u16 dp, hdmi;
+ } port_mapping[] = {
+ [PORT_B] = { DVO_PORT_DPB, DVO_PORT_HDMIB, },
+ [PORT_C] = { DVO_PORT_DPC, DVO_PORT_HDMIC, },
+ [PORT_D] = { DVO_PORT_DPD, DVO_PORT_HDMID, },
+ [PORT_E] = { DVO_PORT_DPE, DVO_PORT_HDMIE, },
+ };
+ int i;
+
+ /* FIXME maybe deal with port A as well? */
+ if (WARN_ON(port == PORT_A) || port >= ARRAY_SIZE(port_mapping))
+ return false;
+
+ if (!dev_priv->vbt.child_dev_num)
+ return false;
+
+ for (i = 0; i < dev_priv->vbt.child_dev_num; i++) {
+ const union child_device_config *p_child =
+ _priv->vbt.child_dev[i];
+ if ((p_child->common.dvo_port == port_mapping[port].dp ||
+p_child->common.dvo_port == port_mapping[port].hdmi) &&
+ (p_child->common.device_type &
(DEVICE_TYPE_TMDS_DVI_SIGNALING |
+
DEVICE_TYPE_DISPLAYPORT_OUTPUT)))
+ return true;
+ }
+
+ return false;
+}
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 8a4a372..70dd990 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -14559,6 +14559,7 @@ static void intel_setup_outputs(struct drm_device *dev)
if (I915_READ(PCH_DP_D) & DP_DETECTED)
intel_dp_init(dev, PCH_DP_D, PORT_D);
} else if (IS_VALLEYVIEW(dev) || IS_CHERRYVIEW(dev)) {
+ bool has_edp, has_port;
/*
* The DP_DETECTED bit is the latched state of the DDC
* SDA pin at boot. However since eDP doesn't require DDC
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 62bd8f7..12bd17f 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -5957,9 +5957,9 @@ fail:
return false;
}
-void
-intel_dp_init(struct drm_device *dev,
- i915_reg_t output_reg, enum port port)
+bool intel_dp_init(struct drm_device *dev,
+ i915_reg_t output_reg,
+ enum port port)
{
struct drm_i915_private *dev_priv = dev->dev_private;
struct intel_digital_port *intel_dig_port;
diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
index 236ce98..6f69e14 100644
--- a/drivers/gpu/drm/i915/intel_drv.h
+++ b/drivers/gpu/drm/i915/intel_drv.h
@@ -1279,7 +1279,7 @@ void intel_csr_ucode_suspend(struct drm_i915_private *);
void intel_csr_ucode_resume(struct drm_i915_private *);
/* intel_dp.c */
-void intel_dp_init(struct drm_device *dev, i915_reg_t output_reg, enum port
port);
+bool intel_dp_init(struct drm_
[linux-yocto] [PATCH 1/1] drm/i915: Fix v4.4.20 -> v4.4.22 i915 merge.
The addition of a new function and some return types was missed in the
original merge, causing build errors.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/i915/intel_bios.c| 39
drivers/gpu/drm/i915/intel_display.c | 2 ++
drivers/gpu/drm/i915/intel_dp.c | 6 +++---
drivers/gpu/drm/i915/intel_drv.h | 2 +-
5 files changed, 46 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 6f1e0f1..19819aa 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -3485,6 +3485,7 @@ bool intel_bios_is_port_edp(struct drm_i915_private
*dev_priv, enum port port);
bool intel_bios_is_dsi_present(struct drm_i915_private *dev_priv, enum port
*port);
bool intel_bios_is_port_hpd_inverted(struct drm_i915_private *dev_priv,
enum port port);
+bool intel_bios_is_port_present(struct drm_i915_private *dev_priv, enum port
port);
/* intel_opregion.c */
#ifdef CONFIG_ACPI
diff --git a/drivers/gpu/drm/i915/intel_bios.c
b/drivers/gpu/drm/i915/intel_bios.c
index e72dd9a..8118364 100644
--- a/drivers/gpu/drm/i915/intel_bios.c
+++ b/drivers/gpu/drm/i915/intel_bios.c
@@ -1660,3 +1660,42 @@ intel_bios_is_port_hpd_inverted(struct drm_i915_private
*dev_priv,
return false;
}
+
+/**
+ * intel_bios_is_port_present - is the specified digital port present
+ * @dev_priv: i915 device instance
+ * @port: port to check
+ *
+ * Return true if the device in %port is present.
+ */
+bool intel_bios_is_port_present(struct drm_i915_private *dev_priv, enum port
port)
+{
+ static const struct {
+ u16 dp, hdmi;
+ } port_mapping[] = {
+ [PORT_B] = { DVO_PORT_DPB, DVO_PORT_HDMIB, },
+ [PORT_C] = { DVO_PORT_DPC, DVO_PORT_HDMIC, },
+ [PORT_D] = { DVO_PORT_DPD, DVO_PORT_HDMID, },
+ [PORT_E] = { DVO_PORT_DPE, DVO_PORT_HDMIE, },
+ };
+ int i;
+
+ /* FIXME maybe deal with port A as well? */
+ if (WARN_ON(port == PORT_A) || port >= ARRAY_SIZE(port_mapping))
+ return false;
+
+ if (!dev_priv->vbt.child_dev_num)
+ return false;
+
+ for (i = 0; i < dev_priv->vbt.child_dev_num; i++) {
+ const union child_device_config *p_child =
+ _priv->vbt.child_dev[i];
+ if ((p_child->common.dvo_port == port_mapping[port].dp ||
+p_child->common.dvo_port == port_mapping[port].hdmi) &&
+ (p_child->common.device_type &
(DEVICE_TYPE_TMDS_DVI_SIGNALING |
+
DEVICE_TYPE_DISPLAYPORT_OUTPUT)))
+ return true;
+ }
+
+ return false;
+}
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 8a4a372..bf0e19c 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -14559,6 +14559,8 @@ static void intel_setup_outputs(struct drm_device *dev)
if (I915_READ(PCH_DP_D) & DP_DETECTED)
intel_dp_init(dev, PCH_DP_D, PORT_D);
} else if (IS_VALLEYVIEW(dev) || IS_CHERRYVIEW(dev)) {
+ bool has_edp, has_port;
+
/*
* The DP_DETECTED bit is the latched state of the DDC
* SDA pin at boot. However since eDP doesn't require DDC
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 62bd8f7..12bd17f 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -5957,9 +5957,9 @@ fail:
return false;
}
-void
-intel_dp_init(struct drm_device *dev,
- i915_reg_t output_reg, enum port port)
+bool intel_dp_init(struct drm_device *dev,
+ i915_reg_t output_reg,
+ enum port port)
{
struct drm_i915_private *dev_priv = dev->dev_private;
struct intel_digital_port *intel_dig_port;
diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
index 236ce98..6f69e14 100644
--- a/drivers/gpu/drm/i915/intel_drv.h
+++ b/drivers/gpu/drm/i915/intel_drv.h
@@ -1279,7 +1279,7 @@ void intel_csr_ucode_suspend(struct drm_i915_private *);
void intel_csr_ucode_resume(struct drm_i915_private *);
/* intel_dp.c */
-void intel_dp_init(struct drm_device *dev, i915_reg_t output_reg, enum port
port);
+bool intel_dp_init(struct drm_device *dev, i915_reg_t output_reg, enum port
port);
bool intel_dp_init_connector(struct intel_digital_port *intel_dig_port,
struct intel_connector *intel_connector);
void intel_dp_set_link_params(struct intel_dp *intel_dp,
--
2.5.5
--
___
linux-yoct
[linux-yocto] [PATCH 0/1] Fix i915 merge
Hi Eric, The conversation with you, Ilkka, and Fei seems to point towards just fixing the few merge conflicts we get with stable, so that's what I have here. I have built and boot tested this patch but I don't know if I have the process correct. This is a squashed version of reverting the i915 merge from v4.4.20 -> v4.4.22, then reapplying the patches and fixing them as needed. Let me know if I should send that series instead, or do something entirely different. Bruce, If Eric gives the OK go ahead and merge this. Thanks, Cal Sullivan California Sullivan (1): drm/i915: Fix v4.4.20 -> v4.4.22 i915 merge. drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_bios.c| 39 drivers/gpu/drm/i915/intel_display.c | 2 ++ drivers/gpu/drm/i915/intel_dp.c | 6 +++--- drivers/gpu/drm/i915/intel_drv.h | 2 +- 5 files changed, 46 insertions(+), 4 deletions(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-kernel-cache][PATCH 0/2] Fix kernel_configcheck warnings in Intel BSPs
These patches fix most of the configcheck warnings we see with the 4.8 kenel. There are still a couple that I haven't decided how to solve yet, but it gets most of them. With intel-quark we get: Config: CONFIG_INV_MPU6050_I2C Requested value: CONFIG_INV_MPU6050_I2C=m Actual value: Due to a missing I2C_MUX dependency on a driver enabled in iio.cfg. In other BSPs this dependency is satisfied automatically through a select, and I just haven't decided the appropriate place for this yet. Config: CONFIG_BMP280 Requested value: # CONFIG_BMP280 is not set Actual value: Because BMP280 depends on !BMP085 which is used in in bosch-pressure-sensor-i2c and BMP280 is enabled in iio.cfg. Previously this warning complained about BMP280 not getting enabled, so I added "# CONFIG_BMP280 is not set" to the bosch settings, giving us a less scary warning message. With intel-core2-32 or intel-corei7-64 preempt-rt builds we get: Config: CONFIG_LEDS_TRIGGER_CPU Requested value: CONFIG_LEDS_TRIGGER_CPU=y Actual value: >From leds.cfg, included in intel-common-drivers (and thus all intel-* BSPs), trying to enable LEDS_TRIGGER_CPU when it depends on !PREEMPT_RT_BASE. Fixing this one could be uglier. With intel-corei7-64 and intel-core2-32 standard builds, we get no warnings! Let me know if you have any feedback or need to make changes to this patch set. Thanks, Cal California Sullivan (2): features: Fix configcheck warnings in features used by intel-core* BSPs features: Fix configcheck warnings in features used by intel-quark BSPs features/iio/iio.cfg| 4 features/mei/mei-me.cfg | 2 +- features/misc/bosch-pressure-sensor-i2c.cfg | 3 ++- features/nfc/nfc-vendor.cfg | 2 ++ features/soc/x1000/x1000.cfg| 7 --- features/thermal/coretemp.cfg | 2 +- 6 files changed, 10 insertions(+), 10 deletions(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/2] features: Fix configcheck warnings in features used by intel-core* BSPs
IOSF_MBI gets selected by CONFIG_X86_INTEL_LPSS, forcing it to =y and giving us a warning in the kernel_configcheck stage. Fix this by setting CONFIG_IOSF_MBI=y. INV_MPU6050, MPL115, and NFC_PN533 all had their core driver separated from specific implementations such as I2C, SPI, and USB, and can only be enabled by adding one or more of those implementations. This means we weren't getting the drivers and warnings occurred during the kernel_configcheck stage. Fix this by adding the implementations that were separated. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/iio/iio.cfg | 4 features/nfc/nfc-vendor.cfg | 2 ++ features/thermal/coretemp.cfg | 2 +- 3 files changed, 7 insertions(+), 1 deletion(-) diff --git a/features/iio/iio.cfg b/features/iio/iio.cfg index 89b881d..3dac267 100644 --- a/features/iio/iio.cfg +++ b/features/iio/iio.cfg @@ -150,6 +150,8 @@ CONFIG_ADIS16480=m CONFIG_IIO_ADIS_LIB=m CONFIG_IIO_ADIS_LIB_BUFFER=y CONFIG_INV_MPU6050_IIO=m +CONFIG_INV_MPU6050_I2C=m +CONFIG_INV_MPU6050_SPI=m # # Light sensors @@ -196,6 +198,8 @@ CONFIG_IIO_SYSFS_TRIGGER=m # CONFIG_BMP280=m CONFIG_MPL115=m +CONFIG_MPL115_I2C=m +CONFIG_MPL155_SPI=m CONFIG_MPL3115=m CONFIG_MS5611=m CONFIG_MS5611_I2C=m diff --git a/features/nfc/nfc-vendor.cfg b/features/nfc/nfc-vendor.cfg index c012560..eacccf2 100644 --- a/features/nfc/nfc-vendor.cfg +++ b/features/nfc/nfc-vendor.cfg @@ -1,3 +1,5 @@ CONFIG_NFC_PN533=m +CONFIG_NFC_PN533_I2C=m +CONFIG_NFC_PN533_USB=m CONFIG_NFC_MRVL=m CONFIG_NFC_MRVL_USB=m diff --git a/features/thermal/coretemp.cfg b/features/thermal/coretemp.cfg index 47db747..fdab608 100644 --- a/features/thermal/coretemp.cfg +++ b/features/thermal/coretemp.cfg @@ -1,5 +1,5 @@ # IOSF_MBI is required by INTEL_SOC_DTS_THERMAL -CONFIG_IOSF_MBI=m +CONFIG_IOSF_MBI=y # Intel Core/Core2/Atom temperature sensor CONFIG_SENSORS_CORETEMP=m -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/2] features: Fix configcheck warnings in features used by intel-quark BSPs
In mei-me.cfg, CONFIG_PCI was mistakenly set to =m when its a boolean. In bosch-pressure-sensor-i2c, change CONFIG_BMP085 to =m instead of =y, as its dependency is a module. Also attempt to disable BMP280, as it conflicts with the BMP085 driver and throws a warning. In x1000.cfg, remove CONSOLE related 'is not set' CONFIGs. VGA_CONSOLE can't be disabled without enabling EXPERT (and therefore DEBUG_KERNEL), which we don't want normally. The other two configurations are missing dependencies, so they don't get set anyway, but cause warnings. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/mei/mei-me.cfg | 2 +- features/misc/bosch-pressure-sensor-i2c.cfg | 3 ++- features/soc/x1000/x1000.cfg| 7 --- 3 files changed, 3 insertions(+), 9 deletions(-) diff --git a/features/mei/mei-me.cfg b/features/mei/mei-me.cfg index 33423f8..87e81d0 100644 --- a/features/mei/mei-me.cfg +++ b/features/mei/mei-me.cfg @@ -1,2 +1,2 @@ -CONFIG_PCI=m +CONFIG_PCI=y CONFIG_INTEL_MEI_ME=m diff --git a/features/misc/bosch-pressure-sensor-i2c.cfg b/features/misc/bosch-pressure-sensor-i2c.cfg index e24ab24..977a6de 100644 --- a/features/misc/bosch-pressure-sensor-i2c.cfg +++ b/features/misc/bosch-pressure-sensor-i2c.cfg @@ -1,2 +1,3 @@ -CONFIG_BMP085=y +# CONFIG_BMP280 is not set +CONFIG_BMP085=m CONFIG_BMP085_I2C=m diff --git a/features/soc/x1000/x1000.cfg b/features/soc/x1000/x1000.cfg index cd4fcc2..c3fb230 100644 --- a/features/soc/x1000/x1000.cfg +++ b/features/soc/x1000/x1000.cfg @@ -21,10 +21,3 @@ CONFIG_MMC_SDHCI_PLTFM=y CONFIG_MMC_USHC=m CONFIG_USB_OTG=y - -# disable frame buffer consoles since there is no framebuffer -# -# CONFIG_VGA_CONSOLE is not set -# CONFIG_FRAMEBUFFER_CONSOLE is not set -# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set - -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/2] Reapply Upstream-status: Inappropriate commits removed from standard/base
While these are not appropriate for standard/base, they are OK for
standard/intel/base.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/gpio/gpio-pca953x.c | 44 +-
drivers/spi/spi-pxa2xx-pci.c |1 +
include/DSDT.hex | 1191 ++
3 files changed, 1229 insertions(+), 7 deletions(-)
create mode 100644 include/DSDT.hex
diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
index 30798bb..fad258e 100644
--- a/drivers/gpio/gpio-pca953x.c
+++ b/drivers/gpio/gpio-pca953x.c
@@ -80,12 +80,6 @@ static const struct i2c_device_id pca953x_id[] = {
};
MODULE_DEVICE_TABLE(i2c, pca953x_id);
-static const struct acpi_device_id pca953x_acpi_ids[] = {
- { "INT3491", 16 | PCA953X_TYPE | PCA_INT, },
- { }
-};
-MODULE_DEVICE_TABLE(acpi, pca953x_acpi_ids);
-
#define MAX_BANK 5
#define BANK_SZ 8
@@ -112,6 +106,35 @@ struct pca953x_chip {
unsigned long driver_data;
};
+struct pca953x_info {
+ kernel_ulong_t driver_data;
+ void (*setup)(struct pca953x_chip *chip);
+};
+
+static void pca953x_setup_int3491(struct pca953x_chip *chip)
+{
+ struct acpi_device *adev = ACPI_COMPANION(>client->dev);
+ unsigned int uid;
+
+ if (kstrtouint(acpi_device_uid(adev), 0, ) || !uid--)
+ return;
+
+ chip->gpio_start = 8 /* sch_gpio */ +
+ 8 /* gpio-dwapb */ +
+ 16 /* pca9535 */ * uid;
+}
+
+static const struct pca953x_info pca953x_info_int3491 = {
+ .driver_data = 16 | PCA953X_TYPE | PCA_INT,
+ .setup = pca953x_setup_int3491,
+};
+
+static const struct acpi_device_id pca953x_acpi_ids[] = {
+ { "INT3491", (kernel_ulong_t)_info_int3491 },
+ { }
+};
+MODULE_DEVICE_TABLE(acpi, pca953x_acpi_ids);
+
static inline struct pca953x_chip *to_pca(struct gpio_chip *gc)
{
return container_of(gc, struct pca953x_chip, gpio_chip);
@@ -723,12 +746,19 @@ static int pca953x_probe(struct i2c_client *client,
chip->driver_data = id->driver_data;
} else {
const struct acpi_device_id *id;
+ const struct pca953x_info *info;
id = acpi_match_device(pca953x_acpi_ids, >dev);
if (!id)
return -ENODEV;
- chip->driver_data = id->driver_data;
+ info = (struct pca953x_info *)id->driver_data;
+ if (!info)
+ return -ENODEV;
+
+ chip->driver_data = info->driver_data;
+ if (info->setup)
+ info->setup(chip);
}
chip->chip_type = PCA_CHIP_TYPE(chip->driver_data);
diff --git a/drivers/spi/spi-pxa2xx-pci.c b/drivers/spi/spi-pxa2xx-pci.c
index d19d7f2..562ffc1 100644
--- a/drivers/spi/spi-pxa2xx-pci.c
+++ b/drivers/spi/spi-pxa2xx-pci.c
@@ -169,6 +169,7 @@ static int pxa2xx_spi_pci_probe(struct pci_dev *dev,
memset(, 0, sizeof(pi));
pi.parent = >dev;
pi.name = "pxa2xx-spi";
+ pi.fwnode = dev->dev.fwnode;
pi.id = ssp->port_id;
pi.data = _pdata;
pi.size_data = sizeof(spi_pdata);
diff --git a/include/DSDT.hex b/include/DSDT.hex
new file mode 100644
index 000..b1e2960
--- /dev/null
+++ b/include/DSDT.hex
@@ -0,0 +1,1191 @@
+/*
+ * Copyright (c) 2013 Intel Corporation. All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright notice,
this
+ * list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright notice,
+ * this list of conditions and the following disclaimer in the documentation
+ * and/or other materials provided with the distribution.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED
+ * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+ * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+
+/*
+ *
+ * Intel ACPI Component Architecture
+ * ASL+ Optimizing Compiler version 20150515-64
+ * Copyright (c) 2000 - 2015 Intel Corpor
[linux-yocto] [PATCH 1/2] Revert Upstream-status: Inappropriate commits in standard/base
This reverts the following commits:
* c39f26cd "acpi: added a custom DSDT file."
* 94bfb66b "gpio: pca953x: provide GPIO base based on _UID"
* 2fb3159a "spi-pxa2xx: fixed ACPI-based enumeration of SPI devices."
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/gpio/gpio-pca953x.c | 44 +-
drivers/spi/spi-pxa2xx-pci.c |1 -
include/DSDT.hex | 1191 --
3 files changed, 7 insertions(+), 1229 deletions(-)
delete mode 100644 include/DSDT.hex
diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
index fad258e..30798bb 100644
--- a/drivers/gpio/gpio-pca953x.c
+++ b/drivers/gpio/gpio-pca953x.c
@@ -80,6 +80,12 @@ static const struct i2c_device_id pca953x_id[] = {
};
MODULE_DEVICE_TABLE(i2c, pca953x_id);
+static const struct acpi_device_id pca953x_acpi_ids[] = {
+ { "INT3491", 16 | PCA953X_TYPE | PCA_INT, },
+ { }
+};
+MODULE_DEVICE_TABLE(acpi, pca953x_acpi_ids);
+
#define MAX_BANK 5
#define BANK_SZ 8
@@ -106,35 +112,6 @@ struct pca953x_chip {
unsigned long driver_data;
};
-struct pca953x_info {
- kernel_ulong_t driver_data;
- void (*setup)(struct pca953x_chip *chip);
-};
-
-static void pca953x_setup_int3491(struct pca953x_chip *chip)
-{
- struct acpi_device *adev = ACPI_COMPANION(>client->dev);
- unsigned int uid;
-
- if (kstrtouint(acpi_device_uid(adev), 0, ) || !uid--)
- return;
-
- chip->gpio_start = 8 /* sch_gpio */ +
- 8 /* gpio-dwapb */ +
- 16 /* pca9535 */ * uid;
-}
-
-static const struct pca953x_info pca953x_info_int3491 = {
- .driver_data = 16 | PCA953X_TYPE | PCA_INT,
- .setup = pca953x_setup_int3491,
-};
-
-static const struct acpi_device_id pca953x_acpi_ids[] = {
- { "INT3491", (kernel_ulong_t)_info_int3491 },
- { }
-};
-MODULE_DEVICE_TABLE(acpi, pca953x_acpi_ids);
-
static inline struct pca953x_chip *to_pca(struct gpio_chip *gc)
{
return container_of(gc, struct pca953x_chip, gpio_chip);
@@ -746,19 +723,12 @@ static int pca953x_probe(struct i2c_client *client,
chip->driver_data = id->driver_data;
} else {
const struct acpi_device_id *id;
- const struct pca953x_info *info;
id = acpi_match_device(pca953x_acpi_ids, >dev);
if (!id)
return -ENODEV;
- info = (struct pca953x_info *)id->driver_data;
- if (!info)
- return -ENODEV;
-
- chip->driver_data = info->driver_data;
- if (info->setup)
- info->setup(chip);
+ chip->driver_data = id->driver_data;
}
chip->chip_type = PCA_CHIP_TYPE(chip->driver_data);
diff --git a/drivers/spi/spi-pxa2xx-pci.c b/drivers/spi/spi-pxa2xx-pci.c
index 562ffc1..d19d7f2 100644
--- a/drivers/spi/spi-pxa2xx-pci.c
+++ b/drivers/spi/spi-pxa2xx-pci.c
@@ -169,7 +169,6 @@ static int pxa2xx_spi_pci_probe(struct pci_dev *dev,
memset(, 0, sizeof(pi));
pi.parent = >dev;
pi.name = "pxa2xx-spi";
- pi.fwnode = dev->dev.fwnode;
pi.id = ssp->port_id;
pi.data = _pdata;
pi.size_data = sizeof(spi_pdata);
diff --git a/include/DSDT.hex b/include/DSDT.hex
deleted file mode 100644
index b1e2960..000
--- a/include/DSDT.hex
+++ /dev/null
@@ -1,1191 +0,0 @@
-/*
- * Copyright (c) 2013 Intel Corporation. All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions are met:
- *
- * 1. Redistributions of source code must retain the above copyright notice,
this
- * list of conditions and the following disclaimer.
- *
- * 2. Redistributions in binary form must reproduce the above copyright notice,
- * this list of conditions and the following disclaimer in the documentation
- * and/or other materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND
- * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED
- * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
- * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
- * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
- * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
- * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
- * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY,
- * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SU
[linux-yocto] [PATCH 0/2] Fix standard/base pollution
Hi Bruce, Saul, A while back before we created the standard/intel/base branches some patches that were not appropriate for standard/base were merged into the branch and caused bug [YOCTO #9587]. This patch set aims to fix that. The first patch reverts the inappropriate patches in standard/base. The second patch reverts the revert and is intended for standard/intel/base after the first revert patch waterfalls into it. I know this is kind of kludgey but I believe its the right thing to do. Let me know if you think otherwise. Thanks, Cal California Sullivan (2): Revert Upstream-status: Inappropriate commits in standard/base Reapply Upstream-status: Inappropriate commits removed from standard/base -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 4/4] common-pc-drivers.cfg: Remove I2O configs
The dependencies for these configurations were not being met as the drivers were moved to staging. This was causing warnings with the new kernel tools. Rather than satisfying the dependencies and building a bunch of new things we probably don't need, just remove the config options. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/common-pc/common-pc-drivers.cfg | 7 --- 1 file changed, 7 deletions(-) diff --git a/bsp/common-pc/common-pc-drivers.cfg b/bsp/common-pc/common-pc-drivers.cfg index cea6a99..a783744 100644 --- a/bsp/common-pc/common-pc-drivers.cfg +++ b/bsp/common-pc/common-pc-drivers.cfg @@ -58,11 +58,4 @@ CONFIG_SATA_AHCI=y CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_FD=m -CONFIG_I2O=m -CONFIG_I2O_BLOCK=m -CONFIG_I2O_CONFIG=m -CONFIG_I2O_CONFIG_OLD_IOCTL=y -CONFIG_I2O_PROC=m -CONFIG_I2O_SCSI=m - CONFIG_EEPROM_AT24=m -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/4] features: Fix dependencies and =m vs =y discrepancies for corei7
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 <california.l.sulli...@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com> --- 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 -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/4] intel-core2-32.cfg: Explicitly disable CONFIG_64BIT
The new kernel tools do not automagically do this, causing dependency issues and architecture mismatch errors. Explicitly disable the CONFIG to fix it. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com> --- bsp/intel-common/intel-core2-32.cfg | 3 +++ 1 file changed, 3 insertions(+) diff --git a/bsp/intel-common/intel-core2-32.cfg b/bsp/intel-common/intel-core2-32.cfg index ab004ea..dc5536c 100644 --- a/bsp/intel-common/intel-core2-32.cfg +++ b/bsp/intel-common/intel-core2-32.cfg @@ -1,3 +1,6 @@ +# Must explicitly disable 64BIT +# CONFIG_64BIT is not set + CONFIG_MCORE2=y CONFIG_PROCESSOR_SELECT=y -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/4][yocto-4.1] Fix kernel_configcheck warnings for core2 and corei7
This is a backport of a few patches from the yocto-4.4 branch and one new patch for yocto-4.1 specifically. These fix the warnings we get with the new kernel tools for these two BSPs. Still to come is intel-quark fixes for both branches. Thanks, Cal Sullivan California Sullivan (4): features: Add 6lowpan feature and add it where necessary intel-core2-32.cfg: Explicitly disable CONFIG_64BIT features: Fix dependencies and =m vs =y discrepancies for corei7 common-pc-drivers.cfg: Remove I2O configs bsp/common-pc/common-pc-drivers.cfg | 7 --- bsp/intel-common/intel-core2-32.cfg | 3 +++ features/6lowpan/6lowpan.cfg| 7 +++ features/6lowpan/6lowpan.scc| 4 features/bluetooth/bluetooth.cfg| 7 ++- features/bluetooth/bluetooth.scc| 2 ++ features/ieee802154/ieee802154.cfg | 2 +- features/ieee802154/ieee802154.scc | 2 ++ 8 files changed, 25 insertions(+), 9 deletions(-) create mode 100644 features/6lowpan/6lowpan.cfg create mode 100644 features/6lowpan/6lowpan.scc -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/4] features: Add 6lowpan feature and add it where necessary
For now just add the minimum configuration necessary to support other 6LoWPAN options we are already trying to enable. Fixes some configuration warnings that occur due to missing dependencies. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com> --- features/6lowpan/6lowpan.cfg | 7 +++ features/6lowpan/6lowpan.scc | 4 features/bluetooth/bluetooth.scc | 2 ++ features/ieee802154/ieee802154.scc | 2 ++ 4 files changed, 15 insertions(+) create mode 100644 features/6lowpan/6lowpan.cfg create mode 100644 features/6lowpan/6lowpan.scc diff --git a/features/6lowpan/6lowpan.cfg b/features/6lowpan/6lowpan.cfg new file mode 100644 index 000..abac6b1 --- /dev/null +++ b/features/6lowpan/6lowpan.cfg @@ -0,0 +1,7 @@ +# Dependencies +CONFIG_NET=y +CONFIG_INET=y +CONFIG_IPV6=y + +# Feature +CONFIG_6LOWPAN=m diff --git a/features/6lowpan/6lowpan.scc b/features/6lowpan/6lowpan.scc new file mode 100644 index 000..f3035d9 --- /dev/null +++ b/features/6lowpan/6lowpan.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION "Enable 6LoWPAN support" +define KFEATURE_COMPATIBILITY board + +kconf hardware 6lowpan.cfg diff --git a/features/bluetooth/bluetooth.scc b/features/bluetooth/bluetooth.scc index 53d000e..55a4ba9 100644 --- a/features/bluetooth/bluetooth.scc +++ b/features/bluetooth/bluetooth.scc @@ -1 +1,3 @@ kconf hardware bluetooth.cfg + +include features/6lowpan/6lowpan.scc diff --git a/features/ieee802154/ieee802154.scc b/features/ieee802154/ieee802154.scc index 2f40044..f8f18f8 100644 --- a/features/ieee802154/ieee802154.scc +++ b/features/ieee802154/ieee802154.scc @@ -1 +1,3 @@ kconf hardware ieee802154.cfg + +include features/6lowpan/6lowpan.scc -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/3] intel-core2-32.cfg: Explicitly disable CONFIG_64BIT
The new kernel tools do not automagically do this, causing dependency issues and architecture mismatch errors. Explicitly disable the CONFIG to fix it. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-core2-32.cfg | 3 +++ 1 file changed, 3 insertions(+) diff --git a/bsp/intel-common/intel-core2-32.cfg b/bsp/intel-common/intel-core2-32.cfg index b106c76..2b3651e 100644 --- a/bsp/intel-common/intel-core2-32.cfg +++ b/bsp/intel-common/intel-core2-32.cfg @@ -1,3 +1,6 @@ +# Must explicitly disable 64BIT +# CONFIG_64BIT is not set + CONFIG_MCORE2=y # max available for this processory family -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/3] kver: bump to v4.4.18
Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- kver | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kver b/kver index 8f2c70f..036594b 100644 --- a/kver +++ b/kver @@ -1 +1 @@ -v4.4.15 +v4.4.18 -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/3] core2 architecture mismatch and configuration warning fixes
Hi Bruce, I missed some things with my last set of patches. With this set I don't see any more warnings with the new kernel tools in my local testing. Please apply to 4.4 and master. Hopefully this is the last set! Thanks, Cal Sullivan California Sullivan (3): features: Fix dependencies and =m vs =y discrepancies for corei7 intel-core2-32.cfg: Explicitly disable CONFIG_64BIT kver: bump to v4.4.18 bsp/intel-common/intel-core2-32.cfg | 3 +++ features/bluetooth/bluetooth.cfg| 7 ++- features/ieee802154/ieee802154.cfg | 2 +- kver| 2 +- 4 files changed, 11 insertions(+), 3 deletions(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/1] Fix i915 merge
Eric, Bruce, please make sure my strategy with this fix is sane before merging. If it is, please apply it to standard/intel/base and merge into all the other intel branches. 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(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/1] drm/i915: Fix i915 merge with v4.4.16
Since we have i915 code much newer than 4.4, stable backports to this
area don't work well. There were some errors in the merge which caused
compilation failure.
For this resolution I essentially reverted the i915 changes from stable
and reapplied the patches that we did not already have but from master.
All the patches applied cleanly and we can now compile.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
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(-)
diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
index 08f01f4..853b155 100644
--- a/drivers/gpu/drm/i915/i915_reg.h
+++ b/drivers/gpu/drm/i915/i915_reg.h
@@ -7506,6 +7506,8 @@ enum skl_disp_power_wells {
#define TRANS_CLK_SEL_DISABLED(0x0<<29)
#define TRANS_CLK_SEL_PORT(x) (((x)+1)<<29)
+#define CDCLK_FREQ _MMIO(0x46200)
+
#define _TRANSA_MSA_MISC 0x60410
#define _TRANSB_MSA_MISC 0x61410
#define _TRANSC_MSA_MISC 0x62410
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index a3fc494..d92960c 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -4934,13 +4934,15 @@ static void intel_edp_panel_vdd_sanitize(struct
intel_dp *intel_dp)
void intel_dp_encoder_reset(struct drm_encoder *encoder)
{
- struct intel_dp *intel_dp;
+ struct drm_i915_private *dev_priv = to_i915(encoder->dev);
+ struct intel_dp *intel_dp = enc_to_intel_dp(encoder);
+
+ if (!HAS_DDI(dev_priv))
+ intel_dp->DP = I915_READ(intel_dp->output_reg);
if (to_intel_encoder(encoder)->type != INTEL_OUTPUT_EDP)
return;
- intel_dp = enc_to_intel_dp(encoder);
-
pps_lock(intel_dp);
/*
@@ -5012,9 +5014,6 @@ intel_dp_hpd_pulse(struct intel_digital_port
*intel_dig_port, bool long_hpd)
intel_display_power_get(dev_priv, power_domain);
if (long_hpd) {
- /* indicate that we need to restart link training */
- intel_dp->train_set_valid = false;
-
intel_dp_long_pulse(intel_dp->attached_connector);
if (intel_dp->is_mst)
ret = IRQ_HANDLED;
diff --git a/drivers/gpu/drm/i915/intel_dp_link_training.c
b/drivers/gpu/drm/i915/intel_dp_link_training.c
index 0b8eefc..60fb39c 100644
--- a/drivers/gpu/drm/i915/intel_dp_link_training.c
+++ b/drivers/gpu/drm/i915/intel_dp_link_training.c
@@ -85,8 +85,7 @@ static bool
intel_dp_reset_link_train(struct intel_dp *intel_dp,
uint8_t dp_train_pat)
{
- if (!intel_dp->train_set_valid)
- memset(intel_dp->train_set, 0, sizeof(intel_dp->train_set));
+ memset(intel_dp->train_set, 0, sizeof(intel_dp->train_set));
intel_dp_set_signal_levels(intel_dp);
return intel_dp_set_link_train(intel_dp, dp_train_pat);
}
@@ -161,23 +160,6 @@ intel_dp_link_training_clock_recovery(struct intel_dp
*intel_dp)
break;
}
- /*
-* if we used previously trained voltage and pre-emphasis values
-* and we don't get clock recovery, reset link training values
-*/
- if (intel_dp->train_set_valid) {
- DRM_DEBUG_KMS("clock recovery not ok, reset");
- /* clear the flag as we are not reusing train set */
- intel_dp->train_set_valid = false;
- if (!intel_dp_reset_link_train(intel_dp,
- DP_TRAINING_PATTERN_1 |
-
DP_LINK_SCRAMBLING_DISABLE)) {
- DRM_ERROR("failed to enable link training\n");
- return;
- }
- continue;
- }
-
/* Check to see if we've tried the max voltage */
for (i = 0; i < intel_dp->lane_count; i++)
if ((intel_dp->train_set[i] &
DP_TRAIN_MAX_SWING_REACHED) == 0)
@@ -284,7 +266,6 @@ intel_dp_link_training_channel_equalization(struct intel_dp
*intel_dp)
/* Make sure clock is still ok */
if (!drm_dp_clock_recovery_ok(link_status,
intel_dp->lane_count)) {
- intel_dp->train_set_valid = false;
intel_dp_link_training_clock_recovery(intel_dp);
intel_dp_set_link_
[linux-yocto] [PATCH 0/3] Fix kernel_configcheck warnings
Hi Bruce, This set of patches should fix the warnings we see with the new kernel tools. Please apply them to 4.4 and master branches of the yocto-kernel-cache. Thanks, Cal Sullivan California Sullivan (3): features: Add 6lowpan feature and add it where necessary features/iio: Set IIO_BUFFER_CB to =m instead of =y features: Create mfd-intel-lpss feature and use where appropriate features/6lowpan/6lowpan.cfg | 7 +++ features/6lowpan/6lowpan.scc | 5 + features/bluetooth/bluetooth.scc | 2 ++ features/ieee802154/ieee802154.scc | 2 ++ features/iio/iio.cfg | 2 +- features/mfd/mfd-intel-lpss.cfg| 3 +++ features/mfd/mfd-intel-lpss.scc| 4 features/soc/broxton/broxton.cfg | 4 features/soc/broxton/broxton.scc | 3 +++ features/soc/skylake/skylake.cfg | 5 + features/soc/skylake/skylake.scc | 3 +++ 11 files changed, 31 insertions(+), 9 deletions(-) create mode 100644 features/6lowpan/6lowpan.cfg create mode 100644 features/6lowpan/6lowpan.scc create mode 100644 features/mfd/mfd-intel-lpss.cfg create mode 100644 features/mfd/mfd-intel-lpss.scc -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/3] features: Create mfd-intel-lpss feature and use where appropriate
No need to have these similar configurations spread all around. Also solves a warning where skylake tried to set MFD_INTEL_LPSS to build as a module, but MFD_INTEL_LPSS_PCI in broxton hits a select and forces it to built in. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/mfd/mfd-intel-lpss.cfg | 3 +++ features/mfd/mfd-intel-lpss.scc | 4 features/soc/broxton/broxton.cfg | 4 features/soc/broxton/broxton.scc | 3 +++ features/soc/skylake/skylake.cfg | 5 + features/soc/skylake/skylake.scc | 3 +++ 6 files changed, 14 insertions(+), 8 deletions(-) create mode 100644 features/mfd/mfd-intel-lpss.cfg create mode 100644 features/mfd/mfd-intel-lpss.scc diff --git a/features/mfd/mfd-intel-lpss.cfg b/features/mfd/mfd-intel-lpss.cfg new file mode 100644 index 000..ad7e6a5 --- /dev/null +++ b/features/mfd/mfd-intel-lpss.cfg @@ -0,0 +1,3 @@ +CONFIG_MFD_INTEL_LPSS=y +CONFIG_MFD_INTEL_LPSS_PCI=y +CONFIG_MFD_INTEL_LPSS_ACPI=y diff --git a/features/mfd/mfd-intel-lpss.scc b/features/mfd/mfd-intel-lpss.scc new file mode 100644 index 000..f1e18b1 --- /dev/null +++ b/features/mfd/mfd-intel-lpss.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION "Intel LPSS support for Skylake and Broxton" +define KFEATURE_COMPATIBILITY board + +kconf hardware mfd-intel-lpss.cfg diff --git a/features/soc/broxton/broxton.cfg b/features/soc/broxton/broxton.cfg index 0b4e824..446bd54 100644 --- a/features/soc/broxton/broxton.cfg +++ b/features/soc/broxton/broxton.cfg @@ -9,10 +9,6 @@ CONFIG_MMC_SDHCI_PCI=y CONFIG_MMC_SDHCI_ACPI=y CONFIG_MMC_SDHCI_PLTFM=y -# Skylake/Broxton LPSS support -CONFIG_MFD_INTEL_LPSS_ACPI=y -CONFIG_MFD_INTEL_LPSS_PCI=y - # LPSS DMA support CONFIG_DMA_VIRTUAL_CHANNELS=y CONFIG_INTEL_IDMA64=y diff --git a/features/soc/broxton/broxton.scc b/features/soc/broxton/broxton.scc index 2951b7d..b80ee80 100644 --- a/features/soc/broxton/broxton.scc +++ b/features/soc/broxton/broxton.scc @@ -17,4 +17,7 @@ include features/usb/usb-typec.scc include features/mei/mei-me.scc +# Enable Skylake/Broxton LPSS support +include features/mfd/mfd-intel-lpss.scc + kconf hardware broxton.cfg diff --git a/features/soc/skylake/skylake.cfg b/features/soc/skylake/skylake.cfg index 77f0efa..954c9f8 100644 --- a/features/soc/skylake/skylake.cfg +++ b/features/soc/skylake/skylake.cfg @@ -1,7 +1,4 @@ -# Skylake/Broxton LPSS support -CONFIG_MFD_INTEL_LPSS=m -CONFIG_MFD_INTEL_LPSS_ACPI=m -CONFIG_MFD_INTEL_LPSS_PCI=m +# IDMA support for LPSS CONFIG_INTEL_IDMA64=m # Additional power management support diff --git a/features/soc/skylake/skylake.scc b/features/soc/skylake/skylake.scc index bc59f22..4961901 100644 --- a/features/soc/skylake/skylake.scc +++ b/features/soc/skylake/skylake.scc @@ -9,4 +9,7 @@ include features/i2c/i2c.scc # Enable mac 80211 + WLAN support include features/mac80211/mac80211.scc +# Enable Skylake/Broxton LPSS support +include features/mfd/mfd-intel-lpss.scc + kconf hardware skylake.cfg -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/3] features/iio: Set IIO_BUFFER_CB to =m instead of =y
CONFIG_IIO_BUFFER_CB is a tristate and CONFIG_IIO is set to =m, so CONFIG_IIO_BUFFER_CB gets forced to =m anyway. Fixes a kernel_configcheck warning we get with the new tools. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/iio/iio.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features/iio/iio.cfg b/features/iio/iio.cfg index 6ddc452..89b881d 100644 --- a/features/iio/iio.cfg +++ b/features/iio/iio.cfg @@ -29,7 +29,7 @@ CONFIG_HID_SENSOR_HUB=m CONFIG_IIO=m CONFIG_IIO_BUFFER=y -CONFIG_IIO_BUFFER_CB=y +CONFIG_IIO_BUFFER_CB=m CONFIG_IIO_KFIFO_BUF=m CONFIG_IIO_TRIGGERED_BUFFER=m CONFIG_IIO_TRIGGER=y -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/3] features: Add 6lowpan feature and add it where necessary
For now just add the minimum configuration necessary to support other 6LoWPAN options we are already trying to enable. Fixes some configuration warnings that occur due to missing dependencies. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/6lowpan/6lowpan.cfg | 7 +++ features/6lowpan/6lowpan.scc | 5 + features/bluetooth/bluetooth.scc | 2 ++ features/ieee802154/ieee802154.scc | 2 ++ 4 files changed, 16 insertions(+) create mode 100644 features/6lowpan/6lowpan.cfg create mode 100644 features/6lowpan/6lowpan.scc diff --git a/features/6lowpan/6lowpan.cfg b/features/6lowpan/6lowpan.cfg new file mode 100644 index 000..abac6b1 --- /dev/null +++ b/features/6lowpan/6lowpan.cfg @@ -0,0 +1,7 @@ +# Dependencies +CONFIG_NET=y +CONFIG_INET=y +CONFIG_IPV6=y + +# Feature +CONFIG_6LOWPAN=m diff --git a/features/6lowpan/6lowpan.scc b/features/6lowpan/6lowpan.scc new file mode 100644 index 000..9601396 --- /dev/null +++ b/features/6lowpan/6lowpan.scc @@ -0,0 +1,5 @@ +define KFEATURE_DESCRIPTION "Enable 6LoWPAN support" +define KFEATURE_COMPATIBILITY board + +kconf hardware 6lowpan.cfg + diff --git a/features/bluetooth/bluetooth.scc b/features/bluetooth/bluetooth.scc index 53d000e..55a4ba9 100644 --- a/features/bluetooth/bluetooth.scc +++ b/features/bluetooth/bluetooth.scc @@ -1 +1,3 @@ kconf hardware bluetooth.cfg + +include features/6lowpan/6lowpan.scc diff --git a/features/ieee802154/ieee802154.scc b/features/ieee802154/ieee802154.scc index 2f40044..f8f18f8 100644 --- a/features/ieee802154/ieee802154.scc +++ b/features/ieee802154/ieee802154.scc @@ -1 +1,3 @@ kconf hardware ieee802154.cfg + +include features/6lowpan/6lowpan.scc -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 07/10] UPSTREAM: clk: pwm: Use pwm_get_args() where appropriate
From: Boris Brezillon <boris.brezil...@free-electrons.com>
The PWM framework has clarified the concept of reference PWM config (the
platform dependent config retrieved from the DT or the PWM lookup table)
and real PWM state.
Use pwm_get_args() when the PWM user wants to retrieve this reference
config and not the current state.
This is part of the rework allowing the PWM framework to support
hardware readout and expose real PWM state even when the PWM has just
been requested (before the user calls pwm_config/enable/disable()).
Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com>
Acked-by: Stephen Boyd <sb...@codeaurora.org>
Signed-off-by: Thierry Reding <thierry.red...@gmail.com>
(cherry picked from commit dd0b38b7ca0d8c8aadcf8a17d7c90d36ab8ab6e4)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/clk/clk-pwm.c | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/drivers/clk/clk-pwm.c b/drivers/clk/clk-pwm.c
index 328fcfc..9897eb1 100644
--- a/drivers/clk/clk-pwm.c
+++ b/drivers/clk/clk-pwm.c
@@ -59,6 +59,7 @@ static int clk_pwm_probe(struct platform_device *pdev)
struct clk_init_data init;
struct clk_pwm *clk_pwm;
struct pwm_device *pwm;
+ struct pwm_args pargs;
const char *clk_name;
struct clk *clk;
int ret;
@@ -71,22 +72,28 @@ static int clk_pwm_probe(struct platform_device *pdev)
if (IS_ERR(pwm))
return PTR_ERR(pwm);
- if (!pwm->period) {
+ pwm_get_args(pwm, );
+ if (!pargs.period) {
dev_err(>dev, "invalid PWM period\n");
return -EINVAL;
}
if (of_property_read_u32(node, "clock-frequency", _pwm->fixed_rate))
- clk_pwm->fixed_rate = NSEC_PER_SEC / pwm->period;
+ clk_pwm->fixed_rate = NSEC_PER_SEC / pargs.period;
- if (pwm->period != NSEC_PER_SEC / clk_pwm->fixed_rate &&
- pwm->period != DIV_ROUND_UP(NSEC_PER_SEC, clk_pwm->fixed_rate)) {
+ if (pargs.period != NSEC_PER_SEC / clk_pwm->fixed_rate &&
+ pargs.period != DIV_ROUND_UP(NSEC_PER_SEC, clk_pwm->fixed_rate)) {
dev_err(>dev,
"clock-frequency does not match PWM period\n");
return -EINVAL;
}
- ret = pwm_config(pwm, (pwm->period + 1) >> 1, pwm->period);
+ /*
+* FIXME: pwm_apply_args() should be removed when switching to the
+* atomic PWM API.
+*/
+ pwm_apply_args(pwm);
+ ret = pwm_config(pwm, (pargs.period + 1) >> 1, pargs.period);
if (ret < 0)
return ret;
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 10/10] UPSTREAM: hwmon: pwm-fan: Use pwm_get_args() where appropriate
From: Boris Brezillon <boris.brezil...@free-electrons.com>
The PWM framework has clarified the concept of reference PWM config (the
platform dependent config retrieved from the DT or the PWM lookup table)
and real PWM state.
Use pwm_get_args() when the PWM user wants to retrieve this reference
config and not the current state.
This is part of the rework allowing the PWM framework to support
hardware readout and expose real PWM state even when the PWM has just
been requested (before the user calls pwm_config/enable/disable()).
Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com>
Acked-by: Kamil Debski <k.deb...@samsung.com>
Signed-off-by: Thierry Reding <thierry.red...@gmail.com>
(cherry picked from commit 2289711c9d4d588954ff86a06685f1579bf6c446)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/hwmon/pwm-fan.c | 26 --
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/drivers/hwmon/pwm-fan.c b/drivers/hwmon/pwm-fan.c
index 3e23003..f9af393 100644
--- a/drivers/hwmon/pwm-fan.c
+++ b/drivers/hwmon/pwm-fan.c
@@ -40,15 +40,18 @@ struct pwm_fan_ctx {
static int __set_pwm(struct pwm_fan_ctx *ctx, unsigned long pwm)
{
+ struct pwm_args pargs;
unsigned long duty;
int ret = 0;
+ pwm_get_args(ctx->pwm, );
+
mutex_lock(>lock);
if (ctx->pwm_value == pwm)
goto exit_set_pwm_err;
- duty = DIV_ROUND_UP(pwm * (ctx->pwm->period - 1), MAX_PWM);
- ret = pwm_config(ctx->pwm, duty, ctx->pwm->period);
+ duty = DIV_ROUND_UP(pwm * (pargs.period - 1), MAX_PWM);
+ ret = pwm_config(ctx->pwm, duty, pargs.period);
if (ret)
goto exit_set_pwm_err;
@@ -215,6 +218,7 @@ static int pwm_fan_probe(struct platform_device *pdev)
{
struct thermal_cooling_device *cdev;
struct pwm_fan_ctx *ctx;
+ struct pwm_args pargs;
struct device *hwmon;
int duty_cycle;
int ret;
@@ -233,11 +237,19 @@ static int pwm_fan_probe(struct platform_device *pdev)
platform_set_drvdata(pdev, ctx);
+ /*
+* FIXME: pwm_apply_args() should be removed when switching to the
+* atomic PWM API.
+*/
+ pwm_apply_args(ctx->pwm);
+
/* Set duty cycle to maximum allowed */
- duty_cycle = ctx->pwm->period - 1;
+ pwm_get_args(ctx->pwm, );
+
+ duty_cycle = pargs.period - 1;
ctx->pwm_value = MAX_PWM;
- ret = pwm_config(ctx->pwm, duty_cycle, ctx->pwm->period);
+ ret = pwm_config(ctx->pwm, duty_cycle, pargs.period);
if (ret) {
dev_err(>dev, "Failed to configure PWM\n");
return ret;
@@ -303,14 +315,16 @@ static int pwm_fan_suspend(struct device *dev)
static int pwm_fan_resume(struct device *dev)
{
struct pwm_fan_ctx *ctx = dev_get_drvdata(dev);
+ struct pwm_args pargs;
unsigned long duty;
int ret;
if (ctx->pwm_value == 0)
return 0;
- duty = DIV_ROUND_UP(ctx->pwm_value * (ctx->pwm->period - 1), MAX_PWM);
- ret = pwm_config(ctx->pwm, duty, ctx->pwm->period);
+ pwm_get_args(ctx->pwm, );
+ duty = DIV_ROUND_UP(ctx->pwm_value * (pargs.period - 1), MAX_PWM);
+ ret = pwm_config(ctx->pwm, duty, pargs.period);
if (ret)
return ret;
return pwm_enable(ctx->pwm);
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 09/10] UPSTREAM: pwm: Use pwm_get/set_xxx() helpers where appropriate
From: Boris Brezillon <boris.brezil...@free-electrons.com>
Use pwm_get/set_xxx() helpers instead of directly accessing the pwm->xxx
field. Doing that will ease adaptation of the PWM framework to support
atomic update.
Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com>
Signed-off-by: Thierry Reding <thierry.red...@gmail.com>
CONFLICTS:
This patch originally fixed up omap-dmtimer as well, which does not
yet exist in the 4.4 kernel.
(cherry picked from commit 4b58896f72176b781816a9e14dcea5f755b19b5c)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/pwm/pwm-crc.c | 2 +-
drivers/pwm/pwm-lpc18xx-sct.c | 2 +-
drivers/pwm/pwm-sun4i.c | 3 ++-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/pwm/pwm-crc.c b/drivers/pwm/pwm-crc.c
index 7101c70..bd0ebd0 100644
--- a/drivers/pwm/pwm-crc.c
+++ b/drivers/pwm/pwm-crc.c
@@ -75,7 +75,7 @@ static int crc_pwm_config(struct pwm_chip *c, struct
pwm_device *pwm,
return -EINVAL;
}
- if (pwm->period != period_ns) {
+ if (pwm_get_period(pwm) != period_ns) {
int clk_div;
/* changing the clk divisor, need to disable fisrt */
diff --git a/drivers/pwm/pwm-lpc18xx-sct.c b/drivers/pwm/pwm-lpc18xx-sct.c
index 9163085..52aba84 100644
--- a/drivers/pwm/pwm-lpc18xx-sct.c
+++ b/drivers/pwm/pwm-lpc18xx-sct.c
@@ -249,7 +249,7 @@ static int lpc18xx_pwm_enable(struct pwm_chip *chip, struct
pwm_device *pwm)
LPC18XX_PWM_EVSTATEMSK(lpc18xx_data->duty_event),
LPC18XX_PWM_EVSTATEMSK_ALL);
- if (pwm->polarity == PWM_POLARITY_NORMAL) {
+ if (pwm_get_polarity(pwm) == PWM_POLARITY_NORMAL) {
set_event = lpc18xx_pwm->period_event;
clear_event = lpc18xx_data->duty_event;
res_action = LPC18XX_PWM_RES_SET;
diff --git a/drivers/pwm/pwm-sun4i.c b/drivers/pwm/pwm-sun4i.c
index 67af9f6..03a99a5 100644
--- a/drivers/pwm/pwm-sun4i.c
+++ b/drivers/pwm/pwm-sun4i.c
@@ -354,7 +354,8 @@ static int sun4i_pwm_probe(struct platform_device *pdev)
val = sun4i_pwm_readl(pwm, PWM_CTRL_REG);
for (i = 0; i < pwm->chip.npwm; i++)
if (!(val & BIT_CH(PWM_ACT_STATE, i)))
- pwm->chip.pwms[i].polarity = PWM_POLARITY_INVERSED;
+ pwm_set_polarity(>chip.pwms[i],
+PWM_POLARITY_INVERSED);
clk_disable_unprepare(pwm->clk);
return 0;
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 05/10] UPSTREAM: backlight: pwm_bl: Use pwm_get_args() where appropriate
From: Boris Brezillon <boris.brezil...@free-electrons.com>
The PWM framework has clarified the concept of reference PWM config (the
platform dependent config retrieved from the DT or the PWM lookup table)
and real PWM state.
Use pwm_get_args() when the PWM user wants to retrieve this reference
config and not the current state.
This is part of the rework allowing the PWM framework to support
hardware readout and expose real PWM state even when the PWM has just
been requested (before the user calls pwm_config/enable/disable()).
Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com>
Signed-off-by: Thierry Reding <thierry.red...@gmail.com>
(cherry picked from commit 6cb9644db7364ff5d2980ccd365b8cb684145327)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/video/backlight/pwm_bl.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
index a33a290..b2b366b 100644
--- a/drivers/video/backlight/pwm_bl.c
+++ b/drivers/video/backlight/pwm_bl.c
@@ -201,6 +201,7 @@ static int pwm_backlight_probe(struct platform_device *pdev)
struct device_node *node = pdev->dev.of_node;
struct pwm_bl_data *pb;
int initial_blank = FB_BLANK_UNBLANK;
+ struct pwm_args pargs;
int ret;
if (!data) {
@@ -307,12 +308,19 @@ static int pwm_backlight_probe(struct platform_device
*pdev)
dev_dbg(>dev, "got pwm for backlight\n");
/*
+* FIXME: pwm_apply_args() should be removed when switching to
+* the atomic PWM API.
+*/
+ pwm_apply_args(pb->pwm);
+
+ /*
* The DT case will set the pwm_period_ns field to 0 and store the
* period, parsed from the DT, in the PWM device. For the non-DT case,
* set the period from platform data if it has not already been set
* via the PWM lookup table.
*/
- pb->period = pwm_get_period(pb->pwm);
+ pwm_get_args(pb->pwm, );
+ pb->period = pargs.period;
if (!pb->period && (data->pwm_period_ns > 0))
pb->period = data->pwm_period_ns;
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 04/10] UPSTREAM: backlight: pwm_bl: Remove useless call to pwm_set_period()
From: Boris BREZILLON <boris.brezil...@free-electrons.com>
The PWM period will be set when calling pwm_config. Remove this useless
call to pwm_set_period(), which might mess up the internal PWM state.
Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com>
Acked-by: Lee Jones <lee.jo...@linaro.org>
Signed-off-by: Thierry Reding <thierry.red...@gmail.com>
(cherry picked from commit 7f044b09b68d36811518c55f736a20648e8ed6e2)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/video/backlight/pwm_bl.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
index 64f9e1b..a33a290 100644
--- a/drivers/video/backlight/pwm_bl.c
+++ b/drivers/video/backlight/pwm_bl.c
@@ -313,10 +313,8 @@ static int pwm_backlight_probe(struct platform_device
*pdev)
* via the PWM lookup table.
*/
pb->period = pwm_get_period(pb->pwm);
- if (!pb->period && (data->pwm_period_ns > 0)) {
+ if (!pb->period && (data->pwm_period_ns > 0))
pb->period = data->pwm_period_ns;
- pwm_set_period(pb->pwm, data->pwm_period_ns);
- }
pb->lth_brightness = data->lth_brightness * (pb->period / pb->scale);
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 08/10] UPSTREAM: pwm: rcar: Make use of pwm_is_enabled()
From: Boris BREZILLON <boris.brezil...@free-electrons.com>
Commit 5c31252c4a86 ("pwm: Add the pwm_is_enabled() helper") introduced
a new function to test whether a PWM device is enabled or not without
manipulating PWM internal fields.
Hiding this is necessary if we want to smoothly move to the atomic PWM
config approach without impacting PWM drivers. Fix this driver to use
pwm_is_enabled() instead of directly accessing the ->flags field.
Signed-off-by: Boris Brezillon <boris.brezil...@free-electrons.com>
Signed-off-by: Thierry Reding <thierry.red...@gmail.com>
(cherry picked from commit 3587c260906259632df07652743269627f408d85)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/pwm/pwm-rcar.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pwm/pwm-rcar.c b/drivers/pwm/pwm-rcar.c
index 6e99a63..70899c9 100644
--- a/drivers/pwm/pwm-rcar.c
+++ b/drivers/pwm/pwm-rcar.c
@@ -157,7 +157,7 @@ static int rcar_pwm_config(struct pwm_chip *chip, struct
pwm_device *pwm,
return div;
/* Let the core driver set pwm->period if disabled and duty_ns == 0 */
- if (!test_bit(PWMF_ENABLED, >flags) && !duty_ns)
+ if (!pwm_is_enabled(pwm) && !duty_ns)
return 0;
rcar_pwm_update(rp, RCAR_PWMCR_SYNC, RCAR_PWMCR_SYNC, RCAR_PWMCR);
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 03/10] UPSTREAM: backlight: pwm_bl: Free PWM requested by legacy API on error path
From: Vladimir Zapolskiy <vladimir_zapols...@mentor.com>
If pwm is requested by legacy pwm_request() and if the following
backlight_device_register() call fails, add pwm_free() clean-up.
Signed-off-by: Vladimir Zapolskiy <vladimir_zapols...@mentor.com>
Signed-off-by: Lee Jones <lee.jo...@linaro.org>
(cherry picked from commit 60d613d6aef4ae49988eeb3ad38af948c561db1e)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/video/backlight/pwm_bl.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
index a22c1ec..64f9e1b 100644
--- a/drivers/video/backlight/pwm_bl.c
+++ b/drivers/video/backlight/pwm_bl.c
@@ -328,6 +328,8 @@ static int pwm_backlight_probe(struct platform_device *pdev)
if (IS_ERR(bl)) {
dev_err(>dev, "failed to register backlight\n");
ret = PTR_ERR(bl);
+ if (pb->legacy)
+ pwm_free(pb->pwm);
goto err_alloc;
}
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 01/10] UPSTREAM: backlight: pwm_bl: Avoid backlight flicker when probed from DT
From: Philipp Zabel <p.za...@pengutronix.de>
If the driver is probed from the device tree, and there is a phandle
property set on it, and the enable GPIO is already configured as output,
and the backlight is currently disabled, keep it disabled.
If all these conditions are met, assume there will be some other driver
that can enable the backlight at the appropriate time.
Signed-off-by: Philipp Zabel <p.za...@pengutronix.de>
Reviewed-by: Christian Gmeiner <christian.gmei...@gmail.com>
Tested-by: Heiko Stuebner <he...@sntech.de>
Signed-off-by: Lee Jones <lee.jo...@linaro.org>
(cherry picked from 3698d7e7d221a5c90d4b55e96d0c8f98a8b4d7df)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/video/backlight/pwm_bl.c | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
index ae3c6b6..3daf9cc 100644
--- a/drivers/video/backlight/pwm_bl.c
+++ b/drivers/video/backlight/pwm_bl.c
@@ -199,6 +199,8 @@ static int pwm_backlight_probe(struct platform_device *pdev)
struct backlight_properties props;
struct backlight_device *bl;
struct pwm_bl_data *pb;
+ phandle phandle = pdev->dev.of_node->phandle;
+ int initial_blank = FB_BLANK_UNBLANK;
int ret;
if (!data) {
@@ -242,7 +244,7 @@ static int pwm_backlight_probe(struct platform_device *pdev)
pb->enabled = false;
pb->enable_gpio = devm_gpiod_get_optional(>dev, "enable",
- GPIOD_OUT_HIGH);
+ GPIOD_ASIS);
if (IS_ERR(pb->enable_gpio)) {
ret = PTR_ERR(pb->enable_gpio);
goto err_alloc;
@@ -264,12 +266,30 @@ static int pwm_backlight_probe(struct platform_device
*pdev)
pb->enable_gpio = gpio_to_desc(data->enable_gpio);
}
+ if (pb->enable_gpio) {
+ /*
+* If the driver is probed from the device tree and there is a
+* phandle link pointing to the backlight node, it is safe to
+* assume that another driver will enable the backlight at the
+* appropriate time. Therefore, if it is disabled, keep it so.
+*/
+ if (phandle &&
+ gpiod_get_direction(pb->enable_gpio) == GPIOF_DIR_OUT &&
+ gpiod_get_value(pb->enable_gpio) == 0)
+ initial_blank = FB_BLANK_POWERDOWN;
+ else
+ gpiod_direction_output(pb->enable_gpio, 1);
+ }
+
pb->power_supply = devm_regulator_get(>dev, "power");
if (IS_ERR(pb->power_supply)) {
ret = PTR_ERR(pb->power_supply);
goto err_alloc;
}
+ if (phandle && !regulator_is_enabled(pb->power_supply))
+ initial_blank = FB_BLANK_POWERDOWN;
+
pb->pwm = devm_pwm_get(>dev, NULL);
if (IS_ERR(pb->pwm) && PTR_ERR(pb->pwm) != -EPROBE_DEFER
&& !pdev->dev.of_node) {
@@ -320,6 +340,7 @@ static int pwm_backlight_probe(struct platform_device *pdev)
}
bl->props.brightness = data->dft_brightness;
+ bl->props.power = initial_blank;
backlight_update_status(bl);
platform_set_drvdata(pdev, bl);
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/1][yocto-kernel-cache][yocto-4.4] features/input: Add keyboard-gpio feature
This feature adds keyboard-gpio support to the kernel. We also add a specific implementation by default. More can be added as necessary. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/input/keyboard-gpio.cfg | 8 features/input/keyboard-gpio.scc | 6 ++ 2 files changed, 14 insertions(+) create mode 100644 features/input/keyboard-gpio.cfg create mode 100644 features/input/keyboard-gpio.scc diff --git a/features/input/keyboard-gpio.cfg b/features/input/keyboard-gpio.cfg new file mode 100644 index 000..c86a5fc --- /dev/null +++ b/features/input/keyboard-gpio.cfg @@ -0,0 +1,8 @@ +# Dependencies +CONFIG_INPUT_MISC=y + +# The main feature +CONFIG_KEYBOARD_GPIO=m + +# Implementations +CONFIG_INPUT_SOC_BUTTON_ARRAY=m diff --git a/features/input/keyboard-gpio.scc b/features/input/keyboard-gpio.scc new file mode 100644 index 000..aad85ab --- /dev/null +++ b/features/input/keyboard-gpio.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION "Enable keyboard gpio devices" +define KFEATURE_COMPATIBILITY board + +kconf hardware keyboard-gpio.cfg + +include input.scc -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/3] acpi: add support for ACPI reconfiguration notifiers
From: Octavian Purdila <octavian.purd...@intel.com>
Upstream-status: Pending
Add support for ACPI reconfiguration notifiers to allow subsystems to
react to changes in the ACPI tables that happen after the initial
enumeration. This is similar with the way dynamic device tree
notifications work.
The reconfigure notifications supported for now are device add and
device remove.
Since ACPICA allows only one table notification handler, this patch
makes the table notifier function generic and moves it out of the
sysfs specific code.
Signed-off-by: Octavian Purdila <octavian.purd...@intel.com>
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/acpi/bus.c | 9 +++
drivers/acpi/internal.h | 3 +++
drivers/acpi/scan.c | 68 -
drivers/acpi/sysfs.c| 6 ++---
include/linux/acpi.h| 18 +
5 files changed, 99 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index ca4f284..8f19ef9 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -973,6 +973,13 @@ void __init acpi_subsystem_init(void)
}
}
+static acpi_status acpi_bus_table_handler(u32 event, void *table, void
*context)
+{
+ acpi_scan_table_handler(event, table, context);
+
+ return acpi_sysfs_table_handler(event, table, context);
+}
+
static int __init acpi_bus_init(void)
{
int result;
@@ -1017,6 +1024,8 @@ static int __init acpi_bus_init(void)
* _PDC control method may load dynamic SSDT tables,
* and we need to install the table handler before that.
*/
+ status = acpi_install_table_handler(acpi_bus_table_handler, NULL);
+
acpi_sysfs_init();
acpi_early_processor_set_pdc();
diff --git a/drivers/acpi/internal.h b/drivers/acpi/internal.h
index 0f3f41c..86f74c2 100644
--- a/drivers/acpi/internal.h
+++ b/drivers/acpi/internal.h
@@ -80,6 +80,9 @@ bool acpi_queue_hotplug_work(struct work_struct *work);
void acpi_device_hotplug(struct acpi_device *adev, u32 src);
bool acpi_scan_is_offline(struct acpi_device *adev, bool uevent);
+acpi_status acpi_sysfs_table_handler(u32 event, void *table, void *context);
+void acpi_scan_table_handler(u32 event, void *table, void *context);
+
/* --
Device Node Initialization / Removal
--
*/
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index d0875f7..55b84bb 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -486,6 +486,8 @@ static void acpi_device_del(struct acpi_device *device)
device_del(>dev);
}
+static BLOCKING_NOTIFIER_HEAD(acpi_reconfig_chain);
+
static LIST_HEAD(acpi_device_del_list);
static DEFINE_MUTEX(acpi_device_del_lock);
@@ -506,6 +508,9 @@ static void acpi_device_del_work_fn(struct work_struct
*work_not_used)
mutex_unlock(_device_del_lock);
+ blocking_notifier_call_chain(_reconfig_chain,
+ACPI_RECONFIG_DEVICE_REMOVE, adev);
+
acpi_device_del(adev);
/*
* Drop references to all power resources that might have been
@@ -1668,7 +1673,7 @@ static void acpi_default_enumeration(struct acpi_device
*device)
bool is_spi_i2c_slave = false;
/*
-* Do not enemerate SPI/I2C slaves as they will be enuerated by their
+* Do not enemerate SPI/I2C slaves as they will be enumerated by their
* respective parents.
*/
INIT_LIST_HEAD(_list);
@@ -1678,6 +1683,9 @@ static void acpi_default_enumeration(struct acpi_device
*device)
if (!is_spi_i2c_slave) {
acpi_create_platform_device(device);
acpi_device_set_enumerated(device);
+ } else {
+ blocking_notifier_call_chain(_reconfig_chain,
+ACPI_RECONFIG_DEVICE_ADD, device);
}
}
@@ -1909,6 +1917,8 @@ static int acpi_bus_scan_fixed(void)
return result < 0 ? result : 0;
}
+static bool acpi_scan_initialized;
+
int __init acpi_scan_init(void)
{
int result;
@@ -1952,6 +1962,8 @@ int __init acpi_scan_init(void)
acpi_update_all_gpes();
+ acpi_scan_initialized = true;
+
out:
mutex_unlock(_scan_lock);
return result;
@@ -1995,3 +2007,57 @@ int __init __acpi_probe_device_table(struct
acpi_probe_entry *ap_head, int nr)
return count;
}
+
+struct acpi_table_events_work {
+ struct work_struct work;
+ void *table;
+ u32 event;
+};
+
+void acpi_table_events_fn(struct work_struct *work)
+{
+ struct acpi_table_events_work *tew;
+
+ tew = container_of(work, struct acpi_table_events_work, work);
+
+ if (tew->event == ACPI_TABLE_EVENT_LOAD) {
+
[linux-yocto] [PATCH 1/3] acpi: fix enumeration (visited) flags for bus rescans
From: Octavian Purdila <octavian.purd...@intel.com>
Upstream-status: Pending
If the ACPI tables changes as a result of a dinamically loaded table and
a bus rescan is required the enumeration/visited flag are not
consistent.
I2C/SPI are not directly enumerated in acpi_bus_attach(), however the
visited flag is set. This makes it impossible to check if an ACPI device
has already been enumerated by the I2C and SPI subsystems. To fix this
issue we only set the visited flags if the device is not I2C or SPI.
With this change we also need to remove setting visited to false from
acpi_bus_attach(), otherwise if we rescan already enumerated I2C/SPI
devices we try to re-enumerate them.
Note that I2C/SPI devices can be enumerated either via a scan handler
(when using PRP0001) or via regular device_attach(). In either case
the flow goes through acpi_default_enumeration() which makes it the
ideal place to mark the ACPI device as enumerated.
Signed-off-by: Octavian Purdila <octavian.purd...@intel.com>
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/acpi/scan.c | 13 +++--
include/linux/acpi.h | 18 ++
2 files changed, 25 insertions(+), 6 deletions(-)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index 78d5f02..d0875f7 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -1398,7 +1398,7 @@ void acpi_init_device_object(struct acpi_device *device,
acpi_handle handle,
acpi_bus_get_flags(device);
device->flags.match_driver = false;
device->flags.initialized = true;
- device->flags.visited = false;
+ acpi_device_clear_enumerated(device);
device_initialize(>dev);
dev_set_uevent_suppress(>dev, true);
acpi_init_coherency(device);
@@ -1675,8 +1675,10 @@ static void acpi_default_enumeration(struct acpi_device
*device)
acpi_dev_get_resources(device, _list, acpi_check_spi_i2c_slave,
_spi_i2c_slave);
acpi_dev_free_resource_list(_list);
- if (!is_spi_i2c_slave)
+ if (!is_spi_i2c_slave) {
acpi_create_platform_device(device);
+ acpi_device_set_enumerated(device);
+ }
}
static const struct acpi_device_id generic_device_ids[] = {
@@ -1743,7 +1745,7 @@ static void acpi_bus_attach(struct acpi_device *device)
acpi_bus_get_status(device);
/* Skip devices that are not present. */
if (!acpi_device_is_present(device)) {
- device->flags.visited = false;
+ acpi_device_clear_enumerated(device);
device->flags.power_manageable = 0;
return;
}
@@ -1758,7 +1760,7 @@ static void acpi_bus_attach(struct acpi_device *device)
device->flags.initialized = true;
}
- device->flags.visited = false;
+
ret = acpi_scan_attach_handler(device);
if (ret < 0)
return;
@@ -1772,7 +1774,6 @@ static void acpi_bus_attach(struct acpi_device *device)
if (!ret && device->pnp.type.platform_id)
acpi_default_enumeration(device);
}
- device->flags.visited = true;
ok:
list_for_each_entry(child, >children, node)
@@ -1864,7 +1865,7 @@ void acpi_bus_trim(struct acpi_device *adev)
*/
acpi_device_set_power(adev, ACPI_STATE_D3_COLD);
adev->flags.initialized = false;
- adev->flags.visited = false;
+ acpi_device_clear_enumerated(adev);
}
EXPORT_SYMBOL_GPL(acpi_bus_trim);
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 42adb80..ef18314 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -469,6 +469,16 @@ void acpi_walk_dep_device_list(acpi_handle handle);
struct platform_device *acpi_create_platform_device(struct acpi_device *);
#define ACPI_PTR(_ptr) (_ptr)
+static inline void acpi_device_set_enumerated(struct acpi_device *adev)
+{
+ adev->flags.visited = true;
+}
+
+static inline void acpi_device_clear_enumerated(struct acpi_device *adev)
+{
+ adev->flags.visited = false;
+}
+
#else /* !CONFIG_ACPI */
#define acpi_disabled 1
@@ -614,6 +624,14 @@ static inline enum dev_dma_attr acpi_get_dma_attr(struct
acpi_device *adev)
#define ACPI_PTR(_ptr) (NULL)
+static inline void acpi_device_set_enumerated(struct acpi_device *adev)
+{
+}
+
+static inline void acpi_device_clear_enumerated(struct acpi_device *adev)
+{
+}
+
#endif /* !CONFIG_ACPI */
#ifdef CONFIG_ACPI
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/3] i2c: add support for ACPI reconfigure notifications
From: Octavian Purdila <octavian.purd...@intel.com>
Upstream-status: Pending
This patch adds supports for I2C device enumeration and removal via
ACPI reconfiguration notifications that are send as a result of an
ACPI table load or unload operation.
Signed-off-by: Octavian Purdila <octavian.purd...@intel.com>
Reviewed-by: Mika Westerberg <mika.westerb...@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/i2c/i2c-core.c | 172 ++---
1 file changed, 134 insertions(+), 38 deletions(-)
diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
index ba8eb08..e9fe7f3 100644
--- a/drivers/i2c/i2c-core.c
+++ b/drivers/i2c/i2c-core.c
@@ -105,12 +105,11 @@ struct acpi_i2c_lookup {
acpi_handle device_handle;
};
-static int acpi_i2c_find_address(struct acpi_resource *ares, void *data)
+static int acpi_i2c_fill_info(struct acpi_resource *ares, void *data)
{
struct acpi_i2c_lookup *lookup = data;
struct i2c_board_info *info = lookup->info;
struct acpi_resource_i2c_serialbus *sb;
- acpi_handle adapter_handle;
acpi_status status;
if (info->addr || ares->type != ACPI_RESOURCE_TYPE_SERIAL_BUS)
@@ -120,80 +119,102 @@ static int acpi_i2c_find_address(struct acpi_resource
*ares, void *data)
if (sb->type != ACPI_RESOURCE_SERIAL_TYPE_I2C)
return 1;
- /*
-* Extract the ResourceSource and make sure that the handle matches
-* with the I2C adapter handle.
-*/
status = acpi_get_handle(lookup->device_handle,
sb->resource_source.string_ptr,
-_handle);
- if (ACPI_SUCCESS(status) && adapter_handle == lookup->adapter_handle) {
- info->addr = sb->slave_address;
- if (sb->access_mode == ACPI_I2C_10BIT_MODE)
- info->flags |= I2C_CLIENT_TEN;
- }
+>adapter_handle);
+ if (!ACPI_SUCCESS(status))
+ return 1;
+
+ info->addr = sb->slave_address;
+ if (sb->access_mode == ACPI_I2C_10BIT_MODE)
+ info->flags |= I2C_CLIENT_TEN;
return 1;
}
-static acpi_status acpi_i2c_add_device(acpi_handle handle, u32 level,
- void *data, void **return_value)
+static int acpi_i2c_get_info(struct acpi_device *adev,
+struct i2c_board_info *info,
+acpi_handle *adapter_handle)
{
- struct i2c_adapter *adapter = data;
struct list_head resource_list;
- struct acpi_i2c_lookup lookup;
struct resource_entry *entry;
- struct i2c_board_info info;
- struct acpi_device *adev;
+ struct acpi_i2c_lookup lookup;
int ret;
- if (acpi_bus_get_device(handle, ))
- return AE_OK;
- if (acpi_bus_get_status(adev) || !adev->status.present)
- return AE_OK;
+ if (acpi_bus_get_status(adev) || !adev->status.present ||
+ acpi_device_enumerated(adev))
+ return -EINVAL;
- memset(, 0, sizeof(info));
- info.fwnode = acpi_fwnode_handle(adev);
+ memset(info, 0, sizeof(*info));
+ info->fwnode = acpi_fwnode_handle(adev);
memset(, 0, sizeof(lookup));
- lookup.adapter_handle = ACPI_HANDLE(>dev);
- lookup.device_handle = handle;
- lookup.info =
+ lookup.device_handle = acpi_device_handle(adev);
+ lookup.info = info;
- /*
-* Look up for I2cSerialBus resource with ResourceSource that
-* matches with this adapter.
-*/
+ /* Look up for I2cSerialBus resource */
INIT_LIST_HEAD(_list);
ret = acpi_dev_get_resources(adev, _list,
-acpi_i2c_find_address, );
+acpi_i2c_fill_info, );
acpi_dev_free_resource_list(_list);
- if (ret < 0 || !info.addr)
- return AE_OK;
+ if (ret < 0 || !info->addr)
+ return -EINVAL;
+
+ *adapter_handle = lookup.adapter_handle;
/* Then fill IRQ number if any */
ret = acpi_dev_get_resources(adev, _list, NULL, NULL);
if (ret < 0)
- return AE_OK;
+ return -EINVAL;
resource_list_for_each_entry(entry, _list) {
if (resource_type(entry->res) == IORESOURCE_IRQ) {
- info.irq = entry->res->start;
+ info->irq = entry->res->start;
break;
}
}
acpi_dev_free_resource_list(_list);
+ strlcpy(info->type, dev_name(>dev), sizeof(info->type));
+
+ return 0;
+}
+
+static void acpi_i2c_register_device(stru
[linux-yocto] [PATCH 1/1] ALSA: hda - hdmi_find_pcm_slot return value bug fix
From: Libin Yang <libin.y...@linux.intel.com>
commit d10a80de04a3a8c0d7c1567cbc0a8d2e1181c10a upstream.
hdmi_find_pcm_slot return -EBUSY when not no pcm slot found,
not -ENODEV. So the caller should compare with -EBUSY.
Fixes: a76056f2e57e ('ALSA: hda - hdmi dynamically bind PCM to pin when monitor
hotplug')
Signed-off-by: Libin Yang <libin.y...@linux.intel.com>
Signed-off-by: Takashi Iwai <ti...@suse.de>
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
sound/pci/hda/patch_hdmi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
index 0de79ef..5b5e5db 100644
--- a/sound/pci/hda/patch_hdmi.c
+++ b/sound/pci/hda/patch_hdmi.c
@@ -1215,7 +1215,7 @@ static void hdmi_attach_hda_pcm(struct hdmi_spec *spec,
if (per_pin->pcm)
return;
idx = hdmi_find_pcm_slot(spec, per_pin);
- if (idx == -ENODEV)
+ if (idx == -EBUSY)
return;
per_pin->pcm_idx = idx;
per_pin->pcm = get_hdmi_pcm(spec, idx);
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/1] Backport ALSA bugfix patch for standard/intel/bxt-rebase
Hi Bruce, Seems that the original ALSA backport missed this patch. See bug 9804. Please apply to linux-yocto-4.4 standard/intel/bxt-rebase branch. Thanks, Cal Sullivan Libin Yang (1): ALSA: hda - hdmi_find_pcm_slot return value bug fix sound/pci/hda/patch_hdmi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/4] mmc: block: Always switch back to main area after RPMB access
From: Adrian Hunter <adrian.hun...@intel.com> commit 3c866568aff7dcfc0bbd5ffc7fcc34fa8f100f67 upstream. In preparation to support the use of the RPMB partition with transfer modes that might require re-tuning, always switch back to the main area after RPMB access. RPMB is accessible only via IOCTL so only those paths are affected. Signed-off-by: Adrian Hunter <adrian.hun...@intel.com> Signed-off-by: Ulf Hansson <ulf.hans...@linaro.org> Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- drivers/mmc/card/block.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c index 553113e..cbc4211 100644 --- a/drivers/mmc/card/block.c +++ b/drivers/mmc/card/block.c @@ -624,6 +624,10 @@ static int mmc_blk_ioctl_cmd(struct block_device *bdev, ioc_err = __mmc_blk_ioctl_cmd(card, md, idata); + /* Always switch back to main area after RPMB access */ + if (md->area_type & MMC_BLK_DATA_AREA_RPMB) + mmc_blk_part_switch(card, dev_get_drvdata(>dev)); + mmc_put_card(card); err = mmc_blk_ioctl_copy_to_user(ic_ptr, idata); @@ -689,6 +693,10 @@ static int mmc_blk_ioctl_multi_cmd(struct block_device *bdev, for (i = 0; i < num_of_cmds && !ioc_err; i++) ioc_err = __mmc_blk_ioctl_cmd(card, md, idata[i]); + /* Always switch back to main area after RPMB access */ + if (md->area_type & MMC_BLK_DATA_AREA_RPMB) + mmc_blk_part_switch(card, dev_get_drvdata(>dev)); + mmc_put_card(card); /* copy to user if data and response */ -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/4] mmc: block: Pause re-tuning while switched to the RPMB partition
From: Adrian Hunter <adrian.hun...@intel.com>
commit 57da0c042f4af52614f4bd1a148155a299ae5cd8 upstream.
Re-tuning is not possible when switched to the RPMB
partition. However re-tuning should not be needed
if re-tuning is done immediately before switching,
a small set of operations is done, and then we
immediately switch back to the main partition.
A previous patch ensured that we immediately switch
back to the main partition.
This patch uses the new facility to "pause" re-tuning
before switching to the RPMB partition, and to "unpause"
it after switching from the RPMB partition.
Signed-off-by: Adrian Hunter <adrian.hun...@intel.com>
Signed-off-by: Ulf Hansson <ulf.hans...@linaro.org>
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/mmc/card/block.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
index cbc4211..6e4b26e 100644
--- a/drivers/mmc/card/block.c
+++ b/drivers/mmc/card/block.c
@@ -760,16 +760,25 @@ static inline int mmc_blk_part_switch(struct mmc_card
*card,
if (mmc_card_mmc(card)) {
u8 part_config = card->ext_csd.part_config;
+ if (md->part_type == EXT_CSD_PART_CONFIG_ACC_RPMB)
+ mmc_retune_pause(card->host);
+
part_config &= ~EXT_CSD_PART_CONFIG_ACC_MASK;
part_config |= md->part_type;
ret = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
EXT_CSD_PART_CONFIG, part_config,
card->ext_csd.part_time);
- if (ret)
+ if (ret) {
+ if (md->part_type == EXT_CSD_PART_CONFIG_ACC_RPMB)
+ mmc_retune_unpause(card->host);
return ret;
+ }
card->ext_csd.part_config = part_config;
+
+ if (main_md->part_curr == EXT_CSD_PART_CONFIG_ACC_RPMB)
+ mmc_retune_unpause(card->host);
}
main_md->part_curr = md->part_type;
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 4/4] mmc: sdhci-pci: Remove MMC_CAP_BUS_WIDTH_TEST for Intel controller
From: Adrian Hunter <adrian.hun...@intel.com>
commit 822969369482166050c5b2f7013501505e025c39 upstream.
CMD19/CMD14 bus width test has been found to be unreliable in
some cases. It is not essential, so simply remove it.
Signed-off-by: Adrian Hunter <adrian.hun...@intel.com>
Cc: sta...@vger.kernel.org
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/mmc/host/sdhci-pci-core.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/mmc/host/sdhci-pci-core.c
b/drivers/mmc/host/sdhci-pci-core.c
index adbc1a7..04096ff 100644
--- a/drivers/mmc/host/sdhci-pci-core.c
+++ b/drivers/mmc/host/sdhci-pci-core.c
@@ -361,7 +361,6 @@ static int byt_emmc_probe_slot(struct sdhci_pci_slot *slot)
{
slot->host->mmc->caps |= MMC_CAP_8_BIT_DATA | MMC_CAP_NONREMOVABLE |
MMC_CAP_HW_RESET | MMC_CAP_1_8V_DDR |
-MMC_CAP_BUS_WIDTH_TEST |
MMC_CAP_WAIT_WHILE_BUSY;
slot->host->mmc->caps2 |= MMC_CAP2_HC_ERASE_SZ;
slot->hw_reset = sdhci_pci_int_hw_reset;
@@ -377,15 +376,13 @@ static int byt_emmc_probe_slot(struct sdhci_pci_slot
*slot)
static int byt_sdio_probe_slot(struct sdhci_pci_slot *slot)
{
slot->host->mmc->caps |= MMC_CAP_POWER_OFF_CARD | MMC_CAP_NONREMOVABLE |
-MMC_CAP_BUS_WIDTH_TEST |
MMC_CAP_WAIT_WHILE_BUSY;
return 0;
}
static int byt_sd_probe_slot(struct sdhci_pci_slot *slot)
{
- slot->host->mmc->caps |= MMC_CAP_BUS_WIDTH_TEST |
-MMC_CAP_WAIT_WHILE_BUSY;
+ slot->host->mmc->caps |= MMC_CAP_WAIT_WHILE_BUSY;
slot->cd_con_id = NULL;
slot->cd_idx = 0;
slot->cd_override_level = true;
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/4] mmc: core: Add a facility to "pause" re-tuning
From: Adrian Hunter <adrian.hun...@intel.com>
commit 7ff2760999a86e4d2b1af93dcf0f0d336c309571 upstream.
Re-tuning is not possible when switched to the RPMB
partition. However re-tuning should not be needed
if re-tuning is done immediately before switching,
a small set of operations is done, and then we
immediately switch back to the main partition.
To ensure that re-tuning can't be done for a short
while, add a facility to "pause" re-tuning.
The existing facility to hold / release re-tuning
is used but it also flags re-tuning as needed to cause
re-tuning before the next command (which will be the
switch to RPMB).
We also need to "unpause" in the recovery path, which
is catered for by adding it to mmc_retune_disable().
Signed-off-by: Adrian Hunter <adrian.hun...@intel.com>
Signed-off-by: Ulf Hansson <ulf.hans...@linaro.org>
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
drivers/mmc/core/host.c | 24
include/linux/mmc/host.h | 4
2 files changed, 28 insertions(+)
diff --git a/drivers/mmc/core/host.c b/drivers/mmc/core/host.c
index da950c4..e11a66d 100644
--- a/drivers/mmc/core/host.c
+++ b/drivers/mmc/core/host.c
@@ -69,8 +69,32 @@ void mmc_retune_enable(struct mmc_host *host)
jiffies + host->retune_period * HZ);
}
+/*
+ * Pause re-tuning for a small set of operations. The pause begins after the
+ * next command and after first doing re-tuning.
+ */
+void mmc_retune_pause(struct mmc_host *host)
+{
+ if (!host->retune_paused) {
+ host->retune_paused = 1;
+ mmc_retune_needed(host);
+ mmc_retune_hold(host);
+ }
+}
+EXPORT_SYMBOL(mmc_retune_pause);
+
+void mmc_retune_unpause(struct mmc_host *host)
+{
+ if (host->retune_paused) {
+ host->retune_paused = 0;
+ mmc_retune_release(host);
+ }
+}
+EXPORT_SYMBOL(mmc_retune_unpause);
+
void mmc_retune_disable(struct mmc_host *host)
{
+ mmc_retune_unpause(host);
host->can_retune = 0;
del_timer_sync(>retune_timer);
host->retune_now = 0;
diff --git a/include/linux/mmc/host.h b/include/linux/mmc/host.h
index 8673ffe..fb8e351 100644
--- a/include/linux/mmc/host.h
+++ b/include/linux/mmc/host.h
@@ -316,6 +316,7 @@ struct mmc_host {
unsigned intcan_retune:1; /* re-tuning can be used */
unsigned intdoing_retune:1; /* re-tuning in progress */
unsigned intretune_now:1; /* do re-tuning at next req */
+ unsigned intretune_paused:1; /* re-tuning is temporarily
disabled */
int rescan_disable; /* disable card detection */
int rescan_entered; /* used with nonremovable
devices */
@@ -515,4 +516,7 @@ static inline void mmc_retune_recheck(struct mmc_host *host)
host->retune_now = 1;
}
+void mmc_retune_pause(struct mmc_host *host);
+void mmc_retune_unpause(struct mmc_host *host);
+
#endif /* LINUX_MMC_HOST_H */
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/4] mmc backports for linux-yocto-4.4 standard/base and standard/intel
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 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(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PULL REQUEST] Broxton related backports for linux-yocto-4.4
Hi Bruce, This is a set of backports from upstream. I have tested allyesconfig, allnoconfig, and standard builds and can't find anything wrong there. I have also tested running the kernel on MinnowBoard Max and there are no new errors or warnings. Let me know if I need to make any modifications and send out a V2. Thanks, Cal Sullivan he following changes since commit 628bf627561c6285d99fb978e11d4c15fc29324b: Merge tag 'v4.4.11' into standard/base (2016-05-19 09:02:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib clsulliv/standard/base for you to fetch changes up to 53e84104c5e68eb468823dd0d262a64623d01a55: mmc: mmc: Fix partition switch timeout for some eMMCs (2016-05-19 17:15:25 -0700) Adrian Hunter (3): mmc: sdhci: Remove SDHCI_SDR104_NEEDS_TUNING mmc: mmc: Attempt to flush cache before reset mmc: mmc: Fix partition switch timeout for some eMMCs Andy Shevchenko (12): device property: always check for fwnode type device property: rename helper functions device property: refactor built-in properties support device property: keep single value inplace device property: improve readability of macros device property: return -EINVAL when property isn't found in ACPI device property: Fallback to secondary fwnode if primary misses the property mfd: core: propagate device properties to sub devices drivers mfd: intel-lpss: Pass HSUART configuration via properties device property: avoid allocations of 0 length lib/string: introduce match_string() helper device property: convert to use match_string() helper Bamvor Jian Zhang (1): gpiolib: do not allow to insert an empty gpiochip Christophe RICARD (2): ACPI: Rename acpi_gsi_get_irq_type to acpi_dev_get_irq_type and export symbol ACPI / gpio: Add irq_type when a GPIO is used as an interrupt Dasaratharaman Chandramouli (1): intel_idle: Support for Intel Xeon Phi Processor x200 Product Family Gwendal Grignou (1): mmc: core: Do regular power cycle when lacking eMMC HW reset support Heikki Krogerus (4): device property: helper macros for property entry creation device property: the secondary fwnode needs to depend on the primary device property: fwnode->secondary may contain ERR_PTR(-ENODEV) device property: fix for a case of use-after-free Len Brown (2): intel_idle: Add SKX support intel_idle: add BXT support Linus Walleij (1): Revert "gpio: revert get() to non-errorprogating behaviour" Mika Westerberg (7): pwm: lpss: Remove ->free() callback pwm: lpss: Rework the sequence of programming PWM_SW_UPDATE device property: Take a copy of the property set driver core: platform: Add support for built-in device properties mfd: intel-lpss: Add support for passing device properties mfd: intel-lpss: Pass SDA hold time to I2C host controller driver mfd: intel-lpss: Pass I2C configuration via properties on BXT Qipeng Zha (1): pinctrl: intel: make the high level interrupt working Richard Cochran (10): intel_idle: remove useless return from void function. intel_idle: Fix a helper function's return value. intel_idle: Remove redundant initialization calls. intel_idle: Fix deallocation order on the driver exit path. intel_idle: Fix dangling registration on error path. intel_idle: Avoid a double free of the per-CPU data. intel_idle: Setup the timer broadcast only on successful driver load. intel_idle: Don't overreact to a cpuidle registration failure. intel_idle: Propagate hot plug errors. intel_idle: Clean up all registered devices on exit. Wolfram Sang (1): mmc: make MAN_BKOPS_EN message a debug qipeng.zha (1): pwm: lpss: Update PWM setting for Broxton arch/x86/include/asm/msr-index.h | 8 + drivers/acpi/gsi.c| 21 +- drivers/acpi/property.c | 10 +- drivers/acpi/resource.c | 26 ++ drivers/base/platform.c | 25 ++ drivers/base/property.c | 516 +++--- drivers/gpio/gpiolib-acpi.c | 33 ++- drivers/gpio/gpiolib.c| 17 +- drivers/gpio/gpiolib.h| 3 +- drivers/idle/intel_idle.c | 257 +++-- drivers/mfd/intel-lpss-acpi.c | 31 +- drivers/mfd/intel-lpss-pci.c | 56 +++- drivers/mfd/intel-lpss.c | 16 +- drivers/mfd/intel-lpss.h | 2 + drivers/mfd/mfd-core.c| 7 + drivers/mmc/core/core.c | 5 +- drivers/mmc/core/mmc.c| 39 ++- drivers/mmc/host/sdhci.c | 7 +- drivers/mmc/host/sdhci.h | 1 - drivers/pinctrl/intel/pinctrl-intel.c | 5 +- drivers/pwm/pwm-lpss.c
[linux-yocto] [PATCH 7/9] bsp/intel-common: Add broxton to supported SoCs in intel-core* BSPs
Adds support to features found on Broxton SoCs. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-core2-32.scc | 1 + bsp/intel-common/intel-corei7-64.scc | 1 + 2 files changed, 2 insertions(+) diff --git a/bsp/intel-common/intel-core2-32.scc b/bsp/intel-common/intel-core2-32.scc index 4d98d7b..1261c29 100644 --- a/bsp/intel-common/intel-core2-32.scc +++ b/bsp/intel-common/intel-core2-32.scc @@ -11,6 +11,7 @@ include cfg/x86.scc include features/soc/baytrail/baytrail.scc include features/soc/tunnelcreek/tunnelcreek.scc include features/soc/skylake/skylake.scc +include features/soc/broxton/broxton.scc # Fixme: These should be moved into something similar to the above include bsp/mohonpeak/mohonpeak32.scc diff --git a/bsp/intel-common/intel-corei7-64.scc b/bsp/intel-common/intel-corei7-64.scc index 15aad87..781ae92 100644 --- a/bsp/intel-common/intel-corei7-64.scc +++ b/bsp/intel-common/intel-corei7-64.scc @@ -10,6 +10,7 @@ include cfg/x86_64.scc # Supported platforms and SoCs include features/soc/baytrail/baytrail.scc include features/soc/skylake/skylake.scc +include features/soc/broxton/broxton.scc # Fixme: These should be moved into something similar to the above include bsp/haswell-wc/haswell-wc.scc -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 5/9] baytrail; valleyisland: Use designware-usb3 feature instead of config
A common configuration is shared across many platforms. Use a feature instead of additional configuration options in each file. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/valleyisland/valleyisland.cfg | 2 -- bsp/valleyisland/valleyisland.scc | 1 + features/soc/baytrail/baytrail.cfg | 2 -- features/soc/baytrail/baytrail.scc | 1 + 4 files changed, 2 insertions(+), 4 deletions(-) diff --git a/bsp/valleyisland/valleyisland.cfg b/bsp/valleyisland/valleyisland.cfg index 486a1aa..3f6c4a2 100644 --- a/bsp/valleyisland/valleyisland.cfg +++ b/bsp/valleyisland/valleyisland.cfg @@ -46,8 +46,6 @@ CONFIG_PWM_SYSFS=y CONFIG_I2C_I801=y # USB Device Support -CONFIG_USB_DWC3=y -CONFIG_USB_DWC3_GADGET=y CONFIG_USB_GADGET=y CONFIG_USB_LIBCOMPOSITE=m CONFIG_USB_MASS_STORAGE=m diff --git a/bsp/valleyisland/valleyisland.scc b/bsp/valleyisland/valleyisland.scc index 0ab5650..379dfbf 100644 --- a/bsp/valleyisland/valleyisland.scc +++ b/bsp/valleyisland/valleyisland.scc @@ -20,3 +20,4 @@ include features/spi/spidev.scc include features/usb/ehci-hcd.scc include features/usb/xhci-hcd.scc +include features/usb/designware-usb3.scc diff --git a/features/soc/baytrail/baytrail.cfg b/features/soc/baytrail/baytrail.cfg index 0a5e6c1..6b9ad27 100644 --- a/features/soc/baytrail/baytrail.cfg +++ b/features/soc/baytrail/baytrail.cfg @@ -37,8 +37,6 @@ CONFIG_DW_DMAC=m CONFIG_DW_DMAC_PCI=m # USB Device Support -CONFIG_USB_DWC3=y -CONFIG_USB_DWC3_GADGET=y CONFIG_USB_GADGET=y CONFIG_USB_LIBCOMPOSITE=m CONFIG_USB_MASS_STORAGE=m diff --git a/features/soc/baytrail/baytrail.scc b/features/soc/baytrail/baytrail.scc index 33a6ecd..49c926a 100644 --- a/features/soc/baytrail/baytrail.scc +++ b/features/soc/baytrail/baytrail.scc @@ -9,6 +9,7 @@ include features/power/intel.scc include features/usb/xhci-hcd.scc include features/usb/ehci-hcd.scc +include features/usb/designware-usb3.scc include features/intel-pinctrl/intel-pinctrl.scc kconf hardware baytrail.cfg -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 8/9] features: add intel-telemetry feature
This feature enables the Intel Telemerty driver for Apollo Lake and newer platforms. The feature adds an interface to the debugfs for SoC state monitoring. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/telemetry/intel-telemetry.cfg | 9 + features/telemetry/intel-telemetry.scc | 4 2 files changed, 13 insertions(+) create mode 100644 features/telemetry/intel-telemetry.cfg create mode 100644 features/telemetry/intel-telemetry.scc diff --git a/features/telemetry/intel-telemetry.cfg b/features/telemetry/intel-telemetry.cfg new file mode 100644 index 000..19d53c0 --- /dev/null +++ b/features/telemetry/intel-telemetry.cfg @@ -0,0 +1,9 @@ +# INTEL_TELEMETRY is x86_64 only! Do not add to 32-bit! +CONFIG_X86_64=y + +# Other dependencies +CONFIG_INTEL_PMC_IPC=y +CONFIG_INTEL_PUNIT_IPC=y + +# The feature +CONFIG_INTEL_TELEMETRY=y diff --git a/features/telemetry/intel-telemetry.scc b/features/telemetry/intel-telemetry.scc new file mode 100644 index 000..5cefbd3 --- /dev/null +++ b/features/telemetry/intel-telemetry.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION "Intel Telemetry driver for Apollo Lake and beyond" +define KFEATURE_COMPATIBILITY board + +kconf hardware intel-telemetry.cfg -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/9] cfg/sound.cfg: Add USB audio support
Sound over USB is very common and should be part of general sound configuration. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- cfg/sound.cfg | 2 ++ 1 file changed, 2 insertions(+) diff --git a/cfg/sound.cfg b/cfg/sound.cfg index bf9846c..d296ae7 100644 --- a/cfg/sound.cfg +++ b/cfg/sound.cfg @@ -11,4 +11,6 @@ CONFIG_SND_RAWMIDI_SEQ=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_ENS1370=m CONFIG_SND_INTEL8X0=m +CONFIG_SND_USB=y +CONFIG_SND_USB_AUDIO=m CONFIG_AC97_BUS=m -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 4/9] features/usb: Add usb-designware2 and 3 features
These features support DesignWare USB2 and USB3 controllers and are used by many SoCs. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/usb/designware-usb2.cfg | 2 ++ features/usb/designware-usb2.scc | 4 features/usb/designware-usb3.cfg | 3 +++ features/usb/designware-usb3.scc | 4 4 files changed, 13 insertions(+) create mode 100644 features/usb/designware-usb2.cfg create mode 100644 features/usb/designware-usb2.scc create mode 100644 features/usb/designware-usb3.cfg create mode 100644 features/usb/designware-usb3.scc diff --git a/features/usb/designware-usb2.cfg b/features/usb/designware-usb2.cfg new file mode 100644 index 000..e7d7e7f --- /dev/null +++ b/features/usb/designware-usb2.cfg @@ -0,0 +1,2 @@ +CONFIG_USB_DWC2=m +CONFIG_USB_DWC2_PCI=m diff --git a/features/usb/designware-usb2.scc b/features/usb/designware-usb2.scc new file mode 100644 index 000..9bc9538 --- /dev/null +++ b/features/usb/designware-usb2.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION "Enable DesignWare USB2 controller support" +define KFEATURE_COMPATIBILITY board + +kconf hardware designware-usb2.cfg diff --git a/features/usb/designware-usb3.cfg b/features/usb/designware-usb3.cfg new file mode 100644 index 000..ed52bdb --- /dev/null +++ b/features/usb/designware-usb3.cfg @@ -0,0 +1,3 @@ +CONFIG_USB_DWC3=y +CONFIG_USB_DWC3_GADGET=y +CONFIG_USB_DWC3_PCI=m diff --git a/features/usb/designware-usb3.scc b/features/usb/designware-usb3.scc new file mode 100644 index 000..dc2a70e --- /dev/null +++ b/features/usb/designware-usb3.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION "Enable DesignWare USB3 controller support" +define KFEATURE_COMPATIBILITY board + +kconf hardware designware-usb3.cfg -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/9] features/soc/skylake: Refactor and comment config fragment
Organized configurations into labeled sections. Removed NETCONSOLE as its in the base configuration and is not necessarily a SoC feature. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/soc/skylake/skylake.cfg | 18 ++ 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/features/soc/skylake/skylake.cfg b/features/soc/skylake/skylake.cfg index 1bcf238..77f0efa 100644 --- a/features/soc/skylake/skylake.cfg +++ b/features/soc/skylake/skylake.cfg @@ -1,21 +1,31 @@ -CONFIG_CPU_IDLE=y +# Skylake/Broxton LPSS support 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 + +# Additional power management support CONFIG_POWERCAP=y CONFIG_INTEL_RAPL=m CONFIG_INTEL_POWERCLAMP=m +CONFIG_CPU_IDLE=y + +# Hardware monitoring CONFIG_HWMON=y CONFIG_SENSORS_I5500=m + +# Additional sound support 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 + +# Additional IO support CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_INTEL=y +CONFIG_USB_EHCI_PCI=y +CONFIG_GPIO_LYNXPOINT=m + +# Other misc support CONFIG_INTEL_MEI_TXE=m -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/9] Broxton enablement and slight refactoring for 4.4 and master
Hi Bruce, This patch series adds some features and configuration settings necessary for Broxton enablement, as well as a couple minor refactoring patches. These changes have been tested with the latest linux-yocto-4.4 HEAD on the MinnowBoard Max/Turbot and NUC6 and no additional errors were found. Matt, Steve, please review and make sure there are no more absolute needs for Broxton enablement. Thanks, Cal California Sullivan (9): features/soc/skylake: Refactor and comment config fragment features/i915: Add CONFIG_KMS_FB_HELPER=y cfg/sound.cfg: Add USB audio support features/usb: Add usb-designware2 and 3 features baytrail;valleyisland: Use designware-usb3 feature instead of config features: add broxton soc feature bsp/intel-common: Add broxton to supported SoCs in intel-core* BSPs features: add intel-telemetry feature bsp/intel-corei7-64: Add intel-telemetry feature bsp/intel-common/intel-core2-32.scc| 1 + bsp/intel-common/intel-corei7-64.scc | 4 bsp/valleyisland/valleyisland.cfg | 2 -- bsp/valleyisland/valleyisland.scc | 1 + cfg/sound.cfg | 2 ++ features/i915/i915.cfg | 1 + features/soc/baytrail/baytrail.cfg | 2 -- features/soc/baytrail/baytrail.scc | 1 + features/soc/broxton/broxton.cfg | 22 ++ features/soc/broxton/broxton.scc | 15 +++ features/soc/skylake/skylake.cfg | 18 ++ features/telemetry/intel-telemetry.cfg | 9 + features/telemetry/intel-telemetry.scc | 4 features/usb/designware-usb2.cfg | 2 ++ features/usb/designware-usb2.scc | 4 features/usb/designware-usb3.cfg | 3 +++ features/usb/designware-usb3.scc | 4 17 files changed, 87 insertions(+), 8 deletions(-) create mode 100644 features/soc/broxton/broxton.cfg create mode 100644 features/soc/broxton/broxton.scc create mode 100644 features/telemetry/intel-telemetry.cfg create mode 100644 features/telemetry/intel-telemetry.scc create mode 100644 features/usb/designware-usb2.cfg create mode 100644 features/usb/designware-usb2.scc create mode 100644 features/usb/designware-usb3.cfg create mode 100644 features/usb/designware-usb3.scc -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/1] drm/i915/skl: Fix DMC load on Skylake J0 and K0
NUC6 (Skylake) graphics firmware fails to load without this patch.
From: Mat Martineau <mathew.j.martin...@linux.intel.com>
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 <rodrigo.v...@intel.com>
Signed-off-by: Mat Martineau <mathew.j.martin...@linux.intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.v...@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.v...@intel.com>
Link:
http://patchwork.freedesktop.org/patch/msgid/1454023163-25469-1-git-send-email-mathew.j.martin...@linux.intel.com
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
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[] = {
--
2.5.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/2] features: Add tmpfs-posix-acl feature fragments
This enables the CONFIG_TMPFS_POSIX_ACL, which is wanted by things like systemd. We also explicitly enable the features's dependencies and options selected by the feature for clarity. Partial fix for [YOCTO #9269]. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/tmpfs/tmpfs-posix-acl.cfg | 10 ++ features/tmpfs/tmpfs-posix-acl.scc | 4 2 files changed, 14 insertions(+) create mode 100644 features/tmpfs/tmpfs-posix-acl.cfg create mode 100644 features/tmpfs/tmpfs-posix-acl.scc diff --git a/features/tmpfs/tmpfs-posix-acl.cfg b/features/tmpfs/tmpfs-posix-acl.cfg new file mode 100644 index 000..b391f8a --- /dev/null +++ b/features/tmpfs/tmpfs-posix-acl.cfg @@ -0,0 +1,10 @@ +# Dependencies of the feature +CONFIG_SHMEM=y +CONFIG_TMPFS=y + +# The feature we want to enable +CONFIG_TMPFS_POSIX_ACL=y + +# The above selects these options automatically +CONFIG_TMPFS_XATTR=y +CONFIG_FS_POSIX_ACL=y diff --git a/features/tmpfs/tmpfs-posix-acl.scc b/features/tmpfs/tmpfs-posix-acl.scc new file mode 100644 index 000..062e6c4 --- /dev/null +++ b/features/tmpfs/tmpfs-posix-acl.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION "Enable ACL support for tmpfs" +define KFEATURE_COMPATIBILITY all + +kconf non-hardware tmpfs-posix-acl.cfg -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/2] ktypes/standard: Add tmpfs-posix-acl feature
Fixes [YOCTO #9269] Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- ktypes/standard/standard.scc | 1 + 1 file changed, 1 insertion(+) diff --git a/ktypes/standard/standard.scc b/ktypes/standard/standard.scc index 6b9fb1a..fb8b343 100644 --- a/ktypes/standard/standard.scc +++ b/ktypes/standard/standard.scc @@ -49,6 +49,7 @@ include features/initramfs/initramfs.scc include features/yaffs2/yaffs2.scc include features/aufs/aufs.scc +include features/tmpfs/tmpfs-posix-acl.scc include features/cgroups/cgroups.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/1] Fix ftrace missing in -standard BSPs
Targetted for 4.4 and master. California Sullivan (1): features/ftrace: set CONFIG_FTRACE=y features/ftrace/ftrace.cfg | 1 + 1 file changed, 1 insertion(+) -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/1] features/ftrace: set CONFIG_FTRACE=y
With EXPERT, EMBEDDED and DEBUG_KERNEL removed from the base, this is no longer being selected by default in in standard BSPs, causing breakage in things that relied on it. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/ftrace/ftrace.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/features/ftrace/ftrace.cfg b/features/ftrace/ftrace.cfg index 692dffe..48ee11b 100644 --- a/features/ftrace/ftrace.cfg +++ b/features/ftrace/ftrace.cfg @@ -1,3 +1,4 @@ CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y +CONFIG_FTRACE=y CONFIG_FTRACE_SYSCALLS=y -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 12/12] bsp: remove profiling and latencytop from non-developer common-pc BSPs
These features enable DEBUG_KERNEL, which is no longer standard. They are still available in the -developer BSPs. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/common-pc-64/common-pc-64-standard.scc | 2 -- bsp/common-pc/common-pc-standard.scc | 2 -- 2 files changed, 4 deletions(-) diff --git a/bsp/common-pc-64/common-pc-64-standard.scc b/bsp/common-pc-64/common-pc-64-standard.scc index 4801cf5..28119ec 100644 --- a/bsp/common-pc-64/common-pc-64-standard.scc +++ b/bsp/common-pc-64/common-pc-64-standard.scc @@ -10,8 +10,6 @@ include common-pc-64.scc # default policy for standard kernels include cfg/boot-live.scc include cfg/usb-mass-storage.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc include cfg/virtio.scc include features/media/media-usb-webcams.scc include features/sound/snd_hda_intel.scc diff --git a/bsp/common-pc/common-pc-standard.scc b/bsp/common-pc/common-pc-standard.scc index 0b7aade..8f169ba 100644 --- a/bsp/common-pc/common-pc-standard.scc +++ b/bsp/common-pc/common-pc-standard.scc @@ -10,8 +10,6 @@ include common-pc.scc # default policy for standard kernels include cfg/boot-live.scc include cfg/usb-mass-storage.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc include cfg/virtio.scc include features/media/media-usb-webcams.scc include features/sound/snd_hda_intel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 08/12] preempt-rt.scc: include developer ktype instead of standard
The developer ktype now has the functionality of the previous standard ktype. To keep preempt-rt's functionality consistent we must include developer. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- ktypes/preempt-rt/preempt-rt.scc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ktypes/preempt-rt/preempt-rt.scc b/ktypes/preempt-rt/preempt-rt.scc index 5e52ec9..db218fc 100644 --- a/ktypes/preempt-rt/preempt-rt.scc +++ b/ktypes/preempt-rt/preempt-rt.scc @@ -1,4 +1,4 @@ -include ktypes/standard/standard.scc nocfg +include ktypes/developer/developer.scc nocfg branch preempt-rt # aufs doesn't even build with preempt-rt kernels -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 11/12] bsp: add developer common-pc BSPs
These -developer BSPs use the developer ktype, giving the same functionality of the old -standard BSPs. With the changes to the standard and base ktypes, the -standard BSPs no longer have EMBEDDED, EXPERT, or DEBUG_KERNEL, creating a more production-ready default. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/common-pc-64/common-pc-64-developer.scc | 16 bsp/common-pc/common-pc-developer.scc | 16 2 files changed, 32 insertions(+) create mode 100644 bsp/common-pc-64/common-pc-64-developer.scc create mode 100644 bsp/common-pc/common-pc-developer.scc diff --git a/bsp/common-pc-64/common-pc-64-developer.scc b/bsp/common-pc-64/common-pc-64-developer.scc new file mode 100644 index 000..99b9c9d --- /dev/null +++ b/bsp/common-pc-64/common-pc-64-developer.scc @@ -0,0 +1,16 @@ +define KMACHINE common-pc-64 +define KMACHINE qemux86-64 +define KTYPE developer +define KARCH x86_64 + +include ktypes/developer/developer.scc + +include common-pc-64.scc + +include cfg/boot-live.scc +include cfg/usb-mass-storage.scc +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc +include cfg/virtio.scc +include features/media/media-usb-webcams.scc +include features/sound/snd_hda_intel.scc diff --git a/bsp/common-pc/common-pc-developer.scc b/bsp/common-pc/common-pc-developer.scc new file mode 100644 index 000..ea728c5 --- /dev/null +++ b/bsp/common-pc/common-pc-developer.scc @@ -0,0 +1,16 @@ +define KMACHINE common-pc +define KMACHINE qemux86 +define KTYPE developer +define KARCH i386 + +include ktypes/developer/developer.scc + +include common-pc.scc + +include cfg/boot-live.scc +include cfg/usb-mass-storage.scc +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc +include cfg/virtio.scc +include features/media/media-usb-webcams.scc +include features/sound/snd_hda_intel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 00/12] ktype refactoring: move DEBUG_KERNEL, EXPERT and EMBEDDED
Targetted for yocto-4.4 and master Changes since last revision: *Removed branch command from developer ktype* Including standard does this already. *Removed "default policy" comment from -developer common-pc BSPs* This was copied from the -standard BSPs and is no longer accurate. I could have changed standard to developer in the comment, but I don't feel comfortable asserting that this is the default policy for developer kernels when more is likely to be added. *Updated commit messages* Explain that standard is now for production in "add developer common-pc BSPs" patch. Fix typo in subject line of "inlcude developer ktype instead of standard" patch. *Patches aren't 00/12* That was embarassing. This patch series refactors the ktypes so that base and standard ktypes do not enable EMBEDDED, EXPERT, or DEBUG_KERNEL. The reason this decision was made is because production platforms likely do not want DEBUG_KERNEL enabled, and EMBEDDED selects EXPERT which selects DEBUG_KERNEL. A new ktype called "developer" was also created. This ktype enables the options now missing from standard and base, making it easy to maintain the functionality of a BSP through simply swapping the ktype from standard to developer. The preempt-rt ktype is now based off of developer in order to maintain its functionality. The new standard ktype does not include EMBEDDED, EXPERT, or DEBUG_KERNEL. Without DEBUG_KERNEL it loses a number of debug features that are selected by default. Without EXPERT it gains RFKILL_INPUT and DEBUG_MEMORY_INIT, while losing VMSPLIT_3G. These are only available to configure with CONFIG_EXPERT=y and default to EXPERT or !EXPERT. Not selecting EMBEDDED has no apparent impacts. Some coordination is required for this change, as existing BSPs WILL be affected, and will either need to accept the changes in the standard ktype or move to the developer ktype. California Sullivan (12): features/debug: add debug-kernel feature ktypes: add developer ktype ktypes/base: Disable EMBEDDED and DEBUG_KERNEL CONFIG_PROCESSOR_SELECT: do not enable intel-common-drivers.scc: move profiling and latencytop to a new file romley.scc remove profiling and latencytop features bsp/intel-common: add intel-core* developer BSPs preempt-rt.scc: include developer ktype instead of standard intel-common: add intel-developer-drivers.scc to preempt-rt BSPs CONFIG_I2C_I801: set option to yes in intel-core* BSPs bsp: add developer common-pc BSPs bsp: remove profiling and latencytop from non-developer common-pc BSPs bsp/common-pc-64/common-pc-64-developer.scc | 16 bsp/common-pc-64/common-pc-64-standard.scc | 2 -- bsp/common-pc/common-pc-developer.scc | 16 bsp/common-pc/common-pc-standard.scc| 2 -- bsp/haswell-wc/haswell-wc.cfg | 2 +- bsp/intel-common/intel-common-drivers.scc | 2 -- bsp/intel-common/intel-core2-32-developer.scc | 14 ++ bsp/intel-common/intel-core2-32-preempt-rt.scc | 1 + bsp/intel-common/intel-core2-32.cfg | 1 - bsp/intel-common/intel-corei7-64-developer.scc | 13 + bsp/intel-common/intel-corei7-64-preempt-rt.scc | 1 + bsp/intel-common/intel-developer-drivers.scc| 3 +++ bsp/mohonpeak/mohonpeak.cfg | 2 +- bsp/romley/romley.scc | 3 --- cfg/amd.cfg | 1 - cfg/intel.cfg | 2 -- features/debug/debug-kernel.cfg | 3 +++ features/debug/debug-kernel.scc | 5 + features/debug/printk.scc | 1 + features/latencytop/latencytop.scc | 3 +++ features/profiling/profiling.scc| 2 ++ features/soc/baytrail/baytrail.cfg | 2 +- ktypes/base/base.cfg| 6 +++--- ktypes/developer/developer.cfg | 19 +++ ktypes/developer/developer.scc | 9 + ktypes/preempt-rt/preempt-rt.scc| 2 +- 26 files changed, 113 insertions(+), 20 deletions(-) create mode 100644 bsp/common-pc-64/common-pc-64-developer.scc create mode 100644 bsp/common-pc/common-pc-developer.scc create mode 100644 bsp/intel-common/intel-core2-32-developer.scc create mode 100644 bsp/intel-common/intel-corei7-64-developer.scc create mode 100644 bsp/intel-common/intel-developer-drivers.scc create mode 100644 features/debug/debug-kernel.cfg create mode 100644 features/debug/debug-kernel.scc create mode 100644 ktypes/developer/developer.cfg create mode 100644 ktypes/developer/developer.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 10/12] CONFIG_I2C_I801: set option to yes in intel-core* BSPs
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 a developer ktype BSP. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- 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] [PATCH v3 03/12] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL
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 <california.l.sulli...@intel.com> --- 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 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 # 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] [PATCH v3 04/12] CONFIG_PROCESSOR_SELECT: do not enable
The base ktype no longer enables EXPERT, so PROCESSOR_SELECT cannot be enabled by default. Nothing relying on PROCESSOR_SELECT is changed from default, and PROCESSOR_SELECT itself only enables a printk, so this will have no functional change on BSPs using these fragments. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-core2-32.cfg | 1 - cfg/amd.cfg | 1 - cfg/intel.cfg | 2 -- 3 files changed, 4 deletions(-) diff --git a/bsp/intel-common/intel-core2-32.cfg b/bsp/intel-common/intel-core2-32.cfg index ab004ea..b106c76 100644 --- a/bsp/intel-common/intel-core2-32.cfg +++ b/bsp/intel-common/intel-core2-32.cfg @@ -1,5 +1,4 @@ CONFIG_MCORE2=y -CONFIG_PROCESSOR_SELECT=y # max available for this processory family CONFIG_NR_CPUS=8 diff --git a/cfg/amd.cfg b/cfg/amd.cfg index 704b8f7..845d29f 100644 --- a/cfg/amd.cfg +++ b/cfg/amd.cfg @@ -6,7 +6,6 @@ CONFIG_MICROCODE_EARLY=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_EARLY_AMD=y -CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_AMD=y CONFIG_X86_MCE=y diff --git a/cfg/intel.cfg b/cfg/intel.cfg index 4b7ad31..5eb6b08 100644 --- a/cfg/intel.cfg +++ b/cfg/intel.cfg @@ -4,8 +4,6 @@ CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_EARLY=y CONFIG_MICROCODE_INTEL_EARLY=y - -CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_INTEL=y CONFIG_X86_EXTENDED_PLATFORM=y -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 07/12] bsp/intel-common: add intel-core* developer BSPs
These BSPs use the developer ktype and add the intel-developer-drivers.scc file. They should have the same functionality as the -standard BSPs had previously. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-core2-32-developer.scc | 14 ++ bsp/intel-common/intel-corei7-64-developer.scc | 13 + 2 files changed, 27 insertions(+) create mode 100644 bsp/intel-common/intel-core2-32-developer.scc create mode 100644 bsp/intel-common/intel-corei7-64-developer.scc diff --git a/bsp/intel-common/intel-core2-32-developer.scc b/bsp/intel-common/intel-core2-32-developer.scc new file mode 100644 index 000..4d8b4cd --- /dev/null +++ b/bsp/intel-common/intel-core2-32-developer.scc @@ -0,0 +1,14 @@ +# intel-core2-32-developer.scc +# +# Developer ktype for 32 bit Core 2 and later CPUs. +# + +define KMACHINE intel-core2-32 +define KARCH i386 +define KTYPE developer + +include ktypes/developer/developer.scc +include intel-common-drivers.scc +include intel-common-drivers-32.scc +include intel-developer-drivers.scc +include intel-core2-32.scc diff --git a/bsp/intel-common/intel-corei7-64-developer.scc b/bsp/intel-common/intel-corei7-64-developer.scc new file mode 100644 index 000..f5445f2 --- /dev/null +++ b/bsp/intel-common/intel-corei7-64-developer.scc @@ -0,0 +1,13 @@ +# intel-corei7-64-developer.scc +# +# Developer ktype for 64 bit Nehalem, Bay Trail, and later CPUs. +# + +define KMACHINE intel-corei7-64 +define KARCH x86_64 +define KTYPE developer + +include ktypes/developer/developer.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
[linux-yocto] [PATCH v3 05/12] intel-common-drivers.scc: move profiling and latencytop to a new file
Profiling and latencytop enable DEBUG_KERNEL, which is no longer a standard config option. Move these features to a new file called intel-developer-drivers.scc, which is to be included in intel developer BSPs. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-common-drivers.scc| 2 -- bsp/intel-common/intel-developer-drivers.scc | 3 +++ 2 files changed, 3 insertions(+), 2 deletions(-) create mode 100644 bsp/intel-common/intel-developer-drivers.scc diff --git a/bsp/intel-common/intel-common-drivers.scc b/bsp/intel-common/intel-common-drivers.scc index a7673e7..9beef28 100644 --- a/bsp/intel-common/intel-common-drivers.scc +++ b/bsp/intel-common/intel-common-drivers.scc @@ -76,5 +76,3 @@ include cfg/efi-ext.scc # default policy for standard kernels include cfg/usb-mass-storage.scc include cfg/boot-live.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc diff --git a/bsp/intel-common/intel-developer-drivers.scc b/bsp/intel-common/intel-developer-drivers.scc new file mode 100644 index 000..46842b6 --- /dev/null +++ b/bsp/intel-common/intel-developer-drivers.scc @@ -0,0 +1,3 @@ +# Additional features for developer bsps +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 02/12] ktypes: add developer ktype
The developer ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL, opening up more kernel options and setting some defaults. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- ktypes/developer/developer.cfg | 19 +++ ktypes/developer/developer.scc | 9 + 2 files changed, 28 insertions(+) create mode 100644 ktypes/developer/developer.cfg create mode 100644 ktypes/developer/developer.scc diff --git a/ktypes/developer/developer.cfg b/ktypes/developer/developer.cfg new file mode 100644 index 000..ee04ec7 --- /dev/null +++ b/ktypes/developer/developer.cfg @@ -0,0 +1,19 @@ +#. +#WARNING +# +# This file is a kernel configuration fragment, and not a full kernel +# configuration file. The final kernel configuration is made up of +# an assembly of processed fragments, each of which is designed to +# capture a specific part of the final configuration (e.g. platform +# configuration, feature configuration, and board specific hardware +# configuration). For more information on kernel configuration, please +# consult the product documentation. +# +#. + +# +# General setup +# +CONFIG_EXPERT=y +CONFIG_EMBEDDED=y +CONFIG_DEBUG_KERNEL=y diff --git a/ktypes/developer/developer.scc b/ktypes/developer/developer.scc new file mode 100644 index 000..cf2c0e6 --- /dev/null +++ b/ktypes/developer/developer.scc @@ -0,0 +1,9 @@ +# Include this kernel type fragment to get the standard features and +# configuration values, as well as EXPERT, EMBEDDED, DEBUG_KERNEL, +# and the options defaulted to yes through them. + +include ktypes/standard/standard.scc + +force kconf non-hardware developer.cfg + +include features/debug/debug-kernel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 06/12] romley.scc remove profiling and latencytop features
Romley is supported by the intel-core* BSP which already include profiling and latencytop where appropriate. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/romley/romley.scc | 3 --- 1 file changed, 3 deletions(-) diff --git a/bsp/romley/romley.scc b/bsp/romley/romley.scc index 9967407..20ffb88 100644 --- a/bsp/romley/romley.scc +++ b/bsp/romley/romley.scc @@ -11,6 +11,3 @@ include features/igb/igb.scc # generic power management include features/power/intel.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc - -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v3 01/12] features/debug: add debug-kernel feature
Since EMBEDDED, EXPERT, and DEBUG_KERNEL are being removed from the base ktype, we can no longer assume DEBUG_KERNEL is enabled. Also add this fragment to features that require DEBUG_KERNEL. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/debug/debug-kernel.cfg| 3 +++ features/debug/debug-kernel.scc| 5 + features/debug/printk.scc | 1 + features/latencytop/latencytop.scc | 3 +++ features/profiling/profiling.scc | 2 ++ 5 files changed, 14 insertions(+) create mode 100644 features/debug/debug-kernel.cfg create mode 100644 features/debug/debug-kernel.scc diff --git a/features/debug/debug-kernel.cfg b/features/debug/debug-kernel.cfg new file mode 100644 index 000..cdc07a9 --- /dev/null +++ b/features/debug/debug-kernel.cfg @@ -0,0 +1,3 @@ +CONFIG_DEBUG_KERNEL=y +CONFIG_DEBUG_INFO=y +CONFIG_DEBUG_PREEMPT=y diff --git a/features/debug/debug-kernel.scc b/features/debug/debug-kernel.scc new file mode 100644 index 000..7d2c351 --- /dev/null +++ b/features/debug/debug-kernel.scc @@ -0,0 +1,5 @@ + +define KFEATURE_DESCRIPTION "Enable debug kernel and some important debug features" +define KFEATURE_COMPATIBILITY all + +kconf non-hardware debug-kernel.cfg diff --git a/features/debug/printk.scc b/features/debug/printk.scc index d592605..3526dea 100644 --- a/features/debug/printk.scc +++ b/features/debug/printk.scc @@ -8,3 +8,4 @@ define KFEATURE_COMPATIBILITY all kconf non-hardware printk.cfg +include debug-kernel.scc diff --git a/features/latencytop/latencytop.scc b/features/latencytop/latencytop.scc index 923b5d9..af59e24 100644 --- a/features/latencytop/latencytop.scc +++ b/features/latencytop/latencytop.scc @@ -1,4 +1,7 @@ + define KFEATURE_DESCRIPTION "Enable latencytop" define KFEATURE_COMPATIBILITY arch kconf non-hardware latencytop.cfg + +include features/debug/debug-kernel.scc diff --git a/features/profiling/profiling.scc b/features/profiling/profiling.scc index 32032fa..50cdcfc 100644 --- a/features/profiling/profiling.scc +++ b/features/profiling/profiling.scc @@ -2,3 +2,5 @@ define KFEATURE_DESCRIPTION "Enable profiling and timerstats" define KFEATURE_COMPATIBILITY board kconf non-hardware profiling.cfg + +include features/debug/debug-kernel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v2 00/12] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL
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 <california.l.sulli...@intel.com> --- 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 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 # 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] [PATCH v2 00/12] ktypes: add developer ktype
The developer ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL, opening up more kernel options and setting some defaults. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- ktypes/developer/developer.cfg | 19 +++ ktypes/developer/developer.scc | 10 ++ 2 files changed, 29 insertions(+) create mode 100644 ktypes/developer/developer.cfg create mode 100644 ktypes/developer/developer.scc diff --git a/ktypes/developer/developer.cfg b/ktypes/developer/developer.cfg new file mode 100644 index 000..ee04ec7 --- /dev/null +++ b/ktypes/developer/developer.cfg @@ -0,0 +1,19 @@ +#. +#WARNING +# +# This file is a kernel configuration fragment, and not a full kernel +# configuration file. The final kernel configuration is made up of +# an assembly of processed fragments, each of which is designed to +# capture a specific part of the final configuration (e.g. platform +# configuration, feature configuration, and board specific hardware +# configuration). For more information on kernel configuration, please +# consult the product documentation. +# +#. + +# +# General setup +# +CONFIG_EXPERT=y +CONFIG_EMBEDDED=y +CONFIG_DEBUG_KERNEL=y diff --git a/ktypes/developer/developer.scc b/ktypes/developer/developer.scc new file mode 100644 index 000..7ab51de --- /dev/null +++ b/ktypes/developer/developer.scc @@ -0,0 +1,10 @@ +# Include this kernel type fragment to get the standard features and +# configuration values, as well as EXPERT, EMBEDDED, DEBUG_KERNEL, +# and the options defaulted to yes through them. + +include ktypes/standard/standard.scc +branch standard + +force kconf non-hardware developer.cfg + +include features/debug/debug-kernel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v2 00/12] intel-common-drivers.scc: move profiling and latencytop to a new file
Profiling and latencytop enable DEBUG_KERNEL, which is no longer a standard config option. Move these features to a new file called intel-developer-drivers.scc, which is to be included in intel developer BSPs. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-common-drivers.scc| 2 -- bsp/intel-common/intel-developer-drivers.scc | 3 +++ 2 files changed, 3 insertions(+), 2 deletions(-) create mode 100644 bsp/intel-common/intel-developer-drivers.scc diff --git a/bsp/intel-common/intel-common-drivers.scc b/bsp/intel-common/intel-common-drivers.scc index a7673e7..9beef28 100644 --- a/bsp/intel-common/intel-common-drivers.scc +++ b/bsp/intel-common/intel-common-drivers.scc @@ -76,5 +76,3 @@ include cfg/efi-ext.scc # default policy for standard kernels include cfg/usb-mass-storage.scc include cfg/boot-live.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc diff --git a/bsp/intel-common/intel-developer-drivers.scc b/bsp/intel-common/intel-developer-drivers.scc new file mode 100644 index 000..46842b6 --- /dev/null +++ b/bsp/intel-common/intel-developer-drivers.scc @@ -0,0 +1,3 @@ +# Additional features for developer bsps +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v2 00/12] preempt-rt.scc: inlcude developer ktype instead of standard
The developer ktype now has the functionality of the previous standard ktype. To keep preempt-rt's functionality consistent we must include developer. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- ktypes/preempt-rt/preempt-rt.scc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ktypes/preempt-rt/preempt-rt.scc b/ktypes/preempt-rt/preempt-rt.scc index 5e52ec9..db218fc 100644 --- a/ktypes/preempt-rt/preempt-rt.scc +++ b/ktypes/preempt-rt/preempt-rt.scc @@ -1,4 +1,4 @@ -include ktypes/standard/standard.scc nocfg +include ktypes/developer/developer.scc nocfg branch preempt-rt # aufs doesn't even build with preempt-rt kernels -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v2 00/12] bsp: remove profiling and latencytop from non-developer common-pc BSPs
These features enable DEBUG_KERNEL, which is no longer standard. They are still available in the -developer BSPs. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/common-pc-64/common-pc-64-standard.scc | 2 -- bsp/common-pc/common-pc-standard.scc | 2 -- 2 files changed, 4 deletions(-) diff --git a/bsp/common-pc-64/common-pc-64-standard.scc b/bsp/common-pc-64/common-pc-64-standard.scc index 4801cf5..28119ec 100644 --- a/bsp/common-pc-64/common-pc-64-standard.scc +++ b/bsp/common-pc-64/common-pc-64-standard.scc @@ -10,8 +10,6 @@ include common-pc-64.scc # default policy for standard kernels include cfg/boot-live.scc include cfg/usb-mass-storage.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc include cfg/virtio.scc include features/media/media-usb-webcams.scc include features/sound/snd_hda_intel.scc diff --git a/bsp/common-pc/common-pc-standard.scc b/bsp/common-pc/common-pc-standard.scc index 0b7aade..8f169ba 100644 --- a/bsp/common-pc/common-pc-standard.scc +++ b/bsp/common-pc/common-pc-standard.scc @@ -10,8 +10,6 @@ include common-pc.scc # default policy for standard kernels include cfg/boot-live.scc include cfg/usb-mass-storage.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc include cfg/virtio.scc include features/media/media-usb-webcams.scc include features/sound/snd_hda_intel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v2 00/12] bsp: add developer common-pc BSPs
By using the developer ktype instead of standard, these BSPs have the same functionality of the old -standard BSPs. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/common-pc-64/common-pc-64-developer.scc | 17 + bsp/common-pc/common-pc-developer.scc | 17 + 2 files changed, 34 insertions(+) create mode 100644 bsp/common-pc-64/common-pc-64-developer.scc create mode 100644 bsp/common-pc/common-pc-developer.scc diff --git a/bsp/common-pc-64/common-pc-64-developer.scc b/bsp/common-pc-64/common-pc-64-developer.scc new file mode 100644 index 000..d8da734 --- /dev/null +++ b/bsp/common-pc-64/common-pc-64-developer.scc @@ -0,0 +1,17 @@ +define KMACHINE common-pc-64 +define KMACHINE qemux86-64 +define KTYPE developer +define KARCH x86_64 + +include ktypes/developer/developer.scc + +include common-pc-64.scc + +# default policy for standard kernels +include cfg/boot-live.scc +include cfg/usb-mass-storage.scc +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc +include cfg/virtio.scc +include features/media/media-usb-webcams.scc +include features/sound/snd_hda_intel.scc diff --git a/bsp/common-pc/common-pc-developer.scc b/bsp/common-pc/common-pc-developer.scc new file mode 100644 index 000..ed96c62 --- /dev/null +++ b/bsp/common-pc/common-pc-developer.scc @@ -0,0 +1,17 @@ +define KMACHINE common-pc +define KMACHINE qemux86 +define KTYPE developer +define KARCH i386 + +include ktypes/developer/developer.scc + +include common-pc.scc + +# default policy for standard kernels +include cfg/boot-live.scc +include cfg/usb-mass-storage.scc +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc +include cfg/virtio.scc +include features/media/media-usb-webcams.scc +include features/sound/snd_hda_intel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v2 00/12] intel-common: add intel-developer-drivers.scc to preempt-rt BSPS
Since we include the developer ktype we should include developer drivers. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- 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 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
[linux-yocto] [PATCH v2 00/12] CONFIG_I2C_I801: set option to yes in intel-core* BSPs
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 a developer ktype BSP. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- 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] [PATCH v2 00/12] features/debug: add debug-kernel feature
Since EMBEDDED, EXPERT, and DEBUG_KERNEL are being removed from the base ktype, we can no longer assume DEBUG_KERNEL is enabled. Also add this fragment to features that require DEBUG_KERNEL. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/debug/debug-kernel.cfg| 3 +++ features/debug/debug-kernel.scc| 6 ++ features/debug/printk.scc | 1 + features/latencytop/latencytop.scc | 3 +++ features/profiling/profiling.scc | 2 ++ 5 files changed, 15 insertions(+) create mode 100644 features/debug/debug-kernel.cfg create mode 100644 features/debug/debug-kernel.scc diff --git a/features/debug/debug-kernel.cfg b/features/debug/debug-kernel.cfg new file mode 100644 index 000..cdc07a9 --- /dev/null +++ b/features/debug/debug-kernel.cfg @@ -0,0 +1,3 @@ +CONFIG_DEBUG_KERNEL=y +CONFIG_DEBUG_INFO=y +CONFIG_DEBUG_PREEMPT=y diff --git a/features/debug/debug-kernel.scc b/features/debug/debug-kernel.scc new file mode 100644 index 000..d3325cb --- /dev/null +++ b/features/debug/debug-kernel.scc @@ -0,0 +1,6 @@ + +define KFEATURE_DESCRIPTION "Enable debug kernel and some important debug features" +define KFEATURE_COMPATIBILITY all + +kconf non-hardware debug-kernel.cfg + diff --git a/features/debug/printk.scc b/features/debug/printk.scc index d592605..3526dea 100644 --- a/features/debug/printk.scc +++ b/features/debug/printk.scc @@ -8,3 +8,4 @@ define KFEATURE_COMPATIBILITY all kconf non-hardware printk.cfg +include debug-kernel.scc diff --git a/features/latencytop/latencytop.scc b/features/latencytop/latencytop.scc index 923b5d9..af59e24 100644 --- a/features/latencytop/latencytop.scc +++ b/features/latencytop/latencytop.scc @@ -1,4 +1,7 @@ + define KFEATURE_DESCRIPTION "Enable latencytop" define KFEATURE_COMPATIBILITY arch kconf non-hardware latencytop.cfg + +include features/debug/debug-kernel.scc diff --git a/features/profiling/profiling.scc b/features/profiling/profiling.scc index 32032fa..50cdcfc 100644 --- a/features/profiling/profiling.scc +++ b/features/profiling/profiling.scc @@ -2,3 +2,5 @@ define KFEATURE_DESCRIPTION "Enable profiling and timerstats" define KFEATURE_COMPATIBILITY board kconf non-hardware profiling.cfg + +include features/debug/debug-kernel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH v2 00/12] ktype refactoring: move DEBUG_KERNEL, EXPERT and EMBEDDED
Targetted for yocto-4.4 and master. Changes since last revision: *Renamed extended to developer* More descriptive name than extended. *Add DEBUG_PREEMPT to debug-kernel feature* This is an important debug feature that we should explicitly enable. Enabling CONFIG_DEBUG_MUTEXES was also proposed, but I decided to leave that out for now, as it is new functionality and I want to keep it as close as possible to previous functionality for this refactoring series. *Removed HID disabling patch* We had somebody run into a keyboard not working because the HIDs were not enabled. These will probably be enabled in base eventually. *Removed PROCESSOR_SELECT from intel-core2-32.cfg* Forgot this my first pass. Without EXPERT we don't get this option and the kernel_configcheck task gives us a warning. *Explicitly enable DEBUG_KERNEL in developer.cfg* I want it to be absolutely clear we get DEBUG_KERNEL, even when inheriting developer nocfg. *Updated commit messages Minor things like bsp -> BSP, as well as updates based on the above changes. This patch series refactors the ktypes so that base and standard ktypes do not enable EMBEDDED, EXPERT, or DEBUG_KERNEL. The reason this decision was made is because production platforms likely do not want DEBUG_KERNEL enabled, and EMBEDDED selects EXPERT which selects DEBUG_KERNEL. A new ktype called "developer" was also created. This ktype enables the options now missing from standard and base, making it easy to maintain the functionality of a BSP through simply swapping the ktype from standard to developer. The preempt-rt ktype is now based off of developer in order to maintain its functionality. The new standard ktype does not include EMBEDDED, EXPERT, or DEBUG_KERNEL. Without DEBUG_KERNEL it loses a number of debug features that are selected by default. Without EXPERT it gains RFKILL_INPUT and DEBUG_MEMORY_INIT, while losing VMSPLIT_3G. These are only available to configure with CONFIG_EXPERT=y and default to EXPERT or !EXPERT. Not selecting EMBEDDED has no apparent impacts. Some coordination is required for this change, as existing BSPs WILL be affected, and will either need to accept the changes in the standard ktype or move to the developer ktype. California Sullivan (12): features/debug: add debug-kernel feature ktypes: add developer ktype ktypes/base: Disable EMBEDDED and DEBUG_KERNEL CONFIG_PROCESSOR_SELECT: do not enable intel-common-drivers.scc: move profiling and latencytop to a new file romley.scc remove profiling and latencytop features bsp/intel-common: add intel-core* developer BSPs preempt-rt.scc: inlcude developer ktype instead of standard intel-common: add intel-developer-drivers.scc to preempt-rt BSPS CONFIG_I2C_I801: set option to yes in intel-core* BSPs bsp: add developer common-pc BSPs bsp: remove profiling and latencytop from non-developer common-pc BSPs bsp/common-pc-64/common-pc-64-developer.scc | 17 + bsp/common-pc-64/common-pc-64-standard.scc | 2 -- bsp/common-pc/common-pc-developer.scc | 17 + bsp/common-pc/common-pc-standard.scc| 2 -- bsp/haswell-wc/haswell-wc.cfg | 2 +- bsp/intel-common/intel-common-drivers.scc | 2 -- bsp/intel-common/intel-core2-32-developer.scc | 14 ++ bsp/intel-common/intel-core2-32-preempt-rt.scc | 1 + bsp/intel-common/intel-core2-32.cfg | 1 - bsp/intel-common/intel-corei7-64-developer.scc | 13 + bsp/intel-common/intel-corei7-64-preempt-rt.scc | 1 + bsp/intel-common/intel-developer-drivers.scc| 3 +++ bsp/mohonpeak/mohonpeak.cfg | 2 +- bsp/romley/romley.scc | 3 --- cfg/amd.cfg | 1 - cfg/intel.cfg | 2 -- features/debug/debug-kernel.cfg | 3 +++ features/debug/debug-kernel.scc | 6 ++ features/debug/printk.scc | 1 + features/latencytop/latencytop.scc | 3 +++ features/profiling/profiling.scc| 2 ++ features/soc/baytrail/baytrail.cfg | 2 +- ktypes/base/base.cfg| 6 +++--- ktypes/developer/developer.cfg | 19 +++ ktypes/developer/developer.scc | 10 ++ ktypes/preempt-rt/preempt-rt.scc| 2 +- 26 files changed, 117 insertions(+), 20 deletions(-) create mode 100644 bsp/common-pc-64/common-pc-64-developer.scc create mode 100644 bsp/common-pc/common-pc-developer.scc create mode 100644 bsp/intel-common/intel-core2-32-developer.scc create mode 100644 bsp/intel-common/intel-corei7-64-developer.scc create mode 100644 bsp/intel-common/intel-developer-drivers.scc create mode 100644 features/debug/debug-kernel.cfg create mode 100644 features/debug/debug-kernel.scc create mode 100644 ktypes/developer/developer.cfg
[linux-yocto] [PATCH v2 00/12] CONFIG_PROCESSOR_SELECT: do not enable
The base ktype no longer enables EXPERT, so PROCESSOR_SELECT cannot be enabled by default. Nothing relying on PROCESSOR_SELECT is changed from default, and PROCESSOR_SELECT itself only enables a printk, so this will have no functional change on BSPs using these fragments. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-core2-32.cfg | 1 - cfg/amd.cfg | 1 - cfg/intel.cfg | 2 -- 3 files changed, 4 deletions(-) diff --git a/bsp/intel-common/intel-core2-32.cfg b/bsp/intel-common/intel-core2-32.cfg index ab004ea..b106c76 100644 --- a/bsp/intel-common/intel-core2-32.cfg +++ b/bsp/intel-common/intel-core2-32.cfg @@ -1,5 +1,4 @@ CONFIG_MCORE2=y -CONFIG_PROCESSOR_SELECT=y # max available for this processory family CONFIG_NR_CPUS=8 diff --git a/cfg/amd.cfg b/cfg/amd.cfg index 704b8f7..845d29f 100644 --- a/cfg/amd.cfg +++ b/cfg/amd.cfg @@ -6,7 +6,6 @@ CONFIG_MICROCODE_EARLY=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_EARLY_AMD=y -CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_AMD=y CONFIG_X86_MCE=y diff --git a/cfg/intel.cfg b/cfg/intel.cfg index 4b7ad31..5eb6b08 100644 --- a/cfg/intel.cfg +++ b/cfg/intel.cfg @@ -4,8 +4,6 @@ CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_EARLY=y CONFIG_MICROCODE_INTEL_EARLY=y - -CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_INTEL=y CONFIG_X86_EXTENDED_PLATFORM=y -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 01/13] features/debug: add debug-kernel feature
Since EMBEDDED, EXPERT, and DEBUG_KERNEL are being removed from the base ktype, we can no longer assume DEBUG_KERNEL is enabled. Also add this fragment to features that require DEBUG_KERNEL. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- features/debug/debug-kernel.cfg| 2 ++ features/debug/debug-kernel.scc| 6 ++ features/debug/printk.scc | 1 + features/latencytop/latencytop.scc | 3 +++ features/profiling/profiling.scc | 2 ++ 5 files changed, 14 insertions(+) create mode 100644 features/debug/debug-kernel.cfg create mode 100644 features/debug/debug-kernel.scc diff --git a/features/debug/debug-kernel.cfg b/features/debug/debug-kernel.cfg new file mode 100644 index 000..96a7954 --- /dev/null +++ b/features/debug/debug-kernel.cfg @@ -0,0 +1,2 @@ +CONFIG_DEBUG_KERNEL=y +CONFIG_DEBUG_INFO=y diff --git a/features/debug/debug-kernel.scc b/features/debug/debug-kernel.scc new file mode 100644 index 000..a4527dc --- /dev/null +++ b/features/debug/debug-kernel.scc @@ -0,0 +1,6 @@ + +define KFEATURE_DESCRIPTION "Enable debug kernel" +define KFEATURE_COMPATIBILITY all + +kconf non-hardware debug-kernel.cfg + diff --git a/features/debug/printk.scc b/features/debug/printk.scc index d592605..3526dea 100644 --- a/features/debug/printk.scc +++ b/features/debug/printk.scc @@ -8,3 +8,4 @@ define KFEATURE_COMPATIBILITY all kconf non-hardware printk.cfg +include debug-kernel.scc diff --git a/features/latencytop/latencytop.scc b/features/latencytop/latencytop.scc index 923b5d9..af59e24 100644 --- a/features/latencytop/latencytop.scc +++ b/features/latencytop/latencytop.scc @@ -1,4 +1,7 @@ + define KFEATURE_DESCRIPTION "Enable latencytop" define KFEATURE_COMPATIBILITY arch kconf non-hardware latencytop.cfg + +include features/debug/debug-kernel.scc diff --git a/features/profiling/profiling.scc b/features/profiling/profiling.scc index 32032fa..f0715e1 100644 --- a/features/profiling/profiling.scc +++ b/features/profiling/profiling.scc @@ -1,3 +1,5 @@ +include features/debug/debug-kernel.scc + define KFEATURE_DESCRIPTION "Enable profiling and timerstats" define KFEATURE_COMPATIBILITY board -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 02/13] ktypes: add extended ktype
The extended ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL, opening up more kernel options. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- ktypes/extended/extended.cfg | 18 ++ ktypes/extended/extended.scc | 10 ++ 2 files changed, 28 insertions(+) create mode 100644 ktypes/extended/extended.cfg create mode 100644 ktypes/extended/extended.scc diff --git a/ktypes/extended/extended.cfg b/ktypes/extended/extended.cfg new file mode 100644 index 000..98f79be --- /dev/null +++ b/ktypes/extended/extended.cfg @@ -0,0 +1,18 @@ +#. +#WARNING +# +# This file is a kernel configuration fragment, and not a full kernel +# configuration file. The final kernel configuration is made up of +# an assembly of processed fragments, each of which is designed to +# capture a specific part of the final configuration (e.g. platform +# configuration, feature configuration, and board specific hardware +# configuration). For more information on kernel configuration, please +# consult the product documentation. +# +#. + +# +# General setup +# +CONFIG_EXPERT=y +CONFIG_EMBEDDED=y diff --git a/ktypes/extended/extended.scc b/ktypes/extended/extended.scc new file mode 100644 index 000..eaa94c8 --- /dev/null +++ b/ktypes/extended/extended.scc @@ -0,0 +1,10 @@ +# Include this kernel type fragment to get the standard features and +# configuration values, as well as extended options through EXPERT, +# EMBEDDED, and DEBUG_KERNEL. + +include ktypes/standard/standard.scc +branch standard + +force kconf non-hardware extended.cfg + +include features/debug/debug-kernel.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL
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 <california.l.sulli...@intel.com> --- 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 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 # 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] [PATCH 00/13] ktype refactoring: move DEBUG_KERNEL, EXPERT and EMBEDDED
Targetted for yocto-4.4 and master. This patch series refactors the ktypes so that base and standard ktypes do not enable EMBEDDED, EXPERT, or DEBUG_KERNEL. The reason this decision was made is because production platforms likely do not want DEBUG_KERNEL enabled, and EMBEDDED selects EXPERT which selects DEBUG_KERNEL. A new ktype called "extended" was also created. This ktype enables the options now missing from standard and base, making it easy to maintain the functionality of a BSP through simply swapping the ktype from standard to extended. The preempt-rt ktype is now based off of extended in order to maintain its functionality. The new standard ktype does not include EMBEDDED, EXPERT, or DEBUG_KERNEL. Without DEBUG_KERNEL it loses a number of debug features that are selected by default. Without EXPERT it gains RFKILL_INPUT and DEBUG_MEMORY_INIT, while losing VMSPLIT_3G. These are only available to configure with CONFIG_EXPERT=y and default to EXPERT or !EXPERT. Not selecting EMBEDDED has no apparent impacts. Some coordination is required for this change, as existing BSPs WILL be affected, and will either need to accept the changes in the standard ktype or move to the extended ktype. California Sullivan (13): features/debug: add debug-kernel feature ktypes: add extended ktype ktypes/base: Disable EMBEDDED and DEBUG_KERNEL base.cfg: disable some HIDs cfg: do not enable PROCESSOR_SELECT intel-common-drivers.scc: move profiling and latencytop to a new file romley.scc remove profiling and latencytop features bsp/intel-common: add intel-core* extended bsps preempt-rt.scc: inlcude extended ktype instead of standard intel-common: add intel-extended-drivers.scc to preempt-rt bsps CONFIG_I2C_I801: set option to yes in intel-core* bsps bsp: add extended common-pc bsps bsp: remove profiling and latencytop from non-extended common-pc bsps bsp/common-pc-64/common-pc-64-extended.scc | 17 + bsp/common-pc-64/common-pc-64-standard.scc | 2 -- bsp/common-pc/common-pc-extended.scc| 17 + bsp/common-pc/common-pc-standard.scc| 2 -- bsp/haswell-wc/haswell-wc.cfg | 2 +- bsp/intel-common/intel-common-drivers.scc | 2 -- bsp/intel-common/intel-core2-32-extended.scc| 14 ++ bsp/intel-common/intel-core2-32-preempt-rt.scc | 1 + bsp/intel-common/intel-corei7-64-extended.scc | 13 + bsp/intel-common/intel-corei7-64-preempt-rt.scc | 1 + bsp/intel-common/intel-extended-drivers.scc | 3 +++ bsp/mohonpeak/mohonpeak.cfg | 2 +- bsp/romley/romley.scc | 3 --- cfg/amd.cfg | 1 - cfg/intel.cfg | 2 -- features/debug/debug-kernel.cfg | 2 ++ features/debug/debug-kernel.scc | 6 ++ features/debug/printk.scc | 1 + features/latencytop/latencytop.scc | 3 +++ features/profiling/profiling.scc| 2 ++ features/soc/baytrail/baytrail.cfg | 2 +- ktypes/base/base.cfg| 17 ++--- ktypes/extended/extended.cfg| 18 ++ ktypes/extended/extended.scc| 10 ++ ktypes/preempt-rt/preempt-rt.scc| 2 +- 25 files changed, 126 insertions(+), 19 deletions(-) create mode 100644 bsp/common-pc-64/common-pc-64-extended.scc create mode 100644 bsp/common-pc/common-pc-extended.scc create mode 100644 bsp/intel-common/intel-core2-32-extended.scc create mode 100644 bsp/intel-common/intel-corei7-64-extended.scc create mode 100644 bsp/intel-common/intel-extended-drivers.scc create mode 100644 features/debug/debug-kernel.cfg create mode 100644 features/debug/debug-kernel.scc create mode 100644 ktypes/extended/extended.cfg create mode 100644 ktypes/extended/extended.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 05/13] cfg: do not enable PROCESSOR_SELECT
The base ktype no longer enables EXPERT, so PROCESSOR_SELECT cannot be enabled on all BSPs. Nothing relying on PROCESSOR_SELECT is changed from default, and PROCESSOR_SELECT itself only enables a printk, so this will have no functional change on BSPs using these fragments. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- cfg/amd.cfg | 1 - cfg/intel.cfg | 2 -- 2 files changed, 3 deletions(-) diff --git a/cfg/amd.cfg b/cfg/amd.cfg index 704b8f7..845d29f 100644 --- a/cfg/amd.cfg +++ b/cfg/amd.cfg @@ -6,7 +6,6 @@ CONFIG_MICROCODE_EARLY=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_EARLY_AMD=y -CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_AMD=y CONFIG_X86_MCE=y diff --git a/cfg/intel.cfg b/cfg/intel.cfg index 4b7ad31..5eb6b08 100644 --- a/cfg/intel.cfg +++ b/cfg/intel.cfg @@ -4,8 +4,6 @@ CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_EARLY=y CONFIG_MICROCODE_INTEL_EARLY=y - -CONFIG_PROCESSOR_SELECT=y CONFIG_CPU_SUP_INTEL=y CONFIG_X86_EXTENDED_PLATFORM=y -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs
These options default to !EXPERT. Since we removed EXPERT from base, these became enabled, adding functionality and size that we do not need. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- 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] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in intel-core* bsps
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. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- 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] [PATCH 10/13] intel-common: add intel-extended-drivers.scc to preempt-rt bsps
Since we include the extended ktype we should include extended drivers. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- 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..b62ab91 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-extended-drivers.scc 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..9c1e413 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-extended-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
[linux-yocto] [PATCH 09/13] preempt-rt.scc: inlcude extended ktype instead of standard
The extended ktype now has the functionality of the previous standard ktype. To keep preempt-rt's functionality consistent we must include extended. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- ktypes/preempt-rt/preempt-rt.scc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ktypes/preempt-rt/preempt-rt.scc b/ktypes/preempt-rt/preempt-rt.scc index 5e52ec9..dfa9901 100644 --- a/ktypes/preempt-rt/preempt-rt.scc +++ b/ktypes/preempt-rt/preempt-rt.scc @@ -1,4 +1,4 @@ -include ktypes/standard/standard.scc nocfg +include ktypes/extended/extended.scc nocfg branch preempt-rt # aufs doesn't even build with preempt-rt kernels -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 06/13] intel-common-drivers.scc: move profiling and latencytop to a new file
Profiling and latencytop enable DEBUG_KERNEL, which is no longer a standard config option. Move these features to a new file called intel-extended-drivers.scc, which is to be included in intel extended bsps. Signed-off-by: California Sullivan <california.l.sulli...@intel.com> --- bsp/intel-common/intel-common-drivers.scc | 2 -- bsp/intel-common/intel-extended-drivers.scc | 3 +++ 2 files changed, 3 insertions(+), 2 deletions(-) create mode 100644 bsp/intel-common/intel-extended-drivers.scc diff --git a/bsp/intel-common/intel-common-drivers.scc b/bsp/intel-common/intel-common-drivers.scc index a7673e7..9beef28 100644 --- a/bsp/intel-common/intel-common-drivers.scc +++ b/bsp/intel-common/intel-common-drivers.scc @@ -76,5 +76,3 @@ include cfg/efi-ext.scc # default policy for standard kernels include cfg/usb-mass-storage.scc include cfg/boot-live.scc -include features/latencytop/latencytop.scc -include features/profiling/profiling.scc diff --git a/bsp/intel-common/intel-extended-drivers.scc b/bsp/intel-common/intel-extended-drivers.scc new file mode 100644 index 000..a78348e --- /dev/null +++ b/bsp/intel-common/intel-extended-drivers.scc @@ -0,0 +1,3 @@ +# Additional features for extended bsps +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
