From: Romain Naour <romain.naour@smile.fr> To: Grygorii Strashko <grygorii.strashko@ti.com>, Roger Quadros <rogerq@kernel.org>, krzysztof.kozlowski@canonical.com, miquel.raynal@bootlin.com, tony@atomide.com Cc: robh@kernel.org, kishon@ti.com, nm@ti.com, vigneshr@ti.com, linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org Subject: Re: [PATCH v4 0/4] memory: omap-gpmc: Add AM64 SoC support Date: Fri, 13 May 2022 10:49:35 +0200 [thread overview] Message-ID: <13fa1d59-7750-a327-c100-a53823509017@smile.fr> (raw) In-Reply-To: <5d8ba4e2-a281-5d0f-d65f-bb0121165b73@ti.com> Hi, Le 15/04/2022 à 15:06, Grygorii Strashko a écrit : > > > On 15/04/2022 11:59, Romain Naour wrote: >> Hello, >> >> Le 21/12/2021 à 14:17, Roger Quadros a écrit : >>> Hi, >>> >>> TI's AM64 SoC contains one GPMC module. Add driver support for it. >> >> What's the status of the GPMC interface on K3 architecture, especially for AM65, >> AM62 and other Jacinto 7 CPU devices ? >> >> TI currently don't recommend to use it for now even if there are still some GPMC >> use case with FPGA devices: >> >> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/994191/am6442-am64x-gpmc-support >> >> >> This patch series add omap-gpmc support for AM64 Soc but as of kernel 5.18-rc2, >> there is no devicetree using ti,am64-gpmc. >> >> This patch seems missing (at least): >> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-5.10.y&id=55c102a75d399896c7396229cd687bf97afb5cf6 >> > > It's not how LKML development process works - driver changes has to be sent first > and then DT changes as they accepted by different maintainers and through > different trees. Ok, I understand. DT changes are still under review [1] and are not yet merged in 5.18-rc6. Sorry for the noise. [1] https://lkml.org/lkml/2022/2/4/320 Best regards, Romain > >> >> Thanks! >> >> Best regards, >> Romain >> >>> >>> cheers, >>> -roger >>> >>> Changelog: >>> v4 >>> - move compatible match table to header file so it can be used by >>> GPMC driver even when NAND driver is not enabled or as a module. >>> GPMC driver is always enabled as built-in. >>> - Select OMAP_GPMC driver from MTD_NAND_OMAP2 driver config as >>> OMAP_GPMC is not essential for ARCH_K3 boot. >>> >>> v3 >>> - use compatible match table for checking for NAND controller node in >>> GPMC driver. >>> >>> v2 >>> - update DT binding doc to make reg-names and power-domains property >>> required only for specific SoC. >>> >>> Roger Quadros (4): >>> dt-bindings: memory-controllers: ti,gpmc: Add compatible for AM64 >>> memory: omap-gpmc: Add support for GPMC on AM64 SoC >>> memory: omap-gpmc: Use a compatible match table when checking for NAND >>> controller >>> mtd: rawnand: omap2: Select GPMC device driver for ARCH_K3 >>> >>> .../bindings/memory-controllers/ti,gpmc.yaml | 23 +++++++++- >>> drivers/memory/omap-gpmc.c | 46 ++++++++++++++----- >>> drivers/mtd/nand/raw/Kconfig | 1 + >>> drivers/mtd/nand/raw/omap2.c | 5 +- >>> include/linux/platform_data/mtd-nand-omap2.h | 9 +++- >>> 5 files changed, 67 insertions(+), 17 deletions(-) >>> >> >
WARNING: multiple messages have this Message-ID (diff)
From: Romain Naour <romain.naour@smile.fr> To: Grygorii Strashko <grygorii.strashko@ti.com>, Roger Quadros <rogerq@kernel.org>, krzysztof.kozlowski@canonical.com, miquel.raynal@bootlin.com, tony@atomide.com Cc: robh@kernel.org, kishon@ti.com, nm@ti.com, vigneshr@ti.com, linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org Subject: Re: [PATCH v4 0/4] memory: omap-gpmc: Add AM64 SoC support Date: Fri, 13 May 2022 10:49:35 +0200 [thread overview] Message-ID: <13fa1d59-7750-a327-c100-a53823509017@smile.fr> (raw) In-Reply-To: <5d8ba4e2-a281-5d0f-d65f-bb0121165b73@ti.com> Hi, Le 15/04/2022 à 15:06, Grygorii Strashko a écrit : > > > On 15/04/2022 11:59, Romain Naour wrote: >> Hello, >> >> Le 21/12/2021 à 14:17, Roger Quadros a écrit : >>> Hi, >>> >>> TI's AM64 SoC contains one GPMC module. Add driver support for it. >> >> What's the status of the GPMC interface on K3 architecture, especially for AM65, >> AM62 and other Jacinto 7 CPU devices ? >> >> TI currently don't recommend to use it for now even if there are still some GPMC >> use case with FPGA devices: >> >> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/994191/am6442-am64x-gpmc-support >> >> >> This patch series add omap-gpmc support for AM64 Soc but as of kernel 5.18-rc2, >> there is no devicetree using ti,am64-gpmc. >> >> This patch seems missing (at least): >> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-5.10.y&id=55c102a75d399896c7396229cd687bf97afb5cf6 >> > > It's not how LKML development process works - driver changes has to be sent first > and then DT changes as they accepted by different maintainers and through > different trees. Ok, I understand. DT changes are still under review [1] and are not yet merged in 5.18-rc6. Sorry for the noise. [1] https://lkml.org/lkml/2022/2/4/320 Best regards, Romain > >> >> Thanks! >> >> Best regards, >> Romain >> >>> >>> cheers, >>> -roger >>> >>> Changelog: >>> v4 >>> - move compatible match table to header file so it can be used by >>> GPMC driver even when NAND driver is not enabled or as a module. >>> GPMC driver is always enabled as built-in. >>> - Select OMAP_GPMC driver from MTD_NAND_OMAP2 driver config as >>> OMAP_GPMC is not essential for ARCH_K3 boot. >>> >>> v3 >>> - use compatible match table for checking for NAND controller node in >>> GPMC driver. >>> >>> v2 >>> - update DT binding doc to make reg-names and power-domains property >>> required only for specific SoC. >>> >>> Roger Quadros (4): >>> dt-bindings: memory-controllers: ti,gpmc: Add compatible for AM64 >>> memory: omap-gpmc: Add support for GPMC on AM64 SoC >>> memory: omap-gpmc: Use a compatible match table when checking for NAND >>> controller >>> mtd: rawnand: omap2: Select GPMC device driver for ARCH_K3 >>> >>> .../bindings/memory-controllers/ti,gpmc.yaml | 23 +++++++++- >>> drivers/memory/omap-gpmc.c | 46 ++++++++++++++----- >>> drivers/mtd/nand/raw/Kconfig | 1 + >>> drivers/mtd/nand/raw/omap2.c | 5 +- >>> include/linux/platform_data/mtd-nand-omap2.h | 9 +++- >>> 5 files changed, 67 insertions(+), 17 deletions(-) >>> >> > ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-05-13 8:49 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-21 13:17 [PATCH v4 0/4] memory: omap-gpmc: Add AM64 SoC support Roger Quadros 2021-12-21 13:17 ` Roger Quadros 2021-12-21 13:17 ` [PATCH v4 1/4] dt-bindings: memory-controllers: ti,gpmc: Add compatible for AM64 Roger Quadros 2021-12-21 13:17 ` [PATCH v4 1/4] dt-bindings: memory-controllers: ti, gpmc: " Roger Quadros 2021-12-21 13:17 ` [PATCH v4 2/4] memory: omap-gpmc: Add support for GPMC on AM64 SoC Roger Quadros 2021-12-21 13:17 ` Roger Quadros 2021-12-21 13:17 ` [PATCH v4 3/4] memory: omap-gpmc: Use a compatible match table when checking for NAND controller Roger Quadros 2021-12-21 13:17 ` Roger Quadros 2021-12-21 20:01 ` Roger Quadros 2021-12-21 20:01 ` Roger Quadros 2021-12-22 14:18 ` Miquel Raynal 2021-12-22 14:18 ` Miquel Raynal 2021-12-22 15:49 ` Krzysztof Kozlowski 2021-12-22 15:49 ` Krzysztof Kozlowski 2021-12-22 17:04 ` Roger Quadros 2021-12-22 17:04 ` Roger Quadros 2021-12-21 13:17 ` [PATCH v4 4/4] mtd: rawnand: omap2: Select GPMC device driver for ARCH_K3 Roger Quadros 2021-12-21 13:17 ` Roger Quadros 2021-12-21 13:49 ` Miquel Raynal 2021-12-21 13:49 ` Miquel Raynal 2021-12-22 11:50 ` Krzysztof Kozlowski 2021-12-22 11:50 ` Krzysztof Kozlowski 2021-12-22 14:19 ` Miquel Raynal 2021-12-22 14:19 ` Miquel Raynal 2021-12-22 15:52 ` [PATCH v4 0/4] memory: omap-gpmc: Add AM64 SoC support Krzysztof Kozlowski 2021-12-22 15:52 ` Krzysztof Kozlowski 2022-04-15 8:59 ` Romain Naour 2022-04-15 8:59 ` Romain Naour 2022-04-15 13:06 ` Grygorii Strashko 2022-04-15 13:06 ` Grygorii Strashko 2022-05-13 8:49 ` Romain Naour [this message] 2022-05-13 8:49 ` Romain Naour
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=13fa1d59-7750-a327-c100-a53823509017@smile.fr \ --to=romain.naour@smile.fr \ --cc=grygorii.strashko@ti.com \ --cc=kishon@ti.com \ --cc=krzysztof.kozlowski@canonical.com \ --cc=linux-mtd@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=miquel.raynal@bootlin.com \ --cc=nm@ti.com \ --cc=robh@kernel.org \ --cc=rogerq@kernel.org \ --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: linkBe 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.