All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: linux-omap@vger.kernel.org, Benoit Cousson <b-cousson@ti.com>,
	Jon Hunter <jgchunter@gmail.com>
Subject: Re: [PATCH 1/2] ARM: OMAP2+: gpmc: get number of useable GPMC chip-selects via DT
Date: Wed, 12 Jun 2013 09:57:43 -0700	[thread overview]
Message-ID: <20130612165742.GG8164@atomide.com> (raw)
In-Reply-To: <1370001691-29320-1-git-send-email-pekon@ti.com>

* Gupta, Pekon <pekon@ti.com> [130531 05:07]:
> From: "Gupta, Pekon" <pekon@ti.com>
> 
> This patch enables usage of DT property 'gpmc,num-cs' as already documented in
> Documentation/devicetree/bindings/bus/ti-gpmc.txt
> 
> Though GPMC hardware supports upto 8 chip-selects, but all chip-selects may
> not be available for use because:
> - chip-select pin may not be bonded out at SoC device boundary.
> - chip-select pin-mux may conflict with other pins usage.
> - board level constrains.
> 
> gpmc,num-cs allows user to configure maximum number of GPMC chip-selects
> available for use on any given platform. This ensures:
> - GPMC child nodes having chip-selects within allowed range are only probed.
> - And un-used GPMC chip-selects remain blocked.(may be for security reasons).

Thanks applying this patch into omap-for-v3.11/gpmc.

Regards,

Tony

      parent reply	other threads:[~2013-06-12 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 12:01 [PATCH 1/2] ARM: OMAP2+: gpmc: get number of useable GPMC chip-selects via DT Gupta, Pekon
2013-05-31 12:01 ` [PATCH 2/2] ARM: OMAP2+: gpmc: removed 'gpmc,device-nand'. type determined from node-name Gupta, Pekon
2013-06-12 16:59   ` Tony Lindgren
2013-06-18 10:42     ` Gupta, Pekon
2013-06-12 16:57 ` Tony Lindgren [this message]

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=20130612165742.GG8164@atomide.com \
    --to=tony@atomide.com \
    --cc=b-cousson@ti.com \
    --cc=jgchunter@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=pekon@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 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.