On Sat, 25 Jan 2020 at 00:30, Christian König
wrote:
>
> From: Christian König
>
> While working on TTM cleanups I've found that the io_reserve_lru used by
> Nouveau is actually not working at all.
>
> In general we should remove driver specific handling from the memory
> management, so this
On 2020-01-27 at 16:10:32 -0500, Sean Paul wrote:
> On Mon, Jan 27, 2020 at 11:42:31PM +0530, Ramalingam C wrote:
> > As we are not using the sysfs infrastructure anymore, link to it is
> > removed. And global srm data and mutex to protect it are removed,
> > with required handling at revocation
From: Uma Shankar
CEA 861.3 spec adds colorimetry data block for HDMI.
Parsing the block to get the colorimetry data from
panel.
This was posted by Uma Shankar at
https://patchwork.kernel.org/patch/10861327/
Modified by Abhinav Kumar:
- Use macros to distinguish the bit fields for clarity
Hi all,
On Wed, 8 Jan 2020 17:08:03 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the generic-ioremap tree got a conflict in:
>
> drivers/gpu/drm/i915/i915_gem_gtt.c
>
> between commit:
>
> 2c86e55d2ab5 ("drm/i915/gtt: split up i915_gem_gtt")
>
> from the drm-intel tree
On Fri, Jan 24, 2020 at 3:03 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> Let's try to make a lot more stuff const in the edid parser.
>
> The "downside" is that we can no longer mangle the EDID in the
> middle of the parsing to apply quirks (drm_mode_detailed()).
> I don't really think
On Fri, Jan 24, 2020 at 3:03 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> I'm curious if there are any bogus 18 byte descriptors around.
> Let's dump them out if we encounter them.
>
> Not sure we'd actually want this, but at least I get to see
> if our CI has anything that hits this :)
>
On Fri, Jan 24, 2020 at 3:02 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> Let's introduce is_detailed_timing_descritor() as the opposite
> counterpart of is_display_descriptor().
>
> Cc: Allen Chen
> Signed-off-by: Ville Syrjälä
Acked-by: Alex Deucher
> ---
>
On Fri, Jan 24, 2020 at 3:02 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> Currently we assume any 18 byte descriptor to be a display descritor
> if only the tag byte matches the expected value. But for detailed
> timing descriptors that same byte is just the lower 8 bits of
> hblank, and
On Fri, Jan 24, 2020 at 3:03 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> CEA-861 says :
> "d = offset for the byte following the reserved data block.
> If no data is provided in the reserved data block, then d=4.
> If no DTDs are provided, then d=0."
>
> So let's not look for DTDs when
On Fri, Jan 24, 2020 at 3:02 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> I don't understand what the DispID CEA data block revision
> means. The spec doesn't say. I guess some DispID must have
> a value of >= 3 in there or else we generally wouldn't
> even parse the CEA data blocks. Or
On Fri, Jan 24, 2020 at 3:03 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> After much head scratching I managed to convince myself that
> for_each_displayid_db() has already done the bounds checks for
> the DispID CEA data block. Which is why we don't need to repeat
> them in
Hi,
On Mon, Jan 27, 2020 at 1:30 AM Sharat Masetty wrote:
>
> This patch adds the required dt nodes and properties
> to enabled A618 GPU.
>
> Signed-off-by: Sharat Masetty
> ---
> arch/arm64/boot/dts/qcom/sc7180.dtsi | 103
> +++
> 1 file changed, 103
Title should be s/i915/edid/ , with that fixed:
Reviewed-by: Alex Deucher
On Fri, Jan 24, 2020 at 3:03 PM Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> Nuke some whitespace that shouldn't be there.
>
> Signed-off-by: Ville Syrjälä
> ---
> drivers/gpu/drm/drm_edid.c | 6 +++---
> 1 file
On Mon, Jan 27, 2020 at 11:42:31PM +0530, Ramalingam C wrote:
> As we are not using the sysfs infrastructure anymore, link to it is
> removed. And global srm data and mutex to protect it are removed,
> with required handling at revocation check function.
>
> v2:
> srm_data is dropped and few
On Mon, Jan 27, 2020 at 8:52 AM Benjamin Gaignard
wrote:
>
> Convert etnaviv bindings to yaml format.
>
> Signed-off-by: Benjamin Gaignard
> ---
> .../bindings/display/etnaviv/etnaviv-drm.txt | 36 ---
> .../bindings/display/etnaviv/etnaviv-drm.yaml | 72
>
Hi Stephen
On 2020-01-27 10:46, Stephen Boyd wrote:
Quoting Abhinav Kumar (2020-01-23 14:40:45)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 99769d6..148bfa4 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drivers/gpu/drm/drm_edid.c
@@ -4199,6 +4200,57 @@ static
Applied. Thanks!
Alex
On Sat, Jan 25, 2020 at 3:26 PM Colin King wrote:
>
> From: Colin Ian King
>
> There are several spelling mistakes in PP_ASSERT_WITH_CODE messages.
> Fix these.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/gpu/drm/amd/powerplay/smumgr/vega12_smumgr.c | 12
Applied with Walter's comment included.
Thanks!
Alex
On Fri, Jan 17, 2020 at 9:45 AM walter harms wrote:
>
>
>
> Am 17.01.2020 14:33, schrieb Colin King:
> > From: Colin Ian King
> >
> > A for-loop is iterating from 0 up to 1000 however the loop variable count
> > is a u8 and hence not large
On Mon, Jan 27, 2020 at 12:56:33PM +0200, Peter Ujfalusi wrote:
> TC358768/TC358778 is a Parallel RGB to MIPI DSI bridge.
>
> Signed-off-by: Peter Ujfalusi
> ---
> .../display/bridge/toshiba,tc358768.yaml | 158 ++
> 1 file changed, 158 insertions(+)
> create mode 100644
Hi Emil
Am 27.01.20 um 19:12 schrieb Emil Velikov:
> Hi Thomas,
>
> On Thu, 23 Jan 2020 at 09:21, Thomas Zimmermann wrote:
>
>> @@ -174,12 +174,22 @@ struct drm_crtc_state {
>> * @no_vblank:
>> *
>> * Reflects the ability of a CRTC to send VBLANK events. This state
As we are not using the sysfs infrastructure anymore, link to it is
removed. And global srm data and mutex to protect it are removed,
with required handling at revocation check function.
v2:
srm_data is dropped and few more comments are addressed.
Signed-off-by: Ramalingam C
Suggested-by:
Hi Thomas,
On Thu, 23 Jan 2020 at 09:21, Thomas Zimmermann wrote:
> @@ -174,12 +174,22 @@ struct drm_crtc_state {
> * @no_vblank:
> *
> * Reflects the ability of a CRTC to send VBLANK events. This state
> -* usually depends on the pipeline configuration, and
On Mon, 27 Jan 2020 18:26:52 +0100
Daniel Vetter wrote:
> On Mon, Jan 27, 2020 at 12:00:32PM +0100, Boris Brezillon wrote:
> > One of the last remaining objects to not have its atomic state.
> >
> > This is being motivated by our attempt to support runtime bus-format
> > negotiation between
On Mon, Jan 27, 2020 at 12:00:32PM +0100, Boris Brezillon wrote:
> One of the last remaining objects to not have its atomic state.
>
> This is being motivated by our attempt to support runtime bus-format
> negotiation between elements of the bridge chain.
> This patch just paves the road for such
On Wed, Jan 22, 2020 at 11:54:59AM +0100, Yuti Amonkar wrote:
> Document the bindings used for the Cadence MHDP DPI/DP bridge in
> yaml format.
>
> Signed-off-by: Yuti Amonkar
> ---
> .../bindings/display/bridge/cdns,mhdp.yaml | 131
> +
> 1 file changed, 131
This patch adds a new DRM driver for Texas Instruments DSS IPs used on
Texas Instruments Keystone K2G, AM65x, and J721e SoCs. The new DSS IP is
a major change to the older DSS IP versions, which are supported by
the omapdrm driver. While on higher level the Keystone DSS resembles
the older DSS
On Tue, 21 Jan 2020 16:43:14 +0100, Dafna Hirschfeld wrote:
> convert the binding file rockchip-drm.txt to yaml format.
> This was tested and verified on ARM and ARM64 with:
> make dt_binding_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/rockchip/rockchip-drm.yaml
> make
On Thu, Jan 23, 2020 at 09:19:04AM -0800, Matt Roper wrote:
> On Thu, Jan 23, 2020 at 05:45:41PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > To make it easier to figure out what caused a particular debug
> > message let's print out aux->name.
> >
> > Signed-off-by: Ville Syrjälä
Add entry for tidss DRM driver.
Version history:
v2: no change
v3: - Move tidss entry after omapdrm
- Add "T: git git://anongit.freedesktop.org/drm/drm-misc"
v4: no change
v5: no change
v6: no change
v7: no change
v8: - Add Reviewed-by: Benoit Parrot
v9: - Add Signed-off-by: Tomi
This is intended to be the last patch series. I'll apply these trough
drm-misc-next tomorrow.
Changes since v8:
- "dt-bindings: display: ti,k2g-dss: Add dt-schema yaml binding"
- Remove ports-node from the dts example in
- "drm/tidss: New driver for TI Keystone platform Display SubSystem"
-
Add dt-schema yaml bindig for K2G DSS, an ultra-light version of TI
Keystone Display SubSystem.
Version history:
v2: no change
v3: - Add ports node
- Add includes to dts example
- reindent dts example
v4: - Add descriptions to reg and clocks properties
- Remove minItems when its
Add dt-schema yaml bindig for J721E DSS, J721E version TI Keystone
Display SubSystem.
Version history:
v2: no change
v3: - reg-names: "wp" -> "wb"
- Add ports node
- Add includes to dts example
- reindent dts example
v4: - Add descriptions to reg, clocks, and interrupts properties
Add dt-schema yaml bindig for AM65x DSS, AM65x version TI Keystone
Display SubSystem.
Version history:
v2: no change
v3: - Add ports node
- use allOf in ti,am65x-oldi-io-ctrl to add both $ref and maxItems
- Add includes to dts example
- reindent dts example
v4: - Add descriptions
On Mon, 27 Jan 2020 12:00:40 +0100, Boris Brezillon wrote:
> Add the bus-width property to describe the input bus format.
>
> Signed-off-by: Boris Brezillon
> ---
> Changes in v7:
> * Rebase on top of lvds-codec changes
> * Drop the data-mapping property
>
> Changes in v3:
> * New patch
> ---
>
Den 27.01.2020 15.26, skrev Kamlesh Gurudasani:
> This adds support fot ilitek,ili9486 based displays with shift register
> in front of controller.
> Ozzmaker,Piscreen and Waveshare,rpi-lcd-35 are such displays.
>
> Signed-off-by: Kamlesh Gurudasani
> ---
Reviewed-by: Noralf Trønnes
When
On Sun, 26 Jan 2020 23:12:00 +0530, Kamlesh Gurudasani wrote:
> This binding is for the tft displays based on ilitek,ili9486.
> ozzmaker,piscreen and waveshare,rpi-lcd-35 are such displays
>
> Signed-off-by: Kamlesh Gurudasani
> ---
>
> v2 changes:
> * Changing file from txt to yaml format
> *
Thanks, applied to drm-misc-next.
Regards,
Qiang
On Mon, Jan 27, 2020 at 6:21 PM Andreas Baierl wrote:
>
> Am 16.01.2020 um 14:11 schrieb Qiang Yu:
> > Support heap buffer allocation which can grow the back memory
> > size when GP has an out of memory interrupt so that user don't
> > need to
On Fri, Jan 17, 2020 at 2:31 PM Sean Paul wrote:
>
> From: Sean Paul
>
> Hey all,
> Here's v3, which addresses all review comments in v2.
>
Friendly ping
Sean
> Sean
>
> Sean Paul (12):
> drm/i915: Fix sha_text population code
> drm/i915: Clear the repeater bit on HDCP disable
>
On 1/24/20 5:01 PM, Lyude Paul wrote:
On Fri, 2020-01-24 at 16:46 -0500, Lyude Paul wrote:
On Fri, 2020-01-24 at 14:20 -0500, Mikita Lipski wrote:
On 1/24/20 2:10 PM, Lyude Paul wrote:
Disabling a display on MST can potentially happen after the entire MST
topology has been removed, which
Hi Boris,
On Mon, 2020-01-27 at 12:00 +0100, Boris Brezillon wrote:
> Now that bridges can expose the bus format/flags they expect, we can
> use those instead of the relying on the display_info provided by the
> connector (which is only valid if the encoder is directly connected
> to bridge
Le ven. 24 janv. 2020 à 23:08, Lyude Paul a écrit :
>
> On Tue, 2020-01-07 at 14:11 +0100, Benjamin Gaignard wrote:
> > Le ven. 20 déc. 2019 à 15:03, Benjamin Gaignard
> > a écrit :
> > > Le lun. 16 déc. 2019 à 09:28, Benjamin Gaignard
> > > a écrit :
> > > > Le mer. 4 déc. 2019 à 17:47, Jani
Den 26.01.2020 18.42, skrev Kamlesh Gurudasani:
> This adds support fot ilitek,ili9486 based displays with shift register
> in front of controller.
> Ozzmaker,Piscreen and Waveshare,rpi-lcd-35 are such displays.
>
> Signed-off-by: Kamlesh Gurudasani
> ---
Reviewed-by: Noralf Trønnes
I'll
On 1/27/20 11:02 AM, Daniel Vetter wrote:
vmwgfx stopped using them.
With the drm device model that we've slowly evolved over the past few
years master status essentially controls access to display resources,
and nothing else. Since that's a pure access permission check drivers
should have no
Hi Marek,
On Mon, Jan 27, 2020 at 5:16 AM Marek Vasut wrote:
>
> From: Sean Cross
>
> The Innolux N133HSE panel is a 13.3" 1920x1080 panel that contains an
> integrated backlight, and connects via eDP.
>
> It is used in the Kosagi Novena.
>
> Signed-off-by: Sean Cross
> Cc: Shawn Guo
> Cc:
On Mon, Jan 27, 2020 at 11:40:24AM +0100, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Sun, Jan 26, 2020 at 8:44 AM Greg Kroah-Hartman
> wrote:
> >
> > On Sat, Jan 25, 2020 at 02:55:06PM -0500, Rich Felker wrote:
> > > Signed-off-by: Rich Felker
> > > --
> >
> > I know I don't accept patches
On 27/01/2020 12.56, Peter Ujfalusi wrote:
> Add basic support for the Toshiba TC358768 RGB to DSI bridge.
> Not all the features of the TC358768 is implemented by the initial driver:
> MIPI_DSI_MODE_VIDEO and MIPI_DSI_FMT_RGB888 is only supported and tested.
>
> Only write is implemented for
Hi
Am 27.01.20 um 10:53 schrieb Oleksandr Andrushchenko:
> Sorry for jumping in late
>
> On 1/23/20 11:21 AM, Thomas Zimmermann wrote:
>> The atomic helpers automatically send out fake VBLANK events if no
>> vblanking has been initialized. This would apply to xen, but xen has
>> its own vblank
Am 27.01.20 um 11:02 schrieb Daniel Vetter:
> vmwgfx stopped using them.
>
> With the drm device model that we've slowly evolved over the past few
> years master status essentially controls access to display resources,
> and nothing else. Since that's a pure access permission check drivers
>
The current definition does not represent the exact display pipeline we
have on the board: the LVDS panel is actually connected through a
parallel -> LVDS bridge. Let's fix that so the driver can select the
proper bus format on the CRTC end.
Signed-off-by: Boris Brezillon
---
Changes in v7:
*
Some DPI -> LVDS encoders might support several input bus width. Add a
DT property to describe the bus width used on a specific design.
Signed-off-by: Boris Brezillon
---
Changes in v7:
* Fix a use-after-release problem
* Get rid of the data-mapping parsing
* Use kmalloc instead of kcalloc.
One of the last remaining objects to not have its atomic state.
This is being motivated by our attempt to support runtime bus-format
negotiation between elements of the bridge chain.
This patch just paves the road for such a feature by adding a new
drm_bridge_state object inheriting from
Add the bus-width property to describe the input bus format.
Signed-off-by: Boris Brezillon
---
Changes in v7:
* Rebase on top of lvds-codec changes
* Drop the data-mapping property
Changes in v3:
* New patch
---
.../devicetree/bindings/display/bridge/lvds-codec.yaml| 8
1 file
Hello,
This patch series aims at adding support for runtime bus-format
negotiation between all elements of the
'encoder -> bridges -> connector/display' section of the pipeline.
In order to support that, we need drm bridges to fully take part in the
atomic state validation process, which
This way the drm_bridge_funcs interface is consistent with the rest of
the subsystem.
The only driver implementing those hooks (analogix DP) is patched too.
Signed-off-by: Boris Brezillon
Reviewed-by: Laurent Pinchart
Signed-off-by: Neil Armstrong
[narmstrong: renamed state as
The lt089ac29000 panel is an LVDS panel, not a DPI one. Fix the
definition to reflect this fact.
Signed-off-by: Boris Brezillon
Suggested-by: Laurent Pinchart
---
Changes in v7:
* New patch
---
drivers/gpu/drm/panel/panel-simple.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
drm_bridge_state is extended to describe the input and output bus
configurations. These bus configurations are exposed through the
drm_bus_cfg struct which encodes the configuration of a physical
bus between two components in an output pipeline, usually between
two bridges, an encoder and a
Now that bridges can expose the bus format/flags they expect, we can
use those instead of the relying on the display_info provided by the
connector (which is only valid if the encoder is directly connected
to bridge element driving the panel/display).
We also explicitly expose the bus formats
This is needed to pass a bridge state to all atomic hooks, if we don't
do that, the core can't duplicate/create bridge states.
Signed-off-by: Boris Brezillon
Reviewed-by: Neil Armstrong
---
Changes in v9:
* Add Neil's R-b
* Move earlier in the series
Changes in v7:
* New patch
---
So that the previous bridge element in the chain knows which input
format the panel bridge expects.
Signed-off-by: Boris Brezillon
---
Changes in v7:
* Set atomic state hooks explicitly
Changes in v3:
* Adjust things to match the new bus-format negotiation approach
* Use
This is needed to pass a bridge state to all atomic hooks, if we don't
do that, the core can't duplicate/create bridge states.
Signed-off-by: Boris Brezillon
Reviewed-by: Neil Armstrong
---
Changes in v9:
* Add Neil's R-b
* Move earlier in the series
Changes in v7:
* New patch
---
So that bridge drivers have a way to check/reject an atomic operation.
The drm_atomic_bridge_chain_check() (which is just a wrapper around
the ->atomic_check() hook) is called in place of
drm_bridge_chain_mode_fixup() (when ->atomic_check() is not implemented,
the core falls back on
Hi,
Changes since v2:
- Implement pre_enable and post_disbale callbacks and move code from enable and
disable callbacks.
- hw_enable/disable is removed from tc358768_dsi_host_transfer()
- Defines for DSI_CONFW accesses
- breakout from the loops (the check for it) is moved one level up in
TC358768/TC358778 is a Parallel RGB to MIPI DSI bridge.
Signed-off-by: Peter Ujfalusi
---
.../display/bridge/toshiba,tc358768.yaml | 158 ++
1 file changed, 158 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml
diff
Add basic support for the Toshiba TC358768 RGB to DSI bridge.
Not all the features of the TC358768 is implemented by the initial driver:
MIPI_DSI_MODE_VIDEO and MIPI_DSI_FMT_RGB888 is only supported and tested.
Only write is implemented for mipi_dsi_host_ops.transfer.
Signed-off-by: Peter
Hi Greg,
On Sun, Jan 26, 2020 at 8:44 AM Greg Kroah-Hartman
wrote:
>
> On Sat, Jan 25, 2020 at 02:55:06PM -0500, Rich Felker wrote:
> > Signed-off-by: Rich Felker
> > --
>
> I know I don't accept patches without any changelog text, don't know
> about other subsystem maintainers...
FTR, I do,
On 23/01/2020 10:53, Boris Brezillon wrote:
> This is needed to pass a bridge state to all atomic hooks, if we don't
> do that, the core can't duplicate/create bridge states.
>
> Signed-off-by: Boris Brezillon
> ---
> Changes in v7:
> * New patch
> ---
> drivers/gpu/drm/rcar-du/rcar_lvds.c | 3
On 23/01/2020 10:53, Boris Brezillon wrote:
> This is needed to pass a bridge state to all atomic hooks, if we don't
> do that, the core can't duplicate/create bridge states.
>
> Signed-off-by: Boris Brezillon
> ---
> Changes in v7:
> * New patch
> ---
> drivers/gpu/drm/rcar-du/rcar_lvds.c | 3
Am 16.01.2020 um 14:11 schrieb Qiang Yu:
Support heap buffer allocation which can grow the back memory
size when GP has an out of memory interrupt so that user don't
need to allocate a very large buffer at the beginning.
This was
Tested-by: Andreas Baierl
together with
Hi Anatoli,
FYI, the error/warning still remains.
tree: git://people.freedesktop.org/~agd5f/linux.git amd-19.50
head: f9a0b7ad3447d7766dda9923e63a5f4d0be7ce47
commit: c3612b68d1358e8325c377ba5e1f690b39a6cea8 [1967/2713] drm/amdkcl: Test
whether drm_gem_object_put_unlocked() is available
vmwgfx stopped using them.
With the drm device model that we've slowly evolved over the past few
years master status essentially controls access to display resources,
and nothing else. Since that's a pure access permission check drivers
should have no need at all to track additional state on a
On Thu, Jan 23, 2020 at 10:21:23AM +0100, Thomas Zimmermann wrote:
> The atomic helpers automatically send out fake VBLANK events if no
> vblanking has been initialized. This would apply to xen, but xen has
> its own vblank logic. To avoid interfering with the atomic helpers,
> disable automatic
On Thu, Jan 23, 2020 at 10:21:09AM +0100, Thomas Zimmermann wrote:
> At the end of a commit, atomic helpers can generate a VBLANK event
> automatically. Originally implemented for writeback connectors, the
> functionality can be used by any driver and/or hardware without proper
> VBLANK interrupt.
This patch adds the required dt nodes and properties
to enabled A618 GPU.
Signed-off-by: Sharat Masetty
---
arch/arm64/boot/dts/qcom/sc7180.dtsi | 103 +++
1 file changed, 103 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi
On Sat, 25 Jan 2020, Chris Wilson wrote:
> Quoting Wambui Karuga (2020-01-22 12:57:48)
>> This series is a part of the conversion to the new struct drm_device
>> based logging macros in drm/i915.
>> This series focuses on the drm/i915/gem directory and converts all
>> straightforward instances
On Fri, Jan 24, 2020 at 12:56:26PM +, Chris Wilson wrote:
> The file is not part of the global drm resource and can be released
> prior to take the global mutex to drop the open_count (and potentially
> close) the drm device. As the global mutex is indeed global, not only
> within the device
On Fri, Jan 24, 2020 at 08:41:48PM +, Chris Wilson wrote:
> For largely legacy reasons, a global mutex (drm_global_mutex) is taken
> around open/close of the drm_device, including serialising the filp
> release. For drivers with their own fine grained locking, such global
> coordination is a
On Fri, Jan 24, 2020 at 06:39:26PM +, Chris Wilson wrote:
> Quoting Thomas Hellström (VMware) (2020-01-24 13:37:47)
> > On 1/24/20 2:01 PM, Chris Wilson wrote:
> > > Since drm_global_mutex is a true global mutex across devices, we don't
> > > want to acquire it unless absolutely necessary. For
On Mon, Jan 27, 2020 at 09:08:01AM +, Chris Wilson wrote:
> Quoting Daniel Vetter (2020-01-27 09:05:57)
> > On Sat, Jan 25, 2020 at 04:08:39PM +, Chris Wilson wrote:
> > > Quoting Wambui Karuga (2020-01-22 12:57:48)
> > > > This series is a part of the conversion to the new struct
Quoting Daniel Vetter (2020-01-27 09:05:57)
> On Sat, Jan 25, 2020 at 04:08:39PM +, Chris Wilson wrote:
> > Quoting Wambui Karuga (2020-01-22 12:57:48)
> > > This series is a part of the conversion to the new struct drm_device
> > > based logging macros in drm/i915.
> > > This series focuses
On Sat, Jan 25, 2020 at 04:08:39PM +, Chris Wilson wrote:
> Quoting Wambui Karuga (2020-01-22 12:57:48)
> > This series is a part of the conversion to the new struct drm_device
> > based logging macros in drm/i915.
> > This series focuses on the drm/i915/gem directory and converts all
> >
On Wed, Jan 22, 2020 at 10:00:58AM -0600, David Lechner wrote:
> On 1/22/20 4:54 AM, Andy Shevchenko wrote:
> > The spi_register_driver() will set the ->owner member to THIS_MODULE.
> >
> > Signed-off-by: Andy Shevchenko
> > ---
> Reviewed-by: David Lechner
Btw to avoid confusion: Since your
On Mon, 27 Jan 2020, "Bharadiya,Pankaj"
wrote:
> On Thu, Jan 23, 2020 at 11:39:37AM +0200, Jani Nikula wrote:
>> On Thu, 23 Jan 2020, "Bharadiya,Pankaj"
>> wrote:
>> > Will rebase remaining patches and submit.
>>
>> Please also add a patch to convert MISSING_CASE(),
>
> Will do.
>
>> and
On Wed, Jan 22, 2020 at 10:39:15AM -0500, Sean Paul wrote:
> On Wed, Jan 22, 2020 at 3:06 AM Daniel Vetter wrote:
> >
> > On Mon, Jan 20, 2020 at 01:56:21PM -0500, Steven Rostedt wrote:
> > > On Thu, 16 Jan 2020 07:27:22 +0100
> > > Daniel Vetter wrote:
> > >
> > > > On Tue, Jan 14, 2020 at
On Thu, Jan 23, 2020 at 11:39:37AM +0200, Jani Nikula wrote:
> On Thu, 23 Jan 2020, "Bharadiya,Pankaj"
> wrote:
> > Will rebase remaining patches and submit.
>
> Please also add a patch to convert MISSING_CASE(),
Will do.
> and another to remove
> the WARN_ON/WARN_ON_ONCE "overrides" that we
On Sat, Jan 25, 2020 at 04:51:08PM +0200, Jani Nikula wrote:
> On Thu, 23 Jan 2020, Pankaj Bharadiya
> wrote:
> > changes since v2:
> > - rebase pending unmerged patches on drm-tip
>
> Alas, these conflict already... please rebase. :/
Ahh :( ... Looks like other changes are merged before you
Signed-off-by: Rich Felker
--
I've had this lying around a while and figure I should send it
upsteam; it's needed to support the onboard video on my Spectre-free
Atom S1260 server board.
---
drivers/video/fbdev/matrox/matroxfb_base.c | 15 +++
1 file changed, 15 insertions(+)
diff
From: Sean Cross
The Innolux N133HSE panel is a 13.3" 1920x1080 panel that contains an
integrated backlight, and connects via eDP.
It is used in the Kosagi Novena.
Signed-off-by: Sean Cross
Cc: Shawn Guo
Cc: Fabio Estevam
Cc: Thierry Reding
To: dri-devel@lists.freedesktop.org
---
Hi Jernej,
On Sun 26 Jan 20, 07:59, Jernej Skrabec wrote:
> This reverts commit 9db9c0cf5895e4ddde2814360cae7bea9282edd2.
>
> Setting mode_config.allow_fb_modifiers manually is completely
> unnecessary. It is set automatically by drm_universal_plane_init() based
> on the fact if modifier list is
Add vendor prefix for ITE Tech Inc, http://www.ite.com.tw/
Signed-off-by: Marek Vasut
Cc: Daniel Vetter
Cc: Rob Herring
Cc: Sean Cross
Cc: devicet...@vger.kernel.org
To: dri-devel@lists.freedesktop.org
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2
Add driver for the ITE IT6251 LVDS-to-eDP bridge.
Signed-off-by: Marek Vasut
Cc: Daniel Vetter
Cc: Sean Cross
To: dri-devel@lists.freedesktop.org
---
drivers/gpu/drm/bridge/Kconfig | 9 +
drivers/gpu/drm/bridge/Makefile | 1 +
drivers/gpu/drm/bridge/ite-it6251.c | 582
This reverts commit 9db9c0cf5895e4ddde2814360cae7bea9282edd2.
Setting mode_config.allow_fb_modifiers manually is completely
unnecessary. It is set automatically by drm_universal_plane_init() based
on the fact if modifier list is provided or not. Even more, it breaks
DE2 and DE3 as they don't
Krzysztof Kozlowski wrote:
> The ioreadX() helpers have inconsistent interface. On some architectures
> void *__iomem address argument is a pointer to const, on some not.
>
> Implementations of ioreadX() do not modify the memory under the address
> so they can be converted to a "const" version
From: Michael Srba
This patch adds dts bindings for Samsung AMS452EF01 AMOLED panel, which makes
use of their S6E88A0 controller.
Signed-off-by: Michael Srba
---
.../panel/samsung,s6e88a0-ams452ef01.txt | 26 +++
1 file changed, 26 insertions(+)
create mode 100644
This binding is for the tft displays based on ilitek,ili9486.
ozzmaker,piscreen and waveshare,rpi-lcd-35 are such displays
Signed-off-by: Kamlesh Gurudasani
---
v2 changes:
* Changing file from txt to yaml format
* removed ilitek,ili9486 from compatible string
---
The goal of this series is to get the display based on ilitek,ili9486 working
Kamlesh Gurudasani (2):
dt-bindings: add binding for Ilitek ili9486 based display panels
drm/tinydrm: add support for ilitek,ili9486 based displays with
regwidth=16
On Fri, 10 Jan 2020 at 02:53, Nicolas Boichat wrote:
>
> +Ulf to keep me honest on the power domains
>
> On Thu, Jan 9, 2020 at 10:08 PM Steven Price wrote:
> >
> > On 08/01/2020 05:23, Nicolas Boichat wrote:
> > > When there is a single power domain per device, the core will
> > > ensure the
Add DT bindings for ITE IT6251 LVDS-to-eDP bridge.
Signed-off-by: Marek Vasut
Cc: Daniel Vetter
Cc: Rob Herring
Cc: Sean Cross
Cc: devicet...@vger.kernel.org
To: dri-devel@lists.freedesktop.org
---
.../bindings/display/bridge/ite,it6251.txt| 35 +++
1 file changed, 35
This adds support fot ilitek,ili9486 based display with shift register in front
of controller, basically with regwidth=16
Signed-off-by: Kamlesh Gurudasani
---
MAINTAINERS| 7 +
drivers/gpu/drm/tiny/Kconfig | 14 ++
drivers/gpu/drm/tiny/Makefile | 1 +
The goal of this series is to get the displays based on ilitek,ili9486
working.
Ozzmaker, Piscreen and waveshare,rpi-lcd-35 are such displays.
v2 changes:
* Changing file from txt to yaml format
* removed ilitek,ili9486 from compatible string
* assignment of dbi_command before registration
*
From: Michael Srba
Add a driver for Samsung AMS452EF01 AMOLED panel, which makes use of their
S6E88A0 controller. Basic functionality is supported, with the only notable
feature missing being backlight control. Backlight control on these panels is
complex and hard to make look nice, mainly
1 - 100 of 108 matches
Mail list logo
