From: Arnd Bergmann <arnd@arndb.de>
To: David Brown <davidb@codeaurora.org>
Cc: Russell King <linux@arm.linux.org.uk>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH v3 4/4] ARM: msm: Describe MSM 8660 SURF FPGA registers in DT
Date: Thu, 25 Aug 2011 13:27:12 +0200 [thread overview]
Message-ID: <201108251327.13146.arnd@arndb.de> (raw)
In-Reply-To: <1313688345-17699-5-git-send-email-davidb@codeaurora.org>
On Thursday 18 August 2011, David Brown wrote:
> +static void __init msm8660_surf_fpga_init(void __iomem *fpga_mem)
> +{
> + /* Advanced mode */
> + writew(0xFFFF, fpga_mem + 0x15C);
> + /* FPGA_UART_SEL */
> + writew(0, fpga_mem + 0x172);
> + /* FPGA_GPIO_CONFIG_117 */
> + writew(1, fpga_mem + 0xEA);
> + /* FPGA_GPIO_CONFIG_118 */
> + writew(1, fpga_mem + 0xEC);
> + dmb();
> +}
Does the dmb() do the right thing here? It seems strange to combine a strictly
ordered I/O instruction with another ordering instruction, and I think it would
be better to use writew_relaxed for the first one, followed by a 'wmb()'.
> +#ifdef CONFIG_OF
> +static void __init msm8660_surf_fpga_init_dt(void)
> +{
> + struct device_node *node;
> + void __iomem *fpga_mem;
> +
> + node = of_find_compatible_node(NULL, NULL, "qcom,msm8660-surf-fpga");
> + if (!node)
> + return;
> +
> + fpga_mem = of_iomap(node, 0);
> + of_node_put(node);
> + if (!fpga_mem) {
> + printk(KERN_ERR "%s: Can't map fpga registers\n", __func__);
> + return;
> + }
> +
> + msm8660_surf_fpga_init(fpga_mem);
> + iounmap(fpga_mem);
> +}
> +#endif
Is the serial port connected through the FPGA or just configured by it?
In the former case, I think it would be better to make this a proper device driver that
binds to the qcom,msm8660-surf-fpga device, configures it and then creates the
platform_devices for the child nodes (the serial port, possibly others) by calling
of_platform_bus_probe.
Arnd
next prev parent reply other threads:[~2011-08-25 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 17:25 [PATCH v3 0/4] Initial DT support for MSM8660 David Brown
2011-08-18 17:25 ` [PATCH v3 1/4] msm_serial: Use relative resources for iomem David Brown
2011-08-18 17:25 ` [PATCH v3 2/4] msm_serial: Add devicetree support David Brown
2011-08-25 11:28 ` Arnd Bergmann
2011-08-18 17:25 ` [PATCH v3 3/4] ARM: msm: Add devicetree support for msm8660-surf David Brown
2011-08-25 11:28 ` Arnd Bergmann
2011-08-18 17:25 ` [PATCH v3 4/4] ARM: msm: Describe MSM 8660 SURF FPGA registers in DT David Brown
2011-08-25 11:27 ` Arnd Bergmann [this message]
2011-08-25 14:57 ` David Brown
2011-08-25 15:26 ` Arnd Bergmann
2011-08-26 5:03 ` David Brown
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=201108251327.13146.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sboyd@codeaurora.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