From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com> To: Boris Brezillon <boris.brezillon@collabora.com> Cc: qi-ming.wu@intel.com, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, cheol.yong.kim@intel.com, hauke.mehrtens@intel.com, anders.roxell@linaro.org, vigneshr@ti.com, arnd@arndb.de, richard@nod.at, brendanhiggins@google.com, linux-mips@vger.kernel.org, robh+dt@kernel.org, miquel.raynal@bootlin.com, tglx@linutronix.de, masonccyang@mxic.com.tw, andriy.shevchenko@intel.com Subject: Re: [PATCH v4 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Date: Thu, 30 Apr 2020 17:07:03 +0800 [thread overview] Message-ID: <1d5aec11-a7b5-01c2-6614-16e57c64511b@linux.intel.com> (raw) In-Reply-To: <20200430103658.4b0b979e@collabora.com> Hi Boris, On 30/4/2020 4:36 pm, Boris Brezillon wrote: > On Thu, 30 Apr 2020 16:30:15 +0800 > "Ramuthevar, Vadivel MuruganX" > <vadivel.muruganx.ramuthevar@linux.intel.com> wrote: > >>>>> >>>>> And now I'd like you to explain why 5 is the right value for that field >>>>> (I guess that has to do with the position of the CS/ALE/CLE pins). >>>> >>>> 5 : bit 26, 25, 24, 23, 22 to be included for comparison in the >>> >>> That's 6 bits to me, not 5. >> >> No , 5 bits only the above case. > > Oops, right, sorry for the brain fart. > >>> >>> The question is, is it the same value we have in nand_pa or it is >>> different? >>> >> Different address which is 0xE1400000 NAND_BASE_PHY address. > > Then why didn't you tell me they didn't match when I suggested to pass sorry, because you keep asking nand_pa after that only I realized that. > nand_pa? So now the question is, what does this address represent? EBU-MODULE _________ _______________________ | | | |NAND CTRL | | FPI BUS |==>| CS0(0x174) | 0xE100 ( 0xE14/0xE1C) NAND_PHY_BASE |_________| |_CS1(0x17C)_|__________ | EBU_CONRTROLLER_BASE : 0xE0F0_0000 HSNAND_BASE: 0xE100_0000 NAND_CS0: 0xE140_0000 NAND_CS1: 0xE1C0_0000 MEM_REGION_BASE_CS0: 0x17400 (internal to ebu controller ) MEM_REGION_BASE_CS1: 0x17C00 >Do you have a reference manual I can look at to understand what this is? We dont have reference manual since it is new SoC, we keep get information from HW team and we have only register map Thanks a lot !!! Regards Vadivel >
WARNING: multiple messages have this Message-ID (diff)
From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com> To: Boris Brezillon <boris.brezillon@collabora.com> Cc: cheol.yong.kim@intel.com, devicetree@vger.kernel.org, masonccyang@mxic.com.tw, anders.roxell@linaro.org, vigneshr@ti.com, arnd@arndb.de, hauke.mehrtens@intel.com, richard@nod.at, brendanhiggins@google.com, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org, robh+dt@kernel.org, linux-mtd@lists.infradead.org, miquel.raynal@bootlin.com, tglx@linutronix.de, qi-ming.wu@intel.com, andriy.shevchenko@intel.com Subject: Re: [PATCH v4 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Date: Thu, 30 Apr 2020 17:07:03 +0800 [thread overview] Message-ID: <1d5aec11-a7b5-01c2-6614-16e57c64511b@linux.intel.com> (raw) In-Reply-To: <20200430103658.4b0b979e@collabora.com> Hi Boris, On 30/4/2020 4:36 pm, Boris Brezillon wrote: > On Thu, 30 Apr 2020 16:30:15 +0800 > "Ramuthevar, Vadivel MuruganX" > <vadivel.muruganx.ramuthevar@linux.intel.com> wrote: > >>>>> >>>>> And now I'd like you to explain why 5 is the right value for that field >>>>> (I guess that has to do with the position of the CS/ALE/CLE pins). >>>> >>>> 5 : bit 26, 25, 24, 23, 22 to be included for comparison in the >>> >>> That's 6 bits to me, not 5. >> >> No , 5 bits only the above case. > > Oops, right, sorry for the brain fart. > >>> >>> The question is, is it the same value we have in nand_pa or it is >>> different? >>> >> Different address which is 0xE1400000 NAND_BASE_PHY address. > > Then why didn't you tell me they didn't match when I suggested to pass sorry, because you keep asking nand_pa after that only I realized that. > nand_pa? So now the question is, what does this address represent? EBU-MODULE _________ _______________________ | | | |NAND CTRL | | FPI BUS |==>| CS0(0x174) | 0xE100 ( 0xE14/0xE1C) NAND_PHY_BASE |_________| |_CS1(0x17C)_|__________ | EBU_CONRTROLLER_BASE : 0xE0F0_0000 HSNAND_BASE: 0xE100_0000 NAND_CS0: 0xE140_0000 NAND_CS1: 0xE1C0_0000 MEM_REGION_BASE_CS0: 0x17400 (internal to ebu controller ) MEM_REGION_BASE_CS1: 0x17C00 >Do you have a reference manual I can look at to understand what this is? We dont have reference manual since it is new SoC, we keep get information from HW team and we have only register map Thanks a lot !!! Regards Vadivel > ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-04-30 9:07 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 10:42 [PATCH v4 0/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX 2020-04-29 10:42 ` Ramuthevar, Vadivel MuruganX 2020-04-29 10:42 ` [PATCH v4 1/2] dt-bindings: mtd: Add YAML for Nand Flash Controller support Ramuthevar,Vadivel MuruganX 2020-04-29 10:42 ` Ramuthevar, Vadivel MuruganX 2020-04-29 15:34 ` Boris Brezillon 2020-04-29 15:34 ` Boris Brezillon 2020-04-30 1:07 ` Ramuthevar, Vadivel MuruganX 2020-04-30 1:07 ` Ramuthevar, Vadivel MuruganX 2020-04-29 10:42 ` [PATCH v4 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX 2020-04-29 10:42 ` Ramuthevar, Vadivel MuruganX 2020-04-29 11:33 ` Boris Brezillon 2020-04-29 11:33 ` Boris Brezillon 2020-04-29 13:29 ` Ramuthevar, Vadivel MuruganX 2020-04-29 13:29 ` Ramuthevar, Vadivel MuruganX 2020-04-29 13:32 ` Boris Brezillon 2020-04-29 13:32 ` Boris Brezillon 2020-04-29 14:26 ` Ramuthevar, Vadivel MuruganX 2020-04-29 14:26 ` Ramuthevar, Vadivel MuruganX 2020-04-29 14:22 ` Boris Brezillon 2020-04-29 14:22 ` Boris Brezillon 2020-04-29 14:33 ` Ramuthevar, Vadivel MuruganX 2020-04-29 14:33 ` Ramuthevar, Vadivel MuruganX 2020-04-29 14:48 ` Boris Brezillon 2020-04-29 14:48 ` Boris Brezillon 2020-04-29 15:18 ` Ramuthevar, Vadivel MuruganX 2020-04-29 15:18 ` Ramuthevar, Vadivel MuruganX 2020-04-29 15:29 ` Ramuthevar, Vadivel MuruganX 2020-04-29 15:29 ` Ramuthevar, Vadivel MuruganX 2020-04-29 15:31 ` Boris Brezillon 2020-04-29 15:31 ` Boris Brezillon 2020-04-30 7:50 ` Ramuthevar, Vadivel MuruganX 2020-04-30 7:50 ` Ramuthevar, Vadivel MuruganX 2020-04-30 8:21 ` Boris Brezillon 2020-04-30 8:21 ` Boris Brezillon 2020-04-30 8:30 ` Ramuthevar, Vadivel MuruganX 2020-04-30 8:30 ` Ramuthevar, Vadivel MuruganX 2020-04-30 8:36 ` Boris Brezillon 2020-04-30 8:36 ` Boris Brezillon 2020-04-30 9:07 ` Ramuthevar, Vadivel MuruganX [this message] 2020-04-30 9:07 ` Ramuthevar, Vadivel MuruganX 2020-04-30 12:36 ` Boris Brezillon 2020-04-30 12:36 ` Boris Brezillon 2020-04-30 13:01 ` Boris Brezillon 2020-04-30 13:01 ` Boris Brezillon 2020-05-04 1:58 ` Ramuthevar, Vadivel MuruganX 2020-05-04 1:58 ` Ramuthevar, Vadivel MuruganX 2020-05-04 2:02 ` Ramuthevar, Vadivel MuruganX 2020-05-04 2:02 ` Ramuthevar, Vadivel MuruganX 2020-05-04 7:08 ` Boris Brezillon 2020-05-04 7:08 ` Boris Brezillon 2020-05-04 7:15 ` Ramuthevar, Vadivel MuruganX 2020-05-04 7:15 ` Ramuthevar, Vadivel MuruganX 2020-05-04 7:17 ` Boris Brezillon 2020-05-04 7:17 ` Boris Brezillon 2020-05-04 8:50 ` Ramuthevar, Vadivel MuruganX 2020-05-04 8:50 ` Ramuthevar, Vadivel MuruganX 2020-05-04 8:58 ` Boris Brezillon 2020-05-04 8:58 ` Boris Brezillon 2020-05-04 9:17 ` Ramuthevar, Vadivel MuruganX 2020-05-04 9:17 ` Ramuthevar, Vadivel MuruganX 2020-05-05 5:28 ` Ramuthevar, Vadivel MuruganX 2020-05-05 5:28 ` Ramuthevar, Vadivel MuruganX 2020-05-05 7:00 ` Boris Brezillon 2020-05-05 7:00 ` Boris Brezillon 2020-05-05 7:17 ` Ramuthevar, Vadivel MuruganX 2020-05-05 7:17 ` Ramuthevar, Vadivel MuruganX 2020-05-04 1:54 ` Ramuthevar, Vadivel MuruganX 2020-05-04 1:54 ` Ramuthevar, Vadivel MuruganX
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=1d5aec11-a7b5-01c2-6614-16e57c64511b@linux.intel.com \ --to=vadivel.muruganx.ramuthevar@linux.intel.com \ --cc=anders.roxell@linaro.org \ --cc=andriy.shevchenko@intel.com \ --cc=arnd@arndb.de \ --cc=boris.brezillon@collabora.com \ --cc=brendanhiggins@google.com \ --cc=cheol.yong.kim@intel.com \ --cc=devicetree@vger.kernel.org \ --cc=hauke.mehrtens@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=masonccyang@mxic.com.tw \ --cc=miquel.raynal@bootlin.com \ --cc=qi-ming.wu@intel.com \ --cc=richard@nod.at \ --cc=robh+dt@kernel.org \ --cc=tglx@linutronix.de \ --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.