From: Daniel Mack <zonque@gmail.com> To: "Mohammed, Afzal" <afzal@ti.com> Cc: "tony@atomide.com" <tony@atomide.com>, "Hunter, Jon" <jon-hunter@ti.com>, "paul@pwsan.com" <paul@pwsan.com>, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v6 00/10] OMAP-GPMC: generic time calc, prepare for driver Date: Mon, 27 Aug 2012 15:30:32 +0200 [thread overview] Message-ID: <503B7678.90308@gmail.com> (raw) In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E9BA713@DBDE01.ent.ti.com> On 27.08.2012 14:38, Mohammed, Afzal wrote: > On Mon, Aug 27, 2012 at 17:46:17, Daniel Mack wrote: > >>> Such a generic routine would help create a driver out of gpmc platform >>> code, which would be peripheral agnostic and thus lead to DT finally. >>> Input to generic timing calculation routine would be gpmc peripheral >>> timings, output - translated timings that gpmc can understand. Later, >>> to DT'ify, gpmc peripheral timings could be passed through DT. Input >>> timings that has been used here are selected such that it represents >>> those that are present in peripheral timing datasheets. >> >> What I don't understand yet about this new approach is where the gpmc >> client code should live in. In order to probe the drivers via DT, each >> driver would need to call the gpmc support functions itself, right? Is > > By gpmc client code, if you are referring to helper functions in > mach-omap2/gpmc-*, if things go as per plan, with DT, they will go away > and gpmc driver would handle those based on the information from DT. So the GPMC driver is the one that is matched from DT, and the NAND driver will the be instanciated from the (generic) GPMC driver? > No change would be needed for client drivers like smc91x ethernet drivers, > but NAND driver may need some change to live with DT as it is tightly > coupled with GPMC. NAND drivers also typically parse partition entries that are children of the DT node the are owning. >> the plan to obsolete helper functions like gpmc_nand_init() and move >> that functionality to the drivers? > > Yes, plan is to obsolete the functions like gpmc_nand_init, those tasks > would be handled by gpmc driver > >> >> I applied these patches locally and would like to help get the NAND >> controller on my AX33xx DT-driven board going. Let me know if I can do >> anything here. > > Thanks for offering the help, will take liberty to ask you for help > when required. BTW, do you have any OMAP family boards ? I do have a beaglboard xM, but the board I'm currently working with is a custom one based on an AM33xx. Thanks, Daniel
WARNING: multiple messages have this Message-ID (diff)
From: zonque@gmail.com (Daniel Mack) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v6 00/10] OMAP-GPMC: generic time calc, prepare for driver Date: Mon, 27 Aug 2012 15:30:32 +0200 [thread overview] Message-ID: <503B7678.90308@gmail.com> (raw) In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E9BA713@DBDE01.ent.ti.com> On 27.08.2012 14:38, Mohammed, Afzal wrote: > On Mon, Aug 27, 2012 at 17:46:17, Daniel Mack wrote: > >>> Such a generic routine would help create a driver out of gpmc platform >>> code, which would be peripheral agnostic and thus lead to DT finally. >>> Input to generic timing calculation routine would be gpmc peripheral >>> timings, output - translated timings that gpmc can understand. Later, >>> to DT'ify, gpmc peripheral timings could be passed through DT. Input >>> timings that has been used here are selected such that it represents >>> those that are present in peripheral timing datasheets. >> >> What I don't understand yet about this new approach is where the gpmc >> client code should live in. In order to probe the drivers via DT, each >> driver would need to call the gpmc support functions itself, right? Is > > By gpmc client code, if you are referring to helper functions in > mach-omap2/gpmc-*, if things go as per plan, with DT, they will go away > and gpmc driver would handle those based on the information from DT. So the GPMC driver is the one that is matched from DT, and the NAND driver will the be instanciated from the (generic) GPMC driver? > No change would be needed for client drivers like smc91x ethernet drivers, > but NAND driver may need some change to live with DT as it is tightly > coupled with GPMC. NAND drivers also typically parse partition entries that are children of the DT node the are owning. >> the plan to obsolete helper functions like gpmc_nand_init() and move >> that functionality to the drivers? > > Yes, plan is to obsolete the functions like gpmc_nand_init, those tasks > would be handled by gpmc driver > >> >> I applied these patches locally and would like to help get the NAND >> controller on my AX33xx DT-driven board going. Let me know if I can do >> anything here. > > Thanks for offering the help, will take liberty to ask you for help > when required. BTW, do you have any OMAP family boards ? I do have a beaglboard xM, but the board I'm currently working with is a custom one based on an AM33xx. Thanks, Daniel
next prev parent reply other threads:[~2012-08-27 13:30 UTC|newest] Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-21 10:41 [PATCH v6 00/10] OMAP-GPMC: generic time calc, prepare for driver Afzal Mohammed 2012-08-21 10:41 ` Afzal Mohammed 2012-08-21 10:45 ` [PATCH v6 01/10] ARM: OMAP2+: nand: unify init functions Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-21 11:37 ` Igor Grinberg 2012-08-21 11:37 ` Igor Grinberg 2012-08-21 10:45 ` [PATCH v6 02/10] ARM: OMAP2+: gpmc: handle additional timings Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-21 10:45 ` [PATCH v6 03/10] ARM: OMAP2+: onenand: refactor for clarity Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-21 10:45 ` [PATCH v6 04/10] ARM: OMAP2+: GPMC: Remove unused OneNAND get_freq() platform function Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-21 10:45 ` [PATCH v6 05/10] ARM: OMAP2+: gpmc: find features by ip rev check Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-22 2:08 ` Jon Hunter 2012-08-22 2:08 ` Jon Hunter 2012-08-21 10:45 ` [PATCH v6 06/10] ARM: OMAP2+: gpmc: remove cs# in sync clk div calc Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-22 2:11 ` Jon Hunter 2012-08-22 2:11 ` Jon Hunter 2012-08-21 10:45 ` [PATCH v6 07/10] ARM: OMAP2+: gpmc: generic timing calculation Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-23 2:58 ` Jon Hunter 2012-08-23 2:58 ` Jon Hunter 2012-08-24 19:54 ` Tony Lindgren 2012-08-24 19:54 ` Tony Lindgren 2012-08-27 11:46 ` Mohammed, Afzal 2012-08-27 11:46 ` Mohammed, Afzal 2012-08-27 10:37 ` Mohammed, Afzal 2012-08-27 10:37 ` Mohammed, Afzal 2012-08-27 20:30 ` Jon Hunter 2012-08-27 20:30 ` Jon Hunter 2012-08-28 12:21 ` Mohammed, Afzal 2012-08-28 12:21 ` Mohammed, Afzal 2012-08-21 10:45 ` [PATCH v6 08/10] ARM: OMAP2+: onenand: " Afzal Mohammed 2012-08-21 10:45 ` Afzal Mohammed 2012-08-21 10:46 ` [PATCH v6 09/10] ARM: OMAP2+: smc91x: " Afzal Mohammed 2012-08-21 10:46 ` Afzal Mohammed 2012-08-21 10:46 ` [PATCH v6 10/10] ARM: OMAP2+: tusb6010: " Afzal Mohammed 2012-08-21 10:46 ` Afzal Mohammed 2012-08-24 19:46 ` Tony Lindgren 2012-08-24 19:46 ` Tony Lindgren 2012-08-27 8:34 ` Mohammed, Afzal 2012-08-27 8:34 ` Mohammed, Afzal 2012-09-03 5:34 ` Mohammed, Afzal 2012-09-03 5:34 ` Mohammed, Afzal 2012-09-06 7:39 ` Mohammed, Afzal 2012-09-06 7:39 ` Mohammed, Afzal 2012-09-06 20:43 ` Tony Lindgren 2012-09-06 20:43 ` Tony Lindgren 2012-09-11 18:46 ` Tony Lindgren 2012-09-11 18:46 ` Tony Lindgren 2012-09-12 9:50 ` Mohammed, Afzal 2012-09-12 9:50 ` Mohammed, Afzal 2012-09-14 10:20 ` Mohammed, Afzal 2012-09-14 10:20 ` Mohammed, Afzal 2012-09-17 8:39 ` Mohammed, Afzal 2012-09-17 8:39 ` Mohammed, Afzal 2012-09-17 22:50 ` Tony Lindgren 2012-09-17 22:50 ` Tony Lindgren 2012-09-17 23:10 ` Tony Lindgren 2012-09-17 23:10 ` Tony Lindgren 2012-09-19 13:43 ` Mohammed, Afzal 2012-09-19 13:43 ` Mohammed, Afzal 2012-09-07 0:15 ` Paul Walmsley 2012-09-07 0:15 ` Paul Walmsley 2012-08-27 12:16 ` [PATCH v6 00/10] OMAP-GPMC: generic time calc, prepare for driver Daniel Mack 2012-08-27 12:16 ` Daniel Mack 2012-08-27 12:38 ` Mohammed, Afzal 2012-08-27 12:38 ` Mohammed, Afzal 2012-08-27 13:30 ` Daniel Mack [this message] 2012-08-27 13:30 ` Daniel Mack 2012-08-27 14:01 ` Mohammed, Afzal 2012-08-27 14:01 ` Mohammed, Afzal
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=503B7678.90308@gmail.com \ --to=zonque@gmail.com \ --cc=afzal@ti.com \ --cc=jon-hunter@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=paul@pwsan.com \ --cc=tony@atomide.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.