All of lore.kernel.org
 help / color / mirror / Atom feed
From: Afzal Mohammed <x0148406@ti.com>
To: Daniel Mack <zonque@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	jon-hunter@ti.com, paul@pwsan.com, nsekhar@ti.com
Subject: Re: [PATCH 4/4] OMAP: mtd: gpmc: add DT bindings for GPMC timings and NAND
Date: Mon, 29 Oct 2012 13:40:55 +0530	[thread overview]
Message-ID: <508E3A0F.3040309@ti.com> (raw)
In-Reply-To: <50887A6B.3050108@gmail.com>

Hi Daniel,

On Thursday 25 October 2012 05:01 AM, Daniel Mack wrote:

> Thanks for the review. I'll wait for feedback from Afzal next week and
> then repost. Wanted to see first if that goes in the right direction at
> all before bordering the DT people with binding details :)

I was thinking of a generic approach, where there won't be
any check for peripheral device type.

But going that path would delay achieving DT, may be let's
proceed with your approach to start with so that we can
have a minimal level of DT support for GPMC and probably
we can make it generic later. While adding new properties,
it would be better to keep in mind that we need not change
these later once gpmc DT is made generic.

Regarding the bindings, there are some generic nand
properties like ecc already available, may be that be made
use here. Also perhaps memory size (and offset if
needed) to be mapped for peripherals can go with reg
property of child.

Regards
Afzal

WARNING: multiple messages have this Message-ID (diff)
From: x0148406@ti.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] OMAP: mtd: gpmc: add DT bindings for GPMC timings and NAND
Date: Mon, 29 Oct 2012 13:40:55 +0530	[thread overview]
Message-ID: <508E3A0F.3040309@ti.com> (raw)
In-Reply-To: <50887A6B.3050108@gmail.com>

Hi Daniel,

On Thursday 25 October 2012 05:01 AM, Daniel Mack wrote:

> Thanks for the review. I'll wait for feedback from Afzal next week and
> then repost. Wanted to see first if that goes in the right direction at
> all before bordering the DT people with binding details :)

I was thinking of a generic approach, where there won't be
any check for peripheral device type.

But going that path would delay achieving DT, may be let's
proceed with your approach to start with so that we can
have a minimal level of DT support for GPMC and probably
we can make it generic later. While adding new properties,
it would be better to keep in mind that we need not change
these later once gpmc DT is made generic.

Regarding the bindings, there are some generic nand
properties like ecc already available, may be that be made
use here. Also perhaps memory size (and offset if
needed) to be mapped for peripherals can go with reg
property of child.

Regards
Afzal

  reply	other threads:[~2012-10-29  8:11 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 19:55 [PATCH 0/4] RFC: OMAP GPMC bindings Daniel Mack
2012-10-22 19:55 ` Daniel Mack
2012-10-22 19:55 ` [PATCH 1/4] mtd: omap-nand: pass device_node in platform data Daniel Mack
2012-10-22 19:55   ` Daniel Mack
2012-10-22 19:55 ` [PATCH 2/4] ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs Daniel Mack
2012-10-22 19:55   ` Daniel Mack
2012-10-22 19:55 ` [PATCH 3/4] ARM: OMAP: gpmc: don't create devices from initcall on DT Daniel Mack
2012-10-22 19:55   ` Daniel Mack
2012-10-22 19:55 ` [PATCH 4/4] OMAP: mtd: gpmc: add DT bindings for GPMC timings and NAND Daniel Mack
2012-10-22 19:55   ` Daniel Mack
2012-10-24 23:27   ` Tony Lindgren
2012-10-24 23:27     ` Tony Lindgren
2012-10-24 23:31     ` Daniel Mack
2012-10-24 23:31       ` Daniel Mack
2012-10-29  8:10       ` Afzal Mohammed [this message]
2012-10-29  8:10         ` Afzal Mohammed
2012-10-29 11:15         ` Daniel Mack
2012-10-29 11:15           ` Daniel Mack
2012-10-29 11:28           ` Afzal Mohammed
2012-10-29 11:28             ` Afzal Mohammed
2012-10-29 12:32             ` Daniel Mack
2012-10-29 12:32               ` Daniel Mack
2012-10-29 12:56               ` Afzal Mohammed
2012-10-29 12:56                 ` Afzal Mohammed
2012-10-25  1:28   ` Jon Hunter
2012-10-25  1:28     ` Jon Hunter
2012-10-25  8:00     ` Daniel Mack
2012-10-25  8:00       ` Daniel Mack
2012-10-25 13:16       ` Jon Hunter
2012-10-25 13:16         ` Jon Hunter
2012-10-29  8:09       ` Afzal Mohammed
2012-10-29  8:09         ` Afzal Mohammed
2012-10-25  1:53   ` Jon Hunter
2012-10-25  1:53     ` Jon Hunter
2012-10-25  9:43     ` Daniel Mack
2012-10-25  9:43       ` Daniel Mack
2012-10-25 13:22       ` Jon Hunter
2012-10-25 13:22         ` Jon Hunter

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=508E3A0F.3040309@ti.com \
    --to=x0148406@ti.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.com \
    --cc=zonque@gmail.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 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.