linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] 8xx: Add support for the MPC852 based board from keymile.
Date: Tue, 18 Mar 2008 09:04:14 +0100	[thread overview]
Message-ID: <47DF777E.2030103@denx.de> (raw)
In-Reply-To: <20080318183320.49c98183.sfr@canb.auug.org.au>

Hello Stephen,

Stephen Rothwell wrote:
> On Tue, 18 Mar 2008 08:13:06 +0100 Heiko Schocher <hs@denx.de> wrote:
>> Stephen Rothwell wrote:
>>> On Fri, 14 Mar 2008 10:24:30 +0100 Heiko Schocher <hs@denx.de> wrote:
>> [...]
>>>> +struct cpm_pin {
>>>> +		int port, pin, flags;
>>>> +};
>>> I wish someone would consolidate all these definitions of cpm_pin.
>> Hmm... do you mean something like, moving this struct
>> in cpm1.h and ...
> 
> Yes or somewhere else appropriate.
> 
>>>> +	for (i = 0; i < ARRAY_SIZE(mgsuvd_pins); i++) {
>>>> +		struct cpm_pin *pin = &mgsuvd_pins[i];
>>>> +		cpm1_set_pin(pin->port, pin->pin, pin->flags);
>>>> +	}
>>> And the code that uses them ...
>> making in arch/powerpc/sysdev/cpm1.c a function
>> cpm1_setup_pins (struct cpm_pin *pins) ?
> 
> Yes.
> 
> This is not necessary for your patch, but would be a nice cleanup later.
> N.B. this struct is alos used by users of cpm2_set_pin().

OK. Another thought about this. Shouldnt this table go in the dts?
A device node like

cpm_pin {
	pins = <port pin flags>;
};

would be nice, or?

bye,
Heiko

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2008-03-18  7:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  9:24 [PATCH v2] 8xx: Add support for the MPC852 based board from keymile Heiko Schocher
2008-03-14 23:25 ` Stephen Rothwell
2008-03-18  7:13   ` Heiko Schocher
2008-03-18  7:33     ` Stephen Rothwell
2008-03-18  8:04       ` Heiko Schocher [this message]
2008-03-18 15:11         ` Scott Wood
2008-03-18 16:19           ` Wolfgang Denk
2008-03-18 16:56             ` Scott Wood
2008-03-18 16:19         ` Vitaly Bordug
2008-03-19  6:51           ` Heiko Schocher
2008-03-17 22:46 ` Scott Wood
2008-03-18  8:07   ` [PATCH v3] " Heiko Schocher

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=47DF777E.2030103@denx.de \
    --to=hs@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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).