From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC][PATCH] MPC832x_RDB: update dts to use spi, register mmc_spi stub
Date: Tue, 7 Aug 2007 00:08:17 +0200 [thread overview]
Message-ID: <2ec8ba15bad689633a8dd8738acc0399@kernel.crashing.org> (raw)
In-Reply-To: <20070806163137.136cc689.kim.phillips@freescale.com>
>>>>>>> + max-speed-hz = <bebc20>; /* 12500000 Hz */
>>>>
>>>> Just max-speed.
>>>
>>> Segher, how is this different from:
>>>
>>> http://ozlabs.org/pipermail/linuxppc-dev/2007-April/034557.html
>>
>> Not sure what you mean. I'm just saying that "speed-hz" is a
>> terrible name, I'm not saying that "max-speed" is perfect at all.
>
> yet you suggest a /more/ generic name, contrary to your prior comments.
Uh, you mean "hz" doesn't mean "Hertz"? What a great name,
then</sarcasm>.
> My interpretation of your recent comments is that 'max-speed' is now a
> valid property name for devices such as ucc_geth. Do I have that
> right?
It is (and always was) a _valid_ name. Whether it is a _good_
name depends on the context; if there is only one speed it can
be (reasonably) referring to, it is okay; if not (or even if so),
you're better off being a bit more verbose in your property names.
No need to go over the top though, it's all a tradeoff.
Segher
next prev parent reply other threads:[~2007-08-06 22:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 13:57 [RFC][PATCH] MPC832x_RDB: update dts to use spi, register mmc_spi stub Anton Vorontsov
2007-07-26 15:36 ` Joakim Tjernlund
2007-07-26 15:47 ` Anton Vorontsov
2007-07-26 19:40 ` [RFC][PATCH] MPC832x_RDB: update dts to use spi, registermmc_spi stub Joakim Tjernlund
2007-07-27 7:55 ` Kumar Gala
2007-07-31 21:47 ` Segher Boessenkool
2007-07-27 8:14 ` [RFC][PATCH] MPC832x_RDB: update dts to use spi, register mmc_spi stub Kumar Gala
2007-07-27 11:45 ` Anton Vorontsov
2007-07-27 13:55 ` Kumar Gala
2007-07-27 16:40 ` Scott Wood
2007-07-31 22:00 ` Segher Boessenkool
2007-08-01 17:43 ` Scott Wood
2007-08-06 18:24 ` Segher Boessenkool
2007-07-31 22:06 ` Segher Boessenkool
2007-08-01 13:29 ` Anton Vorontsov
2007-08-06 18:18 ` Segher Boessenkool
2007-08-07 10:53 ` Anton Vorontsov
2007-08-07 16:11 ` Segher Boessenkool
2007-08-01 19:16 ` Kim Phillips
2007-08-06 18:25 ` Segher Boessenkool
2007-08-06 21:31 ` Kim Phillips
2007-08-06 22:08 ` Segher Boessenkool [this message]
2007-07-31 22:10 ` Segher Boessenkool
2007-08-01 12:34 ` Anton Vorontsov
2007-08-06 18:09 ` Segher Boessenkool
2007-08-06 18:50 ` Scott Wood
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=2ec8ba15bad689633a8dd8738acc0399@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=kim.phillips@freescale.com \
--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).