Thanks Daniel and Bob,
Agree, DT is good enough for initial settings. But when need to support
on the fly parameter changes, we will end up with 2 solutions. Adding KMS
ioctls or improvising blob prop infrastructure (Ruled out existing KMS 64bit
props as list of parameters is close to 30, as if
On Tue, 4 Mar 2014 09:35:57 +0100
Daniel Vetter wrote:
> On Thu, Feb 20, 2014 at 11:24:40AM +1000, Dave Airlie wrote:
> > > I am working on enabling a Color Enhancement block for primary display
> > > for Exynos SoC. I need to
> > > set a bunch of parameters like Color Conversion matrix,
On Thu, Feb 20, 2014 at 11:24:40AM +1000, Dave Airlie wrote:
> > I am working on enabling a Color Enhancement block for primary display
> > for Exynos SoC. I need to
> > set a bunch of parameters like Color Conversion matrix, Contrast
> > Improvement parameters etc ~ 30 parameters from User Space.
> I am working on enabling a Color Enhancement block for primary display
> for Exynos SoC. I need to
> set a bunch of parameters like Color Conversion matrix, Contrast
> Improvement parameters etc ~ 30 parameters from User Space.
>
> I am planning to use KDS blob property to receive these
Thanks Dave,
On 20 February 2014 06:54, Dave Airlie wrote:
>> I am working on enabling a Color Enhancement block for primary display
>> for Exynos SoC. I need to
>> set a bunch of parameters like Color Conversion matrix, Contrast
>> Improvement parameters etc ~ 30 parameters from User Space.
>>
.
Currently drivers are not allowed to create a blob property inside
drm. Neither, user space can set the blob. There is no ioctl provided
for same.
How about adding set_blob ioctl in DRM? It seems purposely dropped
till now. Please help me
in understanding explains the rationale.
What
