From: Andy Yan <andy.yan@rock-chips.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
heiko@sntech.de, airlied@linux.ie,
dri-devel@lists.freedesktop.org, ykk@rock-chips.com,
devel@driverdev.osuosl.org, Pawel Moll <pawel.moll@arm.com>,
linux-rockchip@lists.infradead.org,
Grant Likely <grant.likely@linaro.org>,
Dave Airlie <airlied@redhat.com>,
jay.xu@rock-chips.com, devicetree@vger.kernel.org,
Zubair.Kakakhel@imgtec.com, Arnd Bergmann <arnd@arndb.de>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Inki Dae <inki.dae@samsung.com>, Rob Herring <robh+dt@kernel.org>,
Sean Paul <seanpaul@chromium.org>,
rmk+kernel@arm.linux.org.uk, mark.yao@rock-chips.com,
fabio.estevam@freescale.com, Josh Boyer <jwboyer@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, djkurtz@google.com,
Kumar Gala <galak@codeaurora.org>,
Shawn Guo <shawn.guo@linaro.org>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH v13 07/12] drm: bridge/dw_hdmi: add support for multi-byte register width access
Date: Fri, 28 Nov 2014 17:43:21 +0800 [thread overview]
Message-ID: <547843B9.6000806@rock-chips.com> (raw)
In-Reply-To: <1417019657.3177.10.camel@pengutronix.de>
Hi Zabel:
On 2014年11月27日 00:34, Philipp Zabel wrote:
> Am Mittwoch, den 26.11.2014, 21:32 +0800 schrieb Andy Yan:
>> On rockchip rk3288, only word(32-bit) accesses are
>> permitted for hdmi registers. Byte width accesses (writeb,
>> readb) generate an imprecise external abort.
>>
>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>>
>> ---
>>
>> Changes in v13: None
>> Changes in v12: None
>> Changes in v11: None
>> Changes in v10: None
>> Changes in v9: None
>> Changes in v8: None
>> Changes in v7: None
>> Changes in v6:
>> - refactor register access without reg_shift
>>
>> Changes in v5:
>> - refactor reg-io-width
>>
>> Changes in v4: None
>> Changes in v3:
>> - split multi-register access to one indepent patch
>>
>> drivers/gpu/drm/bridge/dw_hdmi.c | 57 +++++++++++++++++++++++++++++++++++-----
>> 1 file changed, 51 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/dw_hdmi.c b/drivers/gpu/drm/bridge/dw_hdmi.c
>> index a53bf63..5e88c8d 100644
>> --- a/drivers/gpu/drm/bridge/dw_hdmi.c
>> +++ b/drivers/gpu/drm/bridge/dw_hdmi.c
>> @@ -100,6 +100,11 @@ struct hdmi_data_info {
>> struct hdmi_vmode video_mode;
>> };
>>
>> +union dw_reg_ptr {
>> + u32 __iomem *p32;
>> + u8 __iomem *p8;
>> +};
> I see no need to introduce this. Just explicitly multiply the offset in
> dw_hdmi_writel.
>
Is there any disadvantage to do like this?
The compiler can help us do the explicitly multiply by this way.
>> struct dw_hdmi {
>> struct drm_connector connector;
>> struct drm_encoder *encoder;
>> @@ -121,20 +126,43 @@ struct dw_hdmi {
>>
>> struct regmap *regmap;
>> struct i2c_adapter *ddc;
>> - void __iomem *regs;
>> + union dw_reg_ptr regs;
> Keep this as void __iomem *
>
>> unsigned int sample_rate;
>> int ratio;
>> +
>> + void (*write)(struct dw_hdmi *hdmi, u8 val, int offset);
>> + u8 (*read)(struct dw_hdmi *hdmi, int offset);
>> };
>>
>> +static void dw_hdmi_writel(struct dw_hdmi *hdmi, u8 val, int offset)
>> +{
>> + writel(val, hdmi->regs.p32 + offset);
> hdmi->regs + 4 * offset
>
>> +}
>> +
>> +static u8 dw_hdmi_readl(struct dw_hdmi *hdmi, int offset)
>> +{
>> + return readl(hdmi->regs.p32 + offset);
> same here
>
>> +}
>> +
>> +static void dw_hdmi_writeb(struct dw_hdmi *hdmi, u8 val, int offset)
>> +{
>> + writeb(val, hdmi->regs.p8 + offset);
>> +}
>> +
>> +static u8 dw_hdmi_readb(struct dw_hdmi *hdmi, int offset)
>> +{
>> + return readb(hdmi->regs.p8 + offset);
>> +}
>> +
>> static inline void hdmi_writeb(struct dw_hdmi *hdmi, u8 val, int offset)
>> {
>> - writeb(val, hdmi->regs + offset);
>> + hdmi->write(hdmi, val, offset);
>> }
>>
>> static inline u8 hdmi_readb(struct dw_hdmi *hdmi, int offset)
>> {
>> - return readb(hdmi->regs + offset);
>> + return hdmi->read(hdmi, offset);
>> }
>>
>> static void hdmi_modb(struct dw_hdmi *hdmi, u8 data, u8 mask, unsigned reg)
>> @@ -1508,6 +1536,7 @@ int dw_hdmi_bind(struct device *dev, struct device *master,
>> struct dw_hdmi *hdmi;
>> struct resource *iores;
>> int ret, irq;
>> + u32 val = 1;
>>
>> hdmi = devm_kzalloc(&pdev->dev, sizeof(*hdmi), GFP_KERNEL);
>> if (!hdmi)
>> @@ -1520,6 +1549,22 @@ int dw_hdmi_bind(struct device *dev, struct device *master,
>> hdmi->ratio = 100;
>> hdmi->encoder = encoder;
>>
>> + of_property_read_u32(np, "reg-io-width", &val);
>> +
>> + switch (val) {
>> + case 4:
>> + hdmi->write = dw_hdmi_writel;
>> + hdmi->read = dw_hdmi_readl;
>> + break;
>> + case 1:
>> + hdmi->write = dw_hdmi_writeb;
>> + hdmi->read = dw_hdmi_readb;
>> + break;
>> + default:
>> + dev_err(dev, "reg-io-width must be 1 or 4\n");
>> + return -EINVAL;
>> + }
>> +
>> ddc_node = of_parse_phandle(np, "ddc-i2c-bus", 0);
>> if (ddc_node) {
>> hdmi->ddc = of_find_i2c_adapter_by_node(ddc_node);
>> @@ -1544,9 +1589,9 @@ int dw_hdmi_bind(struct device *dev, struct device *master,
>> return ret;
>>
>> iores = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> - hdmi->regs = devm_ioremap_resource(dev, iores);
>> - if (IS_ERR(hdmi->regs))
>> - return PTR_ERR(hdmi->regs);
>> + hdmi->regs.p32 = devm_ioremap_resource(dev, iores);
>> + if (IS_ERR(hdmi->regs.p32))
>> + return PTR_ERR(hdmi->regs.p32);
>>
>> /* Product and revision IDs */
>> dev_info(dev,
> regards
> Philipp
>
>
>
>
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andy Yan <andy.yan@rock-chips.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: airlied@linux.ie, heiko@sntech.de, fabio.estevam@freescale.com,
rmk+kernel@arm.linux.org.uk,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawn.guo@linaro.org>, Josh Boyer <jwboyer@redhat.com>,
Sean Paul <seanpaul@chromium.org>,
Inki Dae <inki.dae@samsung.com>, Dave Airlie <airlied@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
Lucas Stach <l.stach@pengutronix.de>,
Zubair.Kakakhel@imgtec.com, djkurtz@google.com,
ykk@rock-chips.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, devel@driverdev.osuosl.org,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
jay.xu@rock-chips.com, Pawel Moll <pawel.moll@arm.com>,
mark.yao@rock-chips.com, Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v13 07/12] drm: bridge/dw_hdmi: add support for multi-byte register width access
Date: Fri, 28 Nov 2014 17:43:21 +0800 [thread overview]
Message-ID: <547843B9.6000806@rock-chips.com> (raw)
In-Reply-To: <1417019657.3177.10.camel@pengutronix.de>
Hi Zabel:
On 2014年11月27日 00:34, Philipp Zabel wrote:
> Am Mittwoch, den 26.11.2014, 21:32 +0800 schrieb Andy Yan:
>> On rockchip rk3288, only word(32-bit) accesses are
>> permitted for hdmi registers. Byte width accesses (writeb,
>> readb) generate an imprecise external abort.
>>
>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>>
>> ---
>>
>> Changes in v13: None
>> Changes in v12: None
>> Changes in v11: None
>> Changes in v10: None
>> Changes in v9: None
>> Changes in v8: None
>> Changes in v7: None
>> Changes in v6:
>> - refactor register access without reg_shift
>>
>> Changes in v5:
>> - refactor reg-io-width
>>
>> Changes in v4: None
>> Changes in v3:
>> - split multi-register access to one indepent patch
>>
>> drivers/gpu/drm/bridge/dw_hdmi.c | 57 +++++++++++++++++++++++++++++++++++-----
>> 1 file changed, 51 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/dw_hdmi.c b/drivers/gpu/drm/bridge/dw_hdmi.c
>> index a53bf63..5e88c8d 100644
>> --- a/drivers/gpu/drm/bridge/dw_hdmi.c
>> +++ b/drivers/gpu/drm/bridge/dw_hdmi.c
>> @@ -100,6 +100,11 @@ struct hdmi_data_info {
>> struct hdmi_vmode video_mode;
>> };
>>
>> +union dw_reg_ptr {
>> + u32 __iomem *p32;
>> + u8 __iomem *p8;
>> +};
> I see no need to introduce this. Just explicitly multiply the offset in
> dw_hdmi_writel.
>
Is there any disadvantage to do like this?
The compiler can help us do the explicitly multiply by this way.
>> struct dw_hdmi {
>> struct drm_connector connector;
>> struct drm_encoder *encoder;
>> @@ -121,20 +126,43 @@ struct dw_hdmi {
>>
>> struct regmap *regmap;
>> struct i2c_adapter *ddc;
>> - void __iomem *regs;
>> + union dw_reg_ptr regs;
> Keep this as void __iomem *
>
>> unsigned int sample_rate;
>> int ratio;
>> +
>> + void (*write)(struct dw_hdmi *hdmi, u8 val, int offset);
>> + u8 (*read)(struct dw_hdmi *hdmi, int offset);
>> };
>>
>> +static void dw_hdmi_writel(struct dw_hdmi *hdmi, u8 val, int offset)
>> +{
>> + writel(val, hdmi->regs.p32 + offset);
> hdmi->regs + 4 * offset
>
>> +}
>> +
>> +static u8 dw_hdmi_readl(struct dw_hdmi *hdmi, int offset)
>> +{
>> + return readl(hdmi->regs.p32 + offset);
> same here
>
>> +}
>> +
>> +static void dw_hdmi_writeb(struct dw_hdmi *hdmi, u8 val, int offset)
>> +{
>> + writeb(val, hdmi->regs.p8 + offset);
>> +}
>> +
>> +static u8 dw_hdmi_readb(struct dw_hdmi *hdmi, int offset)
>> +{
>> + return readb(hdmi->regs.p8 + offset);
>> +}
>> +
>> static inline void hdmi_writeb(struct dw_hdmi *hdmi, u8 val, int offset)
>> {
>> - writeb(val, hdmi->regs + offset);
>> + hdmi->write(hdmi, val, offset);
>> }
>>
>> static inline u8 hdmi_readb(struct dw_hdmi *hdmi, int offset)
>> {
>> - return readb(hdmi->regs + offset);
>> + return hdmi->read(hdmi, offset);
>> }
>>
>> static void hdmi_modb(struct dw_hdmi *hdmi, u8 data, u8 mask, unsigned reg)
>> @@ -1508,6 +1536,7 @@ int dw_hdmi_bind(struct device *dev, struct device *master,
>> struct dw_hdmi *hdmi;
>> struct resource *iores;
>> int ret, irq;
>> + u32 val = 1;
>>
>> hdmi = devm_kzalloc(&pdev->dev, sizeof(*hdmi), GFP_KERNEL);
>> if (!hdmi)
>> @@ -1520,6 +1549,22 @@ int dw_hdmi_bind(struct device *dev, struct device *master,
>> hdmi->ratio = 100;
>> hdmi->encoder = encoder;
>>
>> + of_property_read_u32(np, "reg-io-width", &val);
>> +
>> + switch (val) {
>> + case 4:
>> + hdmi->write = dw_hdmi_writel;
>> + hdmi->read = dw_hdmi_readl;
>> + break;
>> + case 1:
>> + hdmi->write = dw_hdmi_writeb;
>> + hdmi->read = dw_hdmi_readb;
>> + break;
>> + default:
>> + dev_err(dev, "reg-io-width must be 1 or 4\n");
>> + return -EINVAL;
>> + }
>> +
>> ddc_node = of_parse_phandle(np, "ddc-i2c-bus", 0);
>> if (ddc_node) {
>> hdmi->ddc = of_find_i2c_adapter_by_node(ddc_node);
>> @@ -1544,9 +1589,9 @@ int dw_hdmi_bind(struct device *dev, struct device *master,
>> return ret;
>>
>> iores = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> - hdmi->regs = devm_ioremap_resource(dev, iores);
>> - if (IS_ERR(hdmi->regs))
>> - return PTR_ERR(hdmi->regs);
>> + hdmi->regs.p32 = devm_ioremap_resource(dev, iores);
>> + if (IS_ERR(hdmi->regs.p32))
>> + return PTR_ERR(hdmi->regs.p32);
>>
>> /* Product and revision IDs */
>> dev_info(dev,
> regards
> Philipp
>
>
>
>
next prev parent reply other threads:[~2014-11-28 9:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 13:22 [PATCH v13 0/12] dw-hdmi: convert imx hdmi to bridge/dw_hdmi Andy Yan
2014-11-26 13:22 ` Andy Yan
[not found] ` <1417008157-31861-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-11-26 13:26 ` [PATCH v13 01/12] drm: imx: imx-hdmi: make checkpatch happy Andy Yan
2014-11-26 13:26 ` Andy Yan
2014-11-26 13:26 ` [PATCH v13 02/12] drm: imx: imx-hdmi: return defer if can't get ddc i2c adapter Andy Yan
2014-11-26 13:26 ` Andy Yan
2014-11-26 13:30 ` [PATCH v13 05/12] drm: imx: imx-hdmi: move imx-hdmi to bridge/dw_hdmi Andy Yan
2014-11-26 13:30 ` Andy Yan
2014-11-26 13:31 ` [PATCH v13 06/12] dt-bindings: add document for dw_hdmi Andy Yan
2014-11-26 13:31 ` Andy Yan
2014-11-26 13:37 ` [PATCH v13 12/12] drm: bridge/dw_hdmi: add rockchip rk3288 support Andy Yan
2014-11-26 13:37 ` Andy Yan
2014-11-26 13:27 ` [PATCH v13 03/12] drm: imx: imx-hdmi: convert imx-hdmi to drm_bridge mode Andy Yan
2014-11-26 13:27 ` Andy Yan
2014-11-26 13:30 ` [PATCH v13 04/12] drm: imx: imx-hdmi: split phy configuration to platform driver Andy Yan
2014-11-26 13:30 ` Andy Yan
2014-11-26 13:32 ` [PATCH v13 07/12] drm: bridge/dw_hdmi: add support for multi-byte register width access Andy Yan
2014-11-26 13:32 ` Andy Yan
2014-11-26 16:34 ` Philipp Zabel
2014-11-26 16:34 ` Philipp Zabel
2014-11-28 9:43 ` Andy Yan [this message]
2014-11-28 9:43 ` Andy Yan
2014-12-01 12:04 ` Philipp Zabel
2014-12-01 12:04 ` Philipp Zabel
2014-12-01 12:46 ` Andy Yan
2014-12-01 12:46 ` Andy Yan
2014-11-26 13:33 ` [PATCH v13 08/12] drm: bridge/dw_hdmi: add mode_valid support Andy Yan
2014-11-26 13:33 ` Andy Yan
2014-11-26 16:23 ` Philipp Zabel
2014-11-26 16:23 ` Philipp Zabel
2014-11-28 9:47 ` Andy Yan
2014-11-28 9:47 ` Andy Yan
2014-11-26 13:34 ` [PATCH v13 09/12] drm: bridge/dw_hdmi: clear i2cmphy_stat0 reg in hdmi_phy_wait_i2c_done Andy Yan
2014-11-26 13:34 ` Andy Yan
2014-11-26 13:35 ` [PATCH v13 10/12] drm: bridge/dw_hdmi: add function dw_hdmi_phy_enable_spare Andy Yan
2014-11-26 13:35 ` Andy Yan
2014-11-26 13:36 ` [PATCH v13 11/12] dt-bindings: Add documentation for rockchip dw hdmi Andy Yan
2014-11-26 13:36 ` Andy Yan
2014-11-26 16:20 ` [PATCH v13 0/12] dw-hdmi: convert imx hdmi to bridge/dw_hdmi Philipp Zabel
2014-11-26 16:20 ` Philipp Zabel
2014-11-28 9:57 ` Andy Yan
2014-11-28 9:57 ` Andy Yan
2014-11-28 16:14 ` Philipp Zabel
2014-11-28 16:14 ` Philipp Zabel
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=547843B9.6000806@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=inki.dae@samsung.com \
--cc=jay.xu@rock-chips.com \
--cc=jwboyer@redhat.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mark.yao@rock-chips.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=shawn.guo@linaro.org \
--cc=ykk@rock-chips.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.