linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Jochen Friedrich <jochen@scram.de>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Implement GPIO LIB API on CPM2 Freescale SoC.
Date: Thu, 17 Apr 2008 14:08:43 +0200	[thread overview]
Message-ID: <200804171408.46533.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <480732C9.9080800@scram.de>

[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]

On Thursday 17 April 2008 13:21, Jochen Friedrich wrote:
> Hi Laurent,
> 
> >> http://patchwork.ozlabs.org/linuxppc/patch?id=16282
> > 
> > The link doesn't seem to be related.
> 
> http://patchwork.ozlabs.org/linuxppc/patch?id=17490 is the correct one. 

Thanks.

> > I'll rework the patch to move CPM2 GPIO support to cpm_common.c. Have you 
> > thought about a proper name for the compatible property ?
> 
> I would leave cpm_init_par_io() in cpm2.c and just move the other parts.
> - for cpm2, the property fsl,cpm2-pario-bank is correct.
> - for cpm1, i'm thinking of something like fsl,cpm1-pario-bank32b and 
fsl,cpm1-pario-bank32e.

Any preference for common function names ? cpm2_gpio32* might be too 
CPM2-specific for cpm_common.c. cpm_gpio32* is a bit too generic as it 
doesn't support port E on the CPM1.

BTW, what's the purpose of the shadow data register in the CPM GPIO chip 
structure ? As the set operation is protected by a spinlock, the only use I 
can think of is to prevent changing bits in the PDAT register for pins 
configured as inputs. Is that correct ? If so this should be clearly 
documented in the code.

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-17 12:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17  9:48 [PATCH] powerpc: Implement GPIO LIB API on CPM2 Freescale SoC Laurent Pinchart
2008-04-17 10:13 ` Jochen Friedrich
2008-04-17 11:11   ` Laurent Pinchart
2008-04-17 11:21     ` Jochen Friedrich
2008-04-17 12:08       ` Laurent Pinchart [this message]
2008-04-17 12:46         ` Jochen Friedrich
2008-04-17 12:48         ` Jochen Friedrich

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=200804171408.46533.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=jochen@scram.de \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).