On Thu, 24 Oct 2019, Jacopo Mondi wrote:
> Hello,
>
> On Thu, Oct 24, 2019 at 07:47:26AM +0100, Lee Jones wrote:
> > On Wed, 23 Oct 2019, Daniel Thompson wrote:
> >
> > > On Tue, Oct 22, 2019 at 11:29:54AM +0200, Bartosz Golaszewski wrote:
> > > > wt., 22 paź 2019 o 10:36 Bartosz Golaszewski
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: c3612b68d1358e8325c377ba5e1f690b39a6cea8 [1967/2647] drm/amdkcl: Test
whether drm_gem_object_put_unlocked() is available
config: x86_64-randconfig-g002-201943
Hello,
I'm looking at the available options to support overlays in the display
pipeline of the i.MX7. The LCDIF itself unfortunaltey doesn't support
overlays, the feature being implemented in the PXP. A driver for the PXP
is available but only supports older SoCs whose PXP doesn't support
On Thu, 31 Oct 2019 13:57:00 -0400
Kenny Ho wrote:
> Hi Yiwei,
>
> This is the latest series:
> https://patchwork.kernel.org/cover/11120371/
>
> (I still need to reply some of the feedback.)
>
> Regards,
> Kenny
>
> On Thu, Oct 31, 2019 at 12:59 PM Yiwei Zhang wrote:
> >
> > Hi Kenny,
> >
>
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 757a363a37449c5b612b3c7c3f62be125b1282e3 [1966/2647] drm/amdkcl: Test
whether drm_get_format_name() is available
config: x86_64-randconfig-g002-201943 (attached as
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: c450088041e3378cd3b78d99169e9bca8fd20a5b [1965/2647] drm/amdkcl: Test
whether drm_gem_object_lookup() wants 2 args
config: x86_64-randconfig-g002-201943 (attached
On 10/31/19 2:09 PM, Ira Weiny wrote:
> On Thu, Oct 31, 2019 at 11:43:37AM -0700, John Hubbard wrote:
>> On 10/31/19 11:35 AM, Ira Weiny wrote:
>>> On Wed, Oct 30, 2019 at 03:49:13PM -0700, John Hubbard wrote:
>> ...
+
+static int __huge_pt_done(struct page *head, int nr_recorded_pages,
Hello,
I'm trying to update from the kernel 4.17.17 to 5.3 on a Utilite pro
(GC2000) but I'm running a bit into trouble:
When on 4.17.17 I can run X11 with the armada driver and I get proper
OpenGL, with 5.3, the same user space, and the same kernel config
querying the chip specs via
On 10/31/19 11:35 AM, Ira Weiny wrote:
> On Wed, Oct 30, 2019 at 03:49:13PM -0700, John Hubbard wrote:
...
>> +
>> +static void __remove_refs_from_head(struct page *page, int refs)
>> +{
>> +/* Do a get_page() first, in case refs == page->_refcount */
>> +get_page(page);
>> +
On Thu Oct 24, 2019 at 10:50 AM Drew DeVault wrote:
> So, I'm not sure what the action items are here. It seems like we might
> have uncovered a potentially icky race condition in Linux, but that this
> protocol is not really affected.
Bump. Happy halloween!
Update the bindings with the new properties used for
PMI8998.
Signed-off-by: Kiran Gunda
Reviewed-by: Bjorn Andersson
Reviewed-by: Rob Herring
Acked-by: Daniel Thompson
---
.../bindings/leds/backlight/qcom-wled.txt | 74 ++
1 file changed, 63 insertions(+), 11
On 10/31/19 4:49 PM, Ira Weiny wrote:
> On Wed, Oct 30, 2019 at 03:49:30PM -0700, John Hubbard wrote:
...
>> +TODO: There is also a special case when the pages are DAX pages: in
>> addition to
>> +the above flags, the caller needs something like a layout lease on the
>> +associated file. This is
Hi Kenny,
Thanks for the info. Do you mind forwarding the existing discussion to me
or have me cc'ed in that thread?
Best,
Yiwei
On Wed, Oct 30, 2019 at 10:23 PM Kenny Ho wrote:
> Hi Yiwei,
>
> I am not sure if you are aware, there is an ongoing RFC on adding drm
> support in cgroup for the
On 2019/10/31 6:26, Dmitry Osipenko wrote:
> 30.10.2019 16:54, YueHaibing пишет:
>> If IOMMU_SUPPORT is not set, but IOMMU_IOVA is m and
>> COMPILE_TEST is y, building fails:
>>
>> drivers/gpu/host1x/dev.o: In function `host1x_remove':
>> dev.c:(.text+0x624): undefined reference to
On 10/30/19 11:52 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next releases on Friday (Nov 1) or Monday
> (Nov 4).
>
> Changes since 20191030:
>
on i386:
ld: drivers/gpu/drm/drm_dp_mst_topology.o: in function
`__dump_topology_ref_history':
Rename the PM8941* references as WLED3 to make the driver
generic and have WLED support for other PMICs. Also rename
"i_boost_limit" and "i_limit" variables to "boost_i_limit"
and "string_i_limit" respectively to resemble the corresponding
register names.
Signed-off-by: Kiran Gunda
Reviewed-by:
pm8941-wled.c driver is supporting the WLED peripheral
on pm8941. Rename it to qcom-wled.c so that it can support
WLED on multiple PMICs.
Signed-off-by: Kiran Gunda
Reviewed-by: Bjorn Andersson
Acked-by: Rob Herring
Acked-by: Daniel Thompson
Acked-by: Pavel Machek
---
Joe Perches writes:
> On Wed, 2019-10-30 at 21:12 +0100, Andrea Righi wrote:
>> Then memset() + memcpy() is probably the best option,
>> since copying all those fields one by one looks quite ugly to me...
>
> A memset of an automatic before a memcpy to the same
> automatic is unnecessary.
You
lp855x forgets to disable enable regulator when remove.
Add a call to regulator_disable in remove just like what is done to
supply regulator.
Signed-off-by: Chuhong Yuan
---
drivers/video/backlight/lp855x_bl.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
This patch series renames the pm8941-wled.c driver to qcom-wled.c to add
the support for multiple PMICs supported by qualcomm. This patch series
supports both PM8941 and PMI8998 WLED. The PMI8998 WLED has the support
to handle the OVP (over voltage protection) and the SC (short circuit
protection)
31.10.2019 16:33, Yuehaibing пишет:
> On 2019/10/31 6:26, Dmitry Osipenko wrote:
>> 30.10.2019 16:54, YueHaibing пишет:
>>> If IOMMU_SUPPORT is not set, but IOMMU_IOVA is m and
>>> COMPILE_TEST is y, building fails:
>>>
>>> drivers/gpu/host1x/dev.o: In function `host1x_remove':
>>>
Restructure the qcom-wled bindings for the better readability.
Signed-off-by: Kiran Gunda
Reviewed-by: Bjorn Andersson
Reviewed-by: Rob Herring
Acked-by: Daniel Thompson
Acked-by: Pavel Machek
---
.../bindings/leds/backlight/qcom-wled.txt | 110 -
1 file
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c: In function vmw_hw_surface_destroy:
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c:335:22: warning: variable srf set but
not used [-Wunused-but-set-variable]
It is introduced by commit 543831cfc976 ("drm/vmwgfx:
On Tue, Oct 29, 2019 at 02:00:27AM -0600, Jonathan Corbet wrote:
> On Tue, 29 Oct 2019 08:31:22 +0800
> Changbin Du wrote:
>
> > Here python is different from C. Both empty string and None are False in
> > python.
> > Note such condition is common in python.
>
> Treating both as a False value
On 10/31/19 4:25 PM, Ira Weiny wrote:
> On Wed, Oct 30, 2019 at 03:49:18PM -0700, John Hubbard wrote:
>> Convert infiniband to use the new wrapper calls, and stop
>> explicitly setting FOLL_LONGTERM at the call sites.
>>
>> The new pin_longterm_*() calls replace get_user_pages*()
>> calls, and set
WLED4 peripheral is present on some PMICs like pmi8998 and
pm660l. It has a different register map and configurations
are also different. Add support for it.
Signed-off-by: Kiran Gunda
Reviewed-by: Bjorn Andersson
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/qcom-wled.c | 255
The auto string detection algorithm checks if the current WLED
sink configuration is valid. It tries enabling every sink and
checks if the OVP fault is observed. Based on this information
it detects and enables the valid sink configuration.
Auto calibration will be triggered when the OVP fault
On Thu, Oct 31, 2019 at 01:51:00PM +0100, Maxime Ripard wrote:
> On Tue, Oct 29, 2019 at 01:16:57PM +0100, Torsten Duwe wrote:
> > +
> > + ports:
> > +anyOf:
> > + - port@0:
> > +description: Video port for LVTTL input
> > + - port@1:
> > +description: Video port for
Restructure the driver to add the support for new WLED
peripherals.
Signed-off-by: Kiran Gunda
Acked-by: Daniel Thompson
---
drivers/video/backlight/qcom-wled.c | 373 ++--
1 file changed, 234 insertions(+), 139 deletions(-)
diff --git
On 10/31/19 4:15 PM, Ira Weiny wrote:
> On Wed, Oct 30, 2019 at 03:49:16PM -0700, John Hubbard wrote:
...
>> + * FOLL_PIN indicates that a special kind of tracking (not just
>> page->_refcount,
>> + * but an additional pin counting system) will be invoked. This is intended
>> for
>> + * anything
On 10/31/19 4:49 PM, Ira Weiny wrote:
> On Wed, Oct 30, 2019 at 03:49:30PM -0700, John Hubbard wrote:
>> Document the new pin_user_pages() and related calls
>> and behavior.
>>
>> Thanks to Jan Kara and Vlastimil Babka for explaining the 4 cases
>> in this documentation. (I've reworded it and
On 2019-10-31 14:28, Lee Jones wrote:
On Wed, 23 Oct 2019, Kiran Gunda wrote:
Update the bindings with the new properties used for
PMI8998.
Signed-off-by: Kiran Gunda
Reviewed-by: Bjorn Andersson
Reviewed-by: Rob Herring
Acked-by: Daniel Thompson
---
Handle the short circuit interrupt and check if the short circuit
interrupt is valid. Re-enable the module to check if it goes
away. Disable the module altogether if the short circuit event
persists.
Signed-off-by: Kiran Gunda
Reviewed-by: Bjorn Andersson
Reviewed-by: Daniel Thompson
---
On 10/31/19 4:35 PM, Ira Weiny wrote:
> On Wed, Oct 30, 2019 at 03:49:19PM -0700, John Hubbard wrote:
>> Convert process_vm_access to use the new pin_user_pages_remote()
>> call, which sets FOLL_PIN. Setting FOLL_PIN is now required for
>> code that requires tracking of pinned pages.
>>
>> Also,
On Wed, Oct 30, 2019 at 09:44:20AM -0500, Adam Ford wrote:
> On Wed, Oct 16, 2019 at 8:52 AM Adam Ford wrote:
> >
> > Previously, there was an omap panel-dpi driver that would
> > read generic timings from the device tree and set the display
> > timing accordingly. This driver was removed so the
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: aa5f7e64d5afdf1b60cb7594bc78632997b6eb38 [1964/2647] drm/amdkcl: Test
whether drm_universal_plane_init() wants 9 args or 8 args
config:
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: f2e0d469732d27bc612df52b42094309ba5877d9 [1963/2647] drm/amdkcl: Test
whether drm_crtc_init_with_planes() wants name
config: x86_64-randconfig-g002-201943 (attached
On Mon, Oct 21, 2019 at 04:47:35PM +, Mihail Atanassov wrote:
> It's possible to get multiple events in a single frame/flip, so add an
> option to print them all.
>
> Signed-off-by: Mihail Atanassov
Reviewed-by: James Qian Wang (Arm Technology China)
> ---
>
On Mon, Oct 21, 2019 at 04:47:29PM +, Mihail Atanassov wrote:
> Extra detail (normally off) almost never hurts.
>
> Signed-off-by: Mihail Atanassov
Reviewed-by: James Qian Wang (Arm Technology China)
> ---
> drivers/gpu/drm/arm/display/komeda/komeda_dev.h | 11 +++
>
On Mon, Oct 21, 2019 at 04:47:19PM +, Mihail Atanassov wrote:
> Now that there's a debugfs node to control the same, remove the
> config option.
>
> Signed-off-by: Mihail Atanassov
> ---
> drivers/gpu/drm/arm/display/Kconfig | 6 --
>
On Mon, Oct 21, 2019 at 04:47:24PM +, Mihail Atanassov wrote:
> It's potentially useful information when diagnosing error/warn IRQs, so
> dump it to dmesg with a drm_info_printer. Hide this extra debug dumping
> behind another komeda_dev->err_verbosity bit.
>
> Note that there's not much
On Mon, Oct 21, 2019 at 04:47:14PM +, Mihail Atanassov wrote:
> Named 'err_verbosity', currently with only 1 active bit in that
> replicates the existing level - print error events once per flip.
>
> Signed-off-by: Mihail Atanassov
> ---
> drivers/gpu/drm/arm/display/komeda/komeda_dev.c |
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.2
head: b027ed8d9051470f4ed6bc071fcde172fe1fc595
commit: 35781c0b8d19ed0d1bdb8cfa85780841ea7985ff [1962/2647] drm/amdkcl: Test
whether drm_encoder_init() wants name
config: x86_64-randconfig-g002-201943 (attached as
This function is for converting drm_color_ctm matrix to komeda hardware
required required Q2.12 2's complement CSC matrix.
v2:
Move the fixpoint conversion function s31_32_to_q2_12() to drm core
as a shared helper.
Signed-off-by: james qian wang (Arm Technology China)
Reviewed-by: Mihail
This series actually are regrouped from:
- drm/komeda: Enable layer/plane color-mgmt:
https://patchwork.freedesktop.org/series/60893/
- drm/komeda: Enable CRTC color-mgmt
https://patchwork.freedesktop.org/series/61370/
For removing the dependence on:
-
Add a new helper function drm_color_ctm_s31_32_to_qm_n() for driver to
convert S31.32 sign-magnitude to Qm.n 2's complement that supported by
hardware.
V4: Address Mihai, Daniel and Ilia's review comments.
V5: Includes the sign bit in the value of m (Qm.n).
V6: Allows m = 0 according to Mihail's
From: "Lowry Li (Arm Technology China)"
Adds gamma and color-transform support for DOU-IPS.
Adds two caps members fgamma_coeffs and ctm_coeffs to komeda_improc_state.
If color management changed, set gamma and color-transform accordingly.
v5: Rebase with drm-misc-next
Signed-off-by: Lowry Li
This function is used to convert drm color lut to komeda HW required curve
coeffs values.
Signed-off-by: james qian wang (Arm Technology China)
Reviewed-by: Mihail Atanassov
---
.../arm/display/komeda/komeda_color_mgmt.c| 52 +++
.../arm/display/komeda/komeda_color_mgmt.h
101 - 148 of 148 matches
Mail list logo