DRM_IMX_FB_HELPER config is currently used to enable/disable fbdev emulation for
the imx kms driver.
Remove this local config option and use the top level DRM_FBDEV_EMULATION config
option where applicable. Using this config lets us also prevent wrapping around
drm_fb_helper_* calls with #ifdefs
DRM_I915_FBDEV config is currently used to enable/disable fbdev emulation for
the i915 kms driver.
Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
config lets us also prevent wrapping around drm_fb_helper_* calls with #ifdefs
in certain places.
The #ifdef in
DRM_STI_FBDEV config is currently used to enable/disable fbdev emulation for
the sti kms driver.
Remove this local config option and use the top level DRM_FBDEV_EMULATION config
option instead where applicable.
We replace the #ifdef in sti_drm_load with CONFIG_DRM_FBDEV_EMULATION. It's
probably
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by selecting
KMS FB helpers. A few provide a separate Kconfig option for the user to enable
or disbale fbdev emulation.
Enabling fbdev emulation is finally
DRM_MSM_FBDEV config is used to enable/disable fbdev emulation for the msm kms
driver.
Replace this with the top level DRM_FBDEV_EMULATION config option where
applicable. This also prevents build breaks caused by undefined drm_fb_helper_*
functions when legacy fbdev support was disabled.
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by selecting
KMS FB helpers. A few provide
On Tue, Mar 10, 2015 at 03:11:30PM +0530, Archit Taneja wrote:
DRM_I915_FBDEV config is currently used to enable/disable fbdev emulation for
the i915 kms driver.
Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
config lets us also prevent wrapping around
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by
selecting
KMS FB helpers. A few provide a separate Kconfig option for the user to
On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide
On 03/10/2015 03:31 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:30PM +0530, Archit Taneja wrote:
DRM_I915_FBDEV config is currently used to enable/disable fbdev emulation for
the i915 kms driver.
Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
config
On Mon, Mar 09, 2015 at 09:16:36AM -0600, Lina Iyer wrote:
@@ -105,18 +109,46 @@ static int __init arm_idle_init(void)
if (ret = 0)
return ret ? : -ENODEV;
+
A bit better formatting would be nice - you don't need the extra blank
line here.
+ ret =
+static bool inject_cmd_hang_tr(struct ufs_hba *hba)
+{
+ int tag;
+
+ tag = find_first_bit(hba-outstanding_reqs, hba-nutrs);
+ if (tag == hba-nutrs)
+ return 0;
+
+ __clear_bit(tag, hba-outstanding_reqs);
+ hba-lrb[tag].cmd = NULL;
+
Changes from V4:
Dropped error injection change titled:
scsi: ufs: inject errors to verify error handling
Dolev Raviv (1):
scsi: ufs: add ioctl interface for query request
Gilad Broner (1):
scsi: ufs: add trace events and dump prints for debug
Lee Susman (1):
scsi: ufs: add debugfs for
On Tue, Mar 10, 2015 at 03:52:41PM +0530, Archit Taneja wrote:
On 03/10/2015 03:35 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
diff --git
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by
selecting
KMS FB helpers. A few provide a separate Kconfig option for the user to
On Tue, Mar 10, 2015 at 10:10:56AM +0200, Ivan T. Ivanov wrote:
On Mon, 2015-03-09 at 18:28 +, Mark Brown wrote:
About the API usage, point taken. GPIO requesting part is more important
in this case. pinctrl core did not request pins and wrong DT configuration
could lead to
DRM_TEGRA_FBDEV config is currently used to enable/disable fbdev emulation for
the tegra kms driver.
Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
config lets us also prevent wrapping around drm_fb_helper_* calls with #ifdefs
in certain places.
The #ifdef in
On 03/10/2015 03:35 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB
This provides a uniform interface to enable/disable legacy fbdev support for
modesetting drivers, based on the discussion here:
http://lists.freedesktop.org/archives/dri-devel/2015-March/078729.html
This has only been build-tested for a few devices. Mainly looking for comments
for now.
The
On 03/10/2015 03:16 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by selecting
KMS FB helpers. A few provide
Ping.
On Mon, 2015-02-23 at 11:59 +0200, Ivan T. Ivanov wrote:
Hi Gilad,
On Thu, 2015-02-19 at 15:54 -0700, Gilad Avidov wrote:
Qualcomm PMIC Arbiter version-2 changes from version-1 are:
- Some different register offsets.
- New channel register space, one per PMIC peripheral
Hi Archit,
thanks for the cleanup!
Am Dienstag, den 10.03.2015, 15:11 +0530 schrieb Archit Taneja:
DRM_IMX_FB_HELPER config is currently used to enable/disable fbdev emulation
for
the imx kms driver.
Remove this local config option and use the top level DRM_FBDEV_EMULATION
config
From: Lee Susman lsus...@codeaurora.org
Adding debugfs capability for ufshcd.
debugfs attributes introduced in this patch:
- View driver/controller runtime data
- Command tag statistics for performance analisis
- Dump device descriptor info
- Track recoverable errors statistics during
Add trace events to driver to allow monitoring and profilig
of activities such as PM suspend/resume, hibernate enter/exit,
clock gating and clock scaling up/down.
In addition, add UFS host controller register dumps to provide
detailed information in case of errors to assist in analysis
of issues.
2015-03-10 19:20 GMT+09:00 Gilad Broner gbro...@codeaurora.org:
+static bool inject_cmd_hang_tr(struct ufs_hba *hba)
+{
+ int tag;
+
+ tag = find_first_bit(hba-outstanding_reqs, hba-nutrs);
+ if (tag == hba-nutrs)
+ return 0;
+
+ __clear_bit(tag,
On Tue, 2015-03-10 at 11:06 +, Mark Brown wrote:
On Tue, Mar 10, 2015 at 10:10:56AM +0200, Ivan T. Ivanov wrote:
On Mon, 2015-03-09 at 18:28 +, Mark Brown wrote:
About the API usage, point taken. GPIO requesting part is more important
in this case. pinctrl core did not
On 03/10/2015 09:03 PM, Jani Nikula wrote:
On Tue, 10 Mar 2015, Archit Taneja arch...@codeaurora.org wrote:
On 03/10/2015 03:35 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at
On 03/10/2015 04:24 PM, Philipp Zabel wrote:
Hi Archit,
thanks for the cleanup!
Am Dienstag, den 10.03.2015, 15:11 +0530 schrieb Archit Taneja:
DRM_IMX_FB_HELPER config is currently used to enable/disable fbdev emulation for
the imx kms driver.
Remove this local config option and use the
On Tue, Mar 10, 2015 at 10:13 AM, Kumar Gala ga...@codeaurora.org wrote:
On Mar 9, 2015, at 7:11 AM, Arnd Bergmann a...@arndb.de wrote:
On Friday 06 March 2015 14:37:52 Kumar Gala wrote:
On Mar 6, 2015, at 1:15 PM, Olof Johansson o...@lixom.net wrote:
On Fri, Mar 6, 2015 at 8:08 AM, Kumar
On Mar 9, 2015, at 10:16 AM, Lina Iyer lina.i...@linaro.org wrote:
SPM is a hardware block that controls the peripheral logic surrounding
the application cores (cpu/l$). When the core executes WFI instruction,
the SPM takes over the putting the core in low power state as
configured. The wake
The top level qcom,msm-id and qcom,board-id are utilized by
bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc: devicet...@vger.kernel.org
Signed-off-by: Kumar Gala ga...@codeaurora.org
Is this the special magic that
On Mar 9, 2015, at 7:11 AM, Arnd Bergmann a...@arndb.de wrote:
On Friday 06 March 2015 14:37:52 Kumar Gala wrote:
On Mar 6, 2015, at 1:15 PM, Olof Johansson o...@lixom.net wrote:
On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala ga...@codeaurora.org wrote:
On Mar 5, 2015, at 7:59 PM, Olof
On Tue, Mar 10 2015 at 04:37 -0600, Russell King - ARM Linux wrote:
On Mon, Mar 09, 2015 at 09:16:36AM -0600, Lina Iyer wrote:
@@ -105,18 +109,46 @@ static int __init arm_idle_init(void)
if (ret = 0)
return ret ? : -ENODEV;
+
A bit better formatting would be nice -
On Tue, 10 Mar 2015, Archit Taneja arch...@codeaurora.org wrote:
On 03/10/2015 03:35 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
On Tue, Mar 10, 2015 at 02:53:17PM +0200, Ivan T. Ivanov wrote:
On Tue, 2015-03-10 at 11:06 +, Mark Brown wrote:
I'm sorry but I can't parse the above. What does they could issue
setup method mean and why is it a problem?
Client drivers could execute spi_setup() in probe(), so we
On Tue, Mar 10 2015 at 11:26 -0600, Kumar Gala wrote:
On Mar 9, 2015, at 10:16 AM, Lina Iyer lina.i...@linaro.org wrote:
SPM is a hardware block that controls the peripheral logic surrounding
the application cores (cpu/l$). When the core executes WFI instruction,
the SPM takes over the
On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
The top level qcom,msm-id and qcom,board-id are utilized by
bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc: devicet...@vger.kernel.org
Signed-off-by: Kumar Gala
On Mar 10, 2015, at 2:52 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
The top level qcom,msm-id and qcom,board-id are utilized by
bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
On Tue, Mar 10, 2015 at 3:52 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
The top level qcom,msm-id and qcom,board-id are utilized by
bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the
On Mon, 2015-03-09 at 18:28 +, Mark Brown wrote:
On Mon, Mar 09, 2015 at 10:23:35AM +0200, Ivan T. Ivanov wrote:
Hi,
Don't reply off list unless there's a good reason...
Sorry, it was not intentional. Wrong button.
Any new GPIO users should really be using the gpiod API, however
40 matches
Mail list logo
