public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Gianluca <gianlucarenzi@eptar.com>
To: MTD List <linux-mtd@lists.infradead.org>
Subject: Adding a second ChipSelect to Samsung s3c2410 driver
Date: Wed, 20 Dec 2006 16:23:44 +0100	[thread overview]
Message-ID: <200612201623.44341.gianlucarenzi@eptar.com> (raw)

Hello,
I am working on a Samsung SMDK S3C2442 eval board made by Meritech Ltd.
It is based on S3C2440 core with NAND Flash and SDRAM, all embedded into the same SoC,
running at 300Mhz.
This board has an external NAND chip too. The internal nand flash chip select is connected
with microprocessor nFCE chip select line coming from internal NAND Controller,
and the external flash chip select is routed to nGCS5/GPA16 pin.

This NAND mtd/nand driver is working and it is using the s3c2410.c, but it uses only the nFCE as
chip select. Which is the cleanest way to add another chip select (in this case an GPIO line) to this
driver, without breaking the whole word?

Kindest regards,
---
Gianluca Renzi

                 reply	other threads:[~2006-12-20 15:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200612201623.44341.gianlucarenzi@eptar.com \
    --to=gianlucarenzi@eptar.com \
    --cc=linux-mtd@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox