Hi Jacopo,
On 12/09/2019 08:59, Jacopo Mondi wrote:
> Hi Kiernan,
> thanks for review
>
> On Wed, Sep 11, 2019 at 04:54:58PM +0100, Kieran Bingham wrote:
>> Hi Jacopo,
>>
>> <This time replying to the mail with ML's included Doh!>
>>
>> On 06/09/2019 14:43, Jacopo Mondi wrote:
>>> Add a driver for the R-Car Display Unit Color Correction Module.
>>>
>>> In most of Gen3 SoCs, each DU output channel is provided with a CMM unit
>>> to perform image enhancement and color correction.
>>>
>>> Add support for CMM through a driver that supports configuration of
>>> the 1-dimensional LUT table. More advanced CMM feature will be
>>
>> s/feature/features/
>>
>>> implemented on top of this basic one.
>>
>> s/basic/initial/
>>
>>>
>>> Signed-off-by: Jacopo Mondi <jacopo+renesas@xxxxxxxxxx>
>>> ---
>>> drivers/gpu/drm/rcar-du/Kconfig | 7 +
>>> drivers/gpu/drm/rcar-du/Makefile | 1 +
>>> drivers/gpu/drm/rcar-du/rcar_cmm.c | 251 +++++++++++++++++++++++++++++
>>> drivers/gpu/drm/rcar-du/rcar_cmm.h | 61 +++++++
>>> 4 files changed, 320 insertions(+)
>>> create mode 100644 drivers/gpu/drm/rcar-du/rcar_cmm.c
>>> create mode 100644 drivers/gpu/drm/rcar-du/rcar_cmm.h
>>>
>>> diff --git a/drivers/gpu/drm/rcar-du/Kconfig
>> b/drivers/gpu/drm/rcar-du/Kconfig
>>> index 1529849e217e..539d232790d1 100644
>>> --- a/drivers/gpu/drm/rcar-du/Kconfig
>>> +++ b/drivers/gpu/drm/rcar-du/Kconfig
>>> @@ -13,6 +13,13 @@ config DRM_RCAR_DU
>>> Choose this option if you have an R-Car chipset.
>>> If M is selected the module will be called rcar-du-drm.
>>>
>>> +config DRM_RCAR_CMM
>>> + bool "R-Car DU Color Management Module (CMM) Support"
>>> + depends on DRM && OF
>>> + depends on DRM_RCAR_DU
>>> + help
>>> + Enable support for R-Car Color Management Module (CMM).
>>> +
>>> config DRM_RCAR_DW_HDMI
>>> tristate "R-Car DU Gen3 HDMI Encoder Support"
>>> depends on DRM && OF
>>> diff --git a/drivers/gpu/drm/rcar-du/Makefile
>> b/drivers/gpu/drm/rcar-du/Makefile
>>> index 6c2ed9c46467..4d1187ccc3e5 100644
>>> --- a/drivers/gpu/drm/rcar-du/Makefile
>>> +++ b/drivers/gpu/drm/rcar-du/Makefile
>>> @@ -15,6 +15,7 @@ rcar-du-drm-$(CONFIG_DRM_RCAR_LVDS) += rcar_du_of.o \
>>> rcar-du-drm-$(CONFIG_DRM_RCAR_VSP) += rcar_du_vsp.o
>>> rcar-du-drm-$(CONFIG_DRM_RCAR_WRITEBACK) += rcar_du_writeback.o
>>>
>>> +obj-$(CONFIG_DRM_RCAR_CMM) += rcar_cmm.o
>>> obj-$(CONFIG_DRM_RCAR_DU) += rcar-du-drm.o
>>> obj-$(CONFIG_DRM_RCAR_DW_HDMI) += rcar_dw_hdmi.o
>>> obj-$(CONFIG_DRM_RCAR_LVDS) += rcar_lvds.o
>>> diff --git a/drivers/gpu/drm/rcar-du/rcar_cmm.c
>> b/drivers/gpu/drm/rcar-du/rcar_cmm.c
>>> new file mode 100644
>>> index 000000000000..3cacdc4474c7
>>> --- /dev/null
>>> +++ b/drivers/gpu/drm/rcar-du/rcar_cmm.c
>>> @@ -0,0 +1,251 @@
>>> +// SPDX-License-Identifier: GPL-2.0+
>>> +/*
>>> + * rcar_cmm.c -- R-Car Display Unit Color Management Module
>>> + *
>>> + * Copyright (C) 2019 Jacopo Mondi <jacopo+renesas@xxxxxxxxxx>
>>> + */
>>> +
>>> +#include <linux/io.h>
>>> +#include <linux/module.h>
>>> +#include <linux/of.h>
>>> +#include <linux/platform_device.h>
>>> +#include <linux/pm_runtime.h>
>>> +
>>> +#include <drm/drm_color_mgmt.h>
>>> +
>>> +#include "rcar_cmm.h"
>>> +
>>> +#define CM2_LUT_CTRL 0x0000
>>> +#define CM2_LUT_CTRL_LUT_EN BIT(0)
>>
>> I'd have a new line here
>>
>>> +#define CM2_LUT_TBL_BASE 0x0600
>>> +#define CM2_LUT_TBL(__i) (CM2_LUT_TBL_BASE + (__i) * 4)
>>> +
>>> +struct rcar_cmm {
>>> + void __iomem *base;
>>> + bool enabled;
>>> +
>>> + /*
>>> + * @lut: 1D-LUT status
>>> + * @lut.enabled: 1D-LUT enabled flag
>>> + * @lut.table: Table of 1D-LUT entries scaled to hardware
>>> + * precision (8-bits per color component)
>>> + */
>>> + struct {
>>> + bool enabled;
>>> + u32 table[CM2_LUT_SIZE];
>>> + } lut;
>>> +};
>>> +
>>> +static inline int rcar_cmm_read(struct rcar_cmm *rcmm, u32 reg)
>>> +{
>>> + return ioread32(rcmm->base + reg);
>>> +}
>>> +
>>> +static inline void rcar_cmm_write(struct rcar_cmm *rcmm, u32 reg, u32
>> data)
>>> +{
>>> + iowrite32(data, rcmm->base + reg);
>>> +}
>>> +
>>> +/*
>>> + * rcar_cmm_lut_extract() - Scale down to hardware precision the DRM
>> LUT table
>>> + * entries and store them.
>>> + * @rcmm: Pointer to the CMM device
>>> + * @drm_lut: Pointer to the DRM LUT table
>>> + */
>>> +static void rcar_cmm_lut_extract(struct rcar_cmm *rcmm,
>>> + const struct drm_color_lut *drm_lut)
>>> +{
>>> + unsigned int i;
>>
>> I think you're missing the following here:
>>
>> if (!drm_lut)
>> return;
>>
>> You mention below that drm_lut could be passed in as NULL, which would
>> cause a segfault here otherwise.
>>
>
> Thanks for spotting, but I should have removed that comment, as I have
> killed that case in rcar_du_atomic_commit_update_cmm() in patch 8/9,
> as from my testing it seems it is not possible to provide from
> userspace a non populated LUT table to just re-enable the CMM.
>
> So we're fine here.
Great, in that case then with the comment removed, and the other
trivials in this handled however you see fit,
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@xxxxxxxxxxxxxxxx>
>
>>
>>> +
>>> + for (i = 0; i < CM2_LUT_SIZE; ++i) {
>>> + const struct drm_color_lut *lut = &drm_lut[i];
>>> +
>>> + rcmm->lut.table[i] = drm_color_lut_extract(lut->red, 8) << 16
>>> + | drm_color_lut_extract(lut->green, 8) << 8
>>> + | drm_color_lut_extract(lut->blue, 8);
>>> + }
>>> +}
>>> +
>>> +/*
>>> + * rcar_cmm_lut_write() - Write to hardware the LUT table entries
>> from the
>>> + * local table.
>>> + * @rcmm: Pointer to the CMM device
>>> + */
>>> +static void rcar_cmm_lut_write(struct rcar_cmm *rcmm)
>>> +{
>>> + unsigned int i;
>>> +
>>> + for (i = 0; i < CM2_LUT_SIZE; ++i)
>>> + rcar_cmm_write(rcmm, CM2_LUT_TBL(i), rcmm->lut.table[i]);
>>> +}
>>> +
>>> +/*
>>> + * rcar_cmm_setup() - Configure the CMM unit.
>>> + * @pdev: The platform device associated with the CMM instance
>>> + * @config: The CRTC-provided configuration.
>>
>> I don't think CRTC-provided should be hyphenated like that.
>> Perhaps just:
>> "The colour management configuration".
>>
>> As I don't think who provides the configuration is relevant to the
>> actual call.
>>
>
> I have no idea. I've been bought into this by the comment
>
> "CRTC-provided" is a compound adjective, qualifying the noun
> "configuration". It thus needs a hyphen.
>
> I'm happy to remove it for a simpler version.
CRTC-provided just looks weird to me :-D however you wish to leave it is
up to you though :D
> +++ b/arch/arm64/boot/dts/renesas/r8a77965.dtsi
@@ -2320,6 +2320,33 @@
resets = <&cpg 611>;
};
+ cmm0: cmm@fea40000 {
+ compatible = "renesas,r8a77965-cmm",
+ "renesas,rcar-gen3-cmm";
+ reg = <0 0xfea40000 0 0x1000>;
+ power-domains = <&sysc R8A77965_PD_ALWAYS_ON>;
+ clocks = <&cpg CPG_MOD 711>;
+ resets = <&cpg 711>;
+ };
+
+ cmm1: cmm@fea50000 {
+ compatible = "renesas,r8a77965-cmm",
+ "renesas,rcar-gen3-cmm";
+ reg = <0 0xfea50000 0 0x1000>;
+ power-domains = <&sysc R8A77965_PD_ALWAYS_ON>;
+ clocks = <&cpg CPG_MOD 710>;
+ resets = <&cpg 710>;
+ };
+
+ cmm3: cmm@fea70000 {
+ compatible = "renesas,r8a77965-cmm",
+ "renesas,rcar-gen3-cmm";
+ reg = <0 0xfea70000 0 0x1000>;
+ power-domains = <&sysc R8A77965_PD_ALWAYS_ON>;
+ clocks = <&cpg CPG_MOD 708>;
+ resets = <&cpg 708>;
+ };
+
csi20: csi2@fea80000 {
compatible = "renesas,r8a77965-csi2";
reg = <0 0xfea80000 0 0x10000>;
@@ -2470,6 +2497,7 @@
status = "disabled";
vsps = <&vspd0 0>, <&vspd1 0>, <&vspd0 1>;
+ renesas,cmms = <&cmm0 &cmm1 &cmm3>;
> Thanks
> j
>
>>> + * Configure the CMM unit with the CRTC-provided configuration.
>>
>> s/CRTC-provided/given/
>>
>>> + * Currently enabling, disabling and programming of the 1-D LUT unit is
>>> + * supported.
>>> + */
>>> +int rcar_cmm_setup(struct platform_device *pdev,
>>> + const struct rcar_cmm_config *config)
>>> +{
>>> + struct rcar_cmm *rcmm = platform_get_drvdata(pdev);
>>> +
>>> + /*
>>> + * As rcar_cmm_setup() is called by atomic commit tail helper, it might
>>> + * be called when the CMM is disabled. As we can't program the hardware
>>> + * in that case, store the configuration internally and apply it when
>>> + * the CMM will be enabled by the CRTC through rcar_cmm_enable().
>>> + */
>>> + if (!rcmm->enabled) {
>>> + if (!config->lut.enable)
>>> + return 0;
>>> +
>>> + rcar_cmm_lut_extract(rcmm, config->lut.table);
>>> + rcmm->lut.enabled = true;
>>> +
>>> + return 0;
>>> + }
>>> +
>>> + /* Stop LUT operations if requested. */
>>> + if (!config->lut.enable) {
>>> + if (rcmm->lut.enabled) {
>>> + rcar_cmm_write(rcmm, CM2_LUT_CTRL, 0);
>>> + rcmm->lut.enabled = false;
>>> + }
>>> +
>>> + return 0;
>>> + }
>>> +
>>> + /*
>>> + * Enable LUT and program the new gamma table values.
>>> + *
>>> + * FIXME: In order to have stable operations it is required to first
>>> + * enable the 1D-LUT and then program its table entries. This seems to
>>> + * contradict what the chip manual reports, and will have to be
>>> + * reconsidered when implementing support for double buffering.
>>> + */
>>> + if (!rcmm->lut.enabled) {
>>> + rcar_cmm_write(rcmm, CM2_LUT_CTRL, CM2_LUT_CTRL_LUT_EN);
>>> + rcmm->lut.enabled = true;
>>> + }
>>> +
>>> + rcar_cmm_lut_extract(rcmm, config->lut.table);
>>> + rcar_cmm_lut_write(rcmm);
>>> +
>>> + return 0;
>>> +}
>>> +EXPORT_SYMBOL_GPL(rcar_cmm_setup);
>>> +
>>> +/*
>>> + * rcar_cmm_enable() - Enable the CMM unit.
>>> + * @pdev: The platform device associated with the CMM instance
>>> + *
>>> + * Enable the CMM unit by enabling the parent clock and enabling the CMM
>>> + * components, such as 1-D LUT, if requested.
>>> + */
>>> +int rcar_cmm_enable(struct platform_device *pdev)
>>> +{
>>> + struct rcar_cmm *rcmm = platform_get_drvdata(pdev);
>>> + int ret;
>>> +
>>> + ret = pm_runtime_get_sync(&pdev->dev);
>>> + if (ret < 0)
>>> + return ret;
>>> +
>>> + /* Apply the LUT table values saved at rcar_cmm_setup() time. */
>>> + if (rcmm->lut.enabled) {
>>> + rcar_cmm_write(rcmm, CM2_LUT_CTRL, CM2_LUT_CTRL_LUT_EN);
>>> + rcar_cmm_lut_write(rcmm);
>>> + }
>>> +
>>> + rcmm->enabled = true;
>>> +
>>> + return 0;
>>> +}
>>> +EXPORT_SYMBOL_GPL(rcar_cmm_enable);
>>> +
>>> +/*
>>> + * rcar_cmm_disable() - Disable the CMM unit.
>>> + * @pdev: The platform device associated with the CMM instance
>>> + *
>>> + * Disable the CMM unit by stopping the parent clock.
>>> + */
>>> +void rcar_cmm_disable(struct platform_device *pdev)
>>> +{
>>> + struct rcar_cmm *rcmm = platform_get_drvdata(pdev);
>>> +
>>> + rcar_cmm_write(rcmm, CM2_LUT_CTRL, 0);
>>> +
>>> + pm_runtime_put(&pdev->dev);
>>> +
>>> + rcmm->lut.enabled = false;
>>> + rcmm->enabled = false;
>>> +}
>>> +EXPORT_SYMBOL_GPL(rcar_cmm_disable);
>>> +
>>> +/*
>>> + * rcar_cmm_init() - Make sure the CMM has probed.
>>> + * @pdev: The platform device associated with the CMM instance
>>> + *
>>> + * Return: 0 if the CMM has probed, -EPROBE_DEFER otherwise
>>> + */
>>> +int rcar_cmm_init(struct platform_device *pdev)
>>> +{
>>> + struct rcar_cmm *rcmm = platform_get_drvdata(pdev);
>>> +
>>> + if (!rcmm)
>>> + return -EPROBE_DEFER;
>>> +
>>> + return 0;
>>> +}
>>> +EXPORT_SYMBOL_GPL(rcar_cmm_init);
>>> +
>>> +static int rcar_cmm_probe(struct platform_device *pdev)
>>> +{
>>> + struct rcar_cmm *rcmm;
>>> +
>>> + rcmm = devm_kzalloc(&pdev->dev, sizeof(*rcmm), GFP_KERNEL);
>>> + if (!rcmm)
>>> + return -ENOMEM;
>>> + platform_set_drvdata(pdev, rcmm);
>>> +
>>> + rcmm->base = devm_platform_ioremap_resource(pdev, 0);
>>> + if (IS_ERR(rcmm->base))
>>> + return PTR_ERR(rcmm->base);
>>> +
>>> + pm_runtime_enable(&pdev->dev);
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static int rcar_cmm_remove(struct platform_device *pdev)
>>> +{
>>> + pm_runtime_disable(&pdev->dev);
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static const struct of_device_id rcar_cmm_of_table[] = {
>>> + { .compatible = "renesas,rcar-gen3-cmm", },
>>> + { .compatible = "renesas,rcar-gen2-cmm", },
>>> + { },
>>> +};
>>> +MODULE_DEVICE_TABLE(of, rcar_cmm_of_table);
>>> +
>>> +static struct platform_driver rcar_cmm_platform_driver = {
>>> + .probe = rcar_cmm_probe,
>>> + .remove = rcar_cmm_remove,
>>> + .driver = {
>>> + .name = "rcar-cmm",
>>> + .of_match_table = rcar_cmm_of_table,
>>> + },
>>> +};
>>> +
>>> +module_platform_driver(rcar_cmm_platform_driver);
>>> +
>>> +MODULE_AUTHOR("Jacopo Mondi <jacopo+renesas@xxxxxxxxxx>");
>>> +MODULE_DESCRIPTION("Renesas R-Car CMM Driver");
>>> +MODULE_LICENSE("GPL v2");
>>> diff --git a/drivers/gpu/drm/rcar-du/rcar_cmm.h
>> b/drivers/gpu/drm/rcar-du/rcar_cmm.h
>>> new file mode 100644
>>> index 000000000000..15a2c874b6a6
>>> --- /dev/null
>>> +++ b/drivers/gpu/drm/rcar-du/rcar_cmm.h
>>> @@ -0,0 +1,61 @@
>>> +/* SPDX-License-Identifier: GPL-2.0+ */
>>> +/*
>>> + * rcar_cmm.h -- R-Car Display Unit Color Management Module
>>> + *
>>> + * Copyright (C) 2019 Jacopo Mondi <jacopo+renesas@xxxxxxxxxx>
>>> + */
>>> +
>>> +#ifndef __RCAR_CMM_H__
>>> +#define __RCAR_CMM_H__
>>> +
>>> +#define CM2_LUT_SIZE 256
>>> +
>>> +struct drm_color_lut;
>>> +struct platform_device;
>>> +
>>> +/**
>>> + * struct rcar_cmm_config - CMM configuration
>>> + *
>>> + * @lut: 1D-LUT configuration
>>> + * @lut.enable: 1D-LUT enable flag
>>> + * @lut.table: 1D-LUT table entries. Might be set to NULL when the
>> CMM has to
>>> + * be re-enabled but not re=programmed.
>>
>> So lut.table can be NULL ... See comment at rcar_cmm_lut_extract()
Ok - so this comment will be removed.
>>
>>> + */
>>> +struct rcar_cmm_config {
>>> + struct {
>>> + bool enable;
>>> + struct drm_color_lut *table;
>>> + } lut;
>>> +};
>>> +
>>> +#if IS_ENABLED(CONFIG_DRM_RCAR_CMM)
>>> +int rcar_cmm_init(struct platform_device *pdev);
>>> +
>>> +int rcar_cmm_enable(struct platform_device *pdev);
>>> +void rcar_cmm_disable(struct platform_device *pdev);
>>> +
>>> +int rcar_cmm_setup(struct platform_device *pdev,
>>> + const struct rcar_cmm_config *config);
>>> +#else
>>> +static inline int rcar_cmm_init(struct platform_device *pdev)
>>> +{
>>> + return 0;
>>> +}
>>> +
>>> +static inline int rcar_cmm_enable(struct platform_device *pdev)
>>> +{
>>> + return 0;
>>> +}
>>> +
>>> +static inline void rcar_cmm_disable(struct platform_device *pdev)
>>> +{
>>> +}
>>> +
>>> +static int rcar_cmm_setup(struct platform_device *pdev,
>>> + const struct rcar_cmm_config *config)
>>> +{
>>> + return 0;
>>> +}
>>> +#endif /* IS_ENABLED(CONFIG_DRM_RCAR_CMM) */
>>> +
>>> +#endif /* __RCAR_CMM_H__ */
>>>
>>
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel
