public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] spi/kirkwood: add weak functions board_spi_bus_claim/release
Date: Thu, 29 Mar 2012 17:44:35 +0200	[thread overview]
Message-ID: <4F748363.8040507@keymile.com> (raw)
In-Reply-To: <4F745A65.4090204@keymile.com>

Hi Prafulla,

On 03/29/2012 02:49 PM, Valentin Longchamp wrote:
> On 03/28/2012 09:48 AM, Prafulla Wadaskar wrote:
>> Basically spi_claim_bus and spi_release_bus are not supported in current Kirkwood spi driver.
>> These are needed if someone wish to share the same interface pins with some other peripheral (that is your use case)
> 
> Correct, this is exactly our use case: we have the NAND Flash Controller and the
> SPI controller that share the same pins.
> 
>>
>> But this is not board specific whereas, it should be feature enhancement for Kirkwood spi driver.
> 
> This is correct for the mpp part of spi_claim_bus. If you look at the actual
> implementation that we do in our board specific function, there is an additional
> step that is needed by our board design.
> 

I have started to implement this, and now I see that with your approach of doing
the mpp part in the driver does not work and my proposed solution of doing this
with board specific functions is the correct one:

The SPI_SI, SPI_SCK, SPI_CSn all can be used with different mpp configuration.
This is a board design parameter. How can the driver know which one is used on
the board ?

Requesting all of them is not an option and adding some configuration would be a
significant effort while the problem is already tackled with the board specific
functions.

-- 
Valentin Longchamp
Embedded Software Engineer
Hardware and Chip Integration
______________________________________
KEYMILE AG
Schwarzenburgstr. 73
CH-3097 Liebefeld
Phone +41 31 377 1318
Fax   +41 31 377 1212
valentin.longchamp at keymile.com
www.keymile.com
______________________________________
KEYMILE: A Specialist as a Partner

  parent reply	other threads:[~2012-03-29 15:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26  9:58 [U-Boot] [PATCH v2] spi/kirkwood: add weak functions board_spi_bus_claim/release Valentin Longchamp
2012-03-27 13:27 ` Valentin Longchamp
2012-03-28  7:48   ` Prafulla Wadaskar
2012-03-29 12:49     ` Valentin Longchamp
2012-03-29 14:21       ` Prafulla Wadaskar
2012-03-29 14:49         ` Valentin Longchamp
2012-03-29 15:44       ` Valentin Longchamp [this message]
2012-03-30 11:34         ` Prafulla Wadaskar
2012-03-30 12:14           ` Valentin Longchamp
2012-03-30 12:58             ` Prafulla Wadaskar
2012-04-02 13:37               ` Valentin Longchamp
2012-04-03  6:35                 ` Prafulla Wadaskar
2012-04-04  7:01                   ` Valentin Longchamp
2012-04-04  7:12                     ` Prafulla Wadaskar

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=4F748363.8040507@keymile.com \
    --to=valentin.longchamp@keymile.com \
    --cc=u-boot@lists.denx.de \
    /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