From: Roger Quadros <rogerq@kernel.org>
To: krzysztof.kozlowski@canonical.com, tony@atomide.com
Cc: kishon@ti.com, nm@ti.com, vigneshr@ti.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] memory: omap-gpmc: memory: omap-gpmc: Add support for GPMC on AM64 SoC
Date: Tue, 23 Nov 2021 12:28:20 +0200 [thread overview]
Message-ID: <a9043d7e-20ca-5a53-c54f-825d94c79689@kernel.org> (raw)
In-Reply-To: <20211123102607.13002-6-rogerq@kernel.org>
Please ignore this one as well.
On 23/11/2021 12:26, Roger Quadros wrote:
> The TI's AM64 SoC has the GPMC module. Add compatible for it.
>
> Traditionally GPMC external addresses have always been mapped to first
> 1GB physical address. However newer platforms, can have it mapped
> at different locations. Support this address provision via device tree.
>
> Signed-off-by: Roger Quadros <rogerq@kernel.org>
> ---
> drivers/memory/omap-gpmc.c | 40 ++++++++++++++++++++++++++++----------
> 1 file changed, 30 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
> index be0858bff4d3..624153048182 100644
> --- a/drivers/memory/omap-gpmc.c
> +++ b/drivers/memory/omap-gpmc.c
> @@ -237,6 +237,7 @@ struct gpmc_device {
> struct omap3_gpmc_regs context;
> int nirqs;
> unsigned int is_suspended:1;
> + struct resource *data;
> };
>
> static struct irq_domain *gpmc_irq_domain;
> @@ -1456,12 +1457,18 @@ static void gpmc_mem_exit(void)
> }
> }
>
> -static void gpmc_mem_init(void)
> +static void gpmc_mem_init(struct gpmc_device *gpmc)
> {
> int cs;
>
> - gpmc_mem_root.start = GPMC_MEM_START;
> - gpmc_mem_root.end = GPMC_MEM_END;
> + if (!gpmc->data) {
> + /* All legacy devices have same data IO window */
> + gpmc_mem_root.start = GPMC_MEM_START;
> + gpmc_mem_root.end = GPMC_MEM_END;
> + } else {
> + gpmc_mem_root.start = gpmc->data->start;
> + gpmc_mem_root.end = gpmc->data->end;
> + }
>
> /* Reserve all regions that has been set up by bootloader */
> for (cs = 0; cs < gpmc_cs_num; cs++) {
> @@ -1888,6 +1895,7 @@ static const struct of_device_id gpmc_dt_ids[] = {
> { .compatible = "ti,omap3430-gpmc" }, /* omap3430 & omap3630 */
> { .compatible = "ti,omap4430-gpmc" }, /* omap4430 & omap4460 & omap543x */
> { .compatible = "ti,am3352-gpmc" }, /* am335x devices */
> + { .compatible = "ti,am64-gpmc" },
> { }
> };
>
> @@ -2502,13 +2510,25 @@ static int gpmc_probe(struct platform_device *pdev)
> gpmc->dev = &pdev->dev;
> platform_set_drvdata(pdev, gpmc);
>
> - res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> - if (!res)
> - return -ENOENT;
> + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "cfg");
> + if (!res) {
> + /* legacy DT */
> + gpmc_base = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(gpmc_base))
> + return PTR_ERR(gpmc_base);
> + } else {
> + gpmc_base = devm_ioremap_resource(&pdev->dev, res);
> + if (IS_ERR(gpmc_base))
> + return PTR_ERR(gpmc_base);
> +
> + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "data");
> + if (!res) {
> + dev_err(&pdev->dev, "couldn't get data reg resource\n");
> + return -ENOENT;
> + }
>
> - gpmc_base = devm_ioremap_resource(&pdev->dev, res);
> - if (IS_ERR(gpmc_base))
> - return PTR_ERR(gpmc_base);
> + gpmc->data = res;
> + }
>
> res = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
> if (!res) {
> @@ -2562,7 +2582,7 @@ static int gpmc_probe(struct platform_device *pdev)
> dev_info(gpmc->dev, "GPMC revision %d.%d\n", GPMC_REVISION_MAJOR(l),
> GPMC_REVISION_MINOR(l));
>
> - gpmc_mem_init();
> + gpmc_mem_init(gpmc);
> rc = gpmc_gpio_init(gpmc);
> if (rc)
> goto gpio_init_failed;
>
next prev parent reply other threads:[~2021-11-23 10:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 10:26 [PATCH 0/4] memory: omap-gpmc: Add AM64 SoC support Roger Quadros
2021-11-23 10:26 ` [PATCH 1/4] dt-bindings: memory-controllers: ti,gpmc: Add compatible for AM64 Roger Quadros
2021-11-23 19:47 ` Krzysztof Kozlowski
2021-11-25 12:18 ` Roger Quadros
2021-11-30 22:02 ` Rob Herring
2021-12-01 11:14 ` Roger Quadros
2021-11-23 10:26 ` [PATCH 2/4] memory: gpmc: Fix menuconfig visibility Roger Quadros
2021-11-23 10:27 ` Roger Quadros
2021-11-23 10:26 ` [PATCH 2/4] memory: omap-gpmc: " Roger Quadros
2021-11-23 19:43 ` Krzysztof Kozlowski
2021-11-25 12:09 ` Roger Quadros
2021-11-23 10:26 ` [PATCH 3/4] memory: omap-gpmc: Add support for GPMC on AM64 SoC Roger Quadros
2021-11-23 10:26 ` [PATCH 3/4] memory: omap-gpmc: " Roger Quadros
2021-11-23 10:28 ` Roger Quadros [this message]
2021-11-23 10:26 ` [PATCH 4/4] memory: omap-gpmc: check for nand node name instead of just compatibility Roger Quadros
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=a9043d7e-20ca-5a53-c54f-825d94c79689@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox