On 08/26/2016 01:10 AM, Daniel Vetter wrote:
> On Thu, Aug 25, 2016 at 05:55:18PM +0530, Archit Taneja wrote:
>> On 08/18/2016 02:26 AM, Daniel Vetter wrote:
>>> +void drm_mode_object_unregister(struct drm_device *dev,
>>> + struct drm_mode_object *object);
>>
>> Alignme
Add support for the JDI LT070ME05000 WUXGA DSI panel used in
Nexus 7 2013 devices.
Programming sequence for the panel is was originally found in the
android-msm-flo-3.4-lollipop-release branch from:
https://android.googlesource.com/kernel/msm.git
And video mode setting is from dsi-panel-jdi-d
Add documentation for lt070me05000 panel
Cc: Archit Taneja
Cc: John Stultz
Cc: Thierry Reding
Cc: Sumit Semwal
Signed-off-by: Vinay Simha BN
Acked-by: Rob Herring
---
v2:
* incorporated rob herring and thierry reviews
gpio to gpios, gpio to regulator using fixed regulators
and pwm ba
On Fri, Aug 26, 2016 at 2:00 AM, David Herrmann
wrote:
> Provide a generic DRM helper that evicts all conflicting firmware
> framebuffers, devices, and drivers. The new helper is called
> drm_evict_firmware(), and takes a flagset controlling which firmware to
> kick out.
>
> This is meant to be u
On Thu, Aug 25, 2016 at 7:03 AM, Jyri Sarha wrote:
> Add "blue-and-red-crossed"-device tree property and update devicetree
> binding document. The red and blue components are reversed between 24
> and 16 bit modes on am335x LCDC output pins. To get 24 RGB format the
> red and blue wires has to be
Hi,
I am sending this posting to dri-devel mailing list and Dave Airlie.
This is sort of a summary of where OpenChrome and drm-openchrome is now.
https://lists.freedesktop.org/archives/dri-devel/2016-August/116736.html
I know that drm-openchrome is still not mainlined, and I am not the original
On Thu, Aug 25, 2016 at 7:00 PM, David Herrmann
wrote:
> Provide a generic DRM helper that evicts all conflicting firmware
> framebuffers, devices, and drivers. The new helper is called
> drm_evict_firmware(), and takes a flagset controlling which firmware to
> kick out.
>
> This is meant to be u
> base on dfi result, we do ddr frequency scaling, register
> dmc driver to devfreq framework, and use simple-ondemand
> policy.
>
> Signed-off-by: Lin Huang
> Reviewed-by: Chanwoo Choi
> ---
Thanks. LGTM.
Signed-off-by: MyungJoo Ham
Cheers,
MyungJoo.
On Thu, Aug 25, 2016 at 11:57 PM, Archit Taneja
wrote:
> Hi Rob,
>
> On 06/23/2016 07:43 PM, Archit Taneja wrote:
>>
>> The MSM8916 SoC contains a MDP5 based display block, and one DSI output.
>> Add the top level MDSS DT node, and the MDP5, DSI and DSI PHY children
>> sub-blocks. Establish the l
Reviewed-by: Sinclair Yeh
On Fri, Aug 19, 2016 at 10:50:38PM +0200, Daniel Vetter wrote:
> Everyone knows them, except all the new folks joining from the ARM
> side haven't lived through all the pain of the past years and are
> entirely surprised when I raise this. Definitely time to document
> t
Hi Connor,
> > r128 is 90% the same as early radeons so it would make sense to add
> > support to radeon.
> >
> > Alex
>
> Ccing Kevin Brace.
>
> The drivers were removed from mesa and "you won't have to freeze your
> kernel or anything" was one of the justifications given at the time for
> why
Hi Emil,
> Hi Kevin,
>
> On 26 August 2016 at 01:19, Kevin Brace wrote:
>
> > I do not want to be seen as stopping progress, but there are still people
> > who use less than current hardware (myself and countless others) or non Big
> > 3 x86 graphics (NVIDIA, AMD, and Intel) for things like t
Hi Kevin,
On 26 August 2016 at 01:19, Kevin Brace wrote:
> I do not want to be seen as stopping progress, but there are still people who
> use less than current hardware (myself and countless others) or non Big 3 x86
> graphics (NVIDIA, AMD, and Intel) for things like thin clients.
[snip]
> A
Hi David,
> Lets move forward and hide the remaining DRI1 drivers behind a config
> option, so we have a central place to disable them all. Furthermore, we
> can provide a clear warning to anyone enabling them.
>
> Signed-off-by: David Herrmann
> ---
> drivers/gpu/drm/Kconfig | 135
> +
Provide a generic DRM helper that evicts all conflicting firmware
framebuffers, devices, and drivers. The new helper is called
drm_evict_firmware(), and takes a flagset controlling which firmware to
kick out.
This is meant to be used by drivers in their ->probe() callbacks of their
parent bus, bef
> on rk3399 platform, there is dfi conroller can monitor
> ddr load, base on this result, we can do ddr freqency
> scaling.
>
> Signed-off-by: Lin Huang
> Acked-by: Chanwoo Choi
LGTM
Signed-off-by: MyungJoo Ham
Even if PR3 support is available on the bridge, it will not be used if
the PCI layer considers it unavailable (i.e. on all laptops from 2013
and 2014). Ensure that this condition is checked to allow a fallback to
the Optimus DSM for device poweroff.
Initially I wanted to call pci_d3cold_enable bef
On Thu, Jun 23, 2016 at 07:43:30PM +0530, Archit Taneja wrote:
> The APQ8016-sbc provides a HDMI output. The APQ8016 display block only
> provides a MIPI DSI output. So, the board has a ADV7533 DSI to HDMI
> encoder chip that sits between the DSI PHY output and the HDMI
> connector.
>
> Add the AD
On Thu, Jun 23, 2016 at 07:43:29PM +0530, Archit Taneja wrote:
> The MSM8916 SoC contains a MDP5 based display block, and one DSI output.
> Add the top level MDSS DT node, and the MDP5, DSI and DSI PHY children
> sub-blocks. Establish the link between MDP5's INTF1 output port and DSI's
> input port
Den 23.08.2016 08:17, skrev Daniel Vetter:
> On Mon, Aug 22, 2016 at 10:25:23PM +0200, Noralf Trønnes wrote:
>> The SimpleDRM driver binds to simple-framebuffer devices and provides a
>> DRM/KMS API. It provides only a single CRTC+encoder+connector combination
>> plus one initial mode.
>>
>> User
101 - 120 of 120 matches
Mail list logo
