Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: yang.zheng@rock-chips.com (Zheng Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [PATCH v5 5/6] drm/rockchip: dw_hdmi: store rockchip_hdmi reference in phy_data object
Date: Fri, 28 Sep 2018 15:52:46 +0800	[thread overview]
Message-ID: <25eb567a-50b1-cac6-e09c-278af6c95250@rock-chips.com> (raw)
In-Reply-To: <3a8b88a3-ec0c-cf39-0a97-a941068318c2@rock-chips.com>

Hi, Heiko:

Reviewed-by: zhengyang <zhengyang@rock-chips.com>

>
> When using special phy handling operations we'll often need access to
> the rockchip_hdmi struct.
>
> As the chip-data that occupies the phy_data pointer initially gets
> assigned to the rockchip_hdmi struct, we can now re-use this phy_data
> pointer to hold the reference to the rockchip_hdmi struct and use this
> reference later on.
>
> Inspiration for this comes from meson and sunxi dw-hdmi, which are using
> the same method.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> Tested-by: Robin Murphy <robin.murphy@arm.com>
>
> changes in v3:
> - reword commit message
> ---
> ?drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 9 +++++++--
> ?1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c 
> b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
> index 57e76dfd5f6d..19f002fa0a09 100644
> --- a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
> +++ b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
> @@ -335,7 +335,7 @@ static int dw_hdmi_rockchip_bind(struct device 
> *dev, struct device *master,
> ????????????????? void *data)
> ?{
> ???? struct platform_device *pdev = to_platform_device(dev);
> -??? const struct dw_hdmi_plat_data *plat_data;
> +??? struct dw_hdmi_plat_data *plat_data;
> ???? const struct of_device_id *match;
> ???? struct drm_device *drm = data;
> ???? struct drm_encoder *encoder;
> @@ -350,9 +350,14 @@ static int dw_hdmi_rockchip_bind(struct device 
> *dev, struct device *master,
> ???????? return -ENOMEM;
> ????? match = of_match_node(dw_hdmi_rockchip_dt_ids, pdev->dev.of_node);
> -??? plat_data = match->data;
> +??? plat_data = devm_kmemdup(&pdev->dev, match->data,
> +???????????????????????? sizeof(*plat_data), GFP_KERNEL);
> +??? if (!plat_data)
> +??????? return -ENOMEM;
> +
> ???? hdmi->dev = &pdev->dev;
> ???? hdmi->chip_data = plat_data->phy_data;
> +??? plat_data->phy_data = hdmi;
> ???? encoder = &hdmi->encoder;
> ????? encoder->possible_crtcs = drm_of_find_possible_crtcs(drm, 
> dev->of_node);

  parent reply	other threads:[~2018-09-28  7:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 12:47 [PATCH v5 0/6] drm/rockchip: hdmi support for rk3328 Heiko Stuebner
2018-09-12 12:47 ` [PATCH v5 1/6] drm/bridge: dw-hdmi: allow forcing vendor phy-type Heiko Stuebner
     [not found]   ` <1851d56f-b628-2d10-0da7-72c1075b2b9a@rock-chips.com>
2018-09-28  7:51     ` Zheng Yang
2018-09-28  8:09   ` Andrzej Hajda
2018-09-12 12:47 ` [PATCH v5 2/6] drm/rockchip: dw_hdmi: Allow outputs that don't need output switching Heiko Stuebner
     [not found]   ` <6d4ee8b5-a1fa-23b7-88db-32b2c02833cb@rock-chips.com>
2018-09-28  7:52     ` Fwd: " Zheng Yang
2018-09-12 12:47 ` [PATCH v5 3/6] dt-bindings: allow optional phys in Rockchip dw_hdmi binding Heiko Stuebner
2018-09-12 12:47 ` [PATCH v5 4/6] drm/rockchip: dw_hdmi: allow including external phys Heiko Stuebner
     [not found]   ` <4187b1f6-9682-6c3e-741e-0374e3e9165b@rock-chips.com>
2018-09-28  7:52     ` Fwd: " Zheng Yang
2018-09-12 12:47 ` [PATCH v5 5/6] drm/rockchip: dw_hdmi: store rockchip_hdmi reference in phy_data object Heiko Stuebner
     [not found]   ` <3a8b88a3-ec0c-cf39-0a97-a941068318c2@rock-chips.com>
2018-09-28  7:52     ` Zheng Yang [this message]
2018-09-12 12:47 ` [PATCH v5 6/6] drm/rockchip: dw_hdmi: add dw-hdmi support for the rk3328 Heiko Stuebner
     [not found]   ` <8ec9f7d2-069a-81e4-acf5-050d6b2094f7@rock-chips.com>
2018-09-28  7:52     ` Fwd: " Zheng Yang
2018-09-28 11:14 ` [PATCH v5 0/6] drm/rockchip: hdmi support for rk3328 Heiko Stuebner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25eb567a-50b1-cac6-e09c-278af6c95250@rock-chips.com \
    --to=yang.zheng@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox