public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Magnus Damm" <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 04/04] resource: add new IORESOURCE_CLK type
Date: Thu, 17 Jul 2008 16:20:32 -0700	[thread overview]
Message-ID: <20080717162032.f5dca88d.akpm@linux-foundation.org> (raw)
In-Reply-To: <aec7e5c30807150119r160a104en5780c3288d50c60d@mail.gmail.com>

On Tue, 15 Jul 2008 17:19:24 +0900
"Magnus Damm" <magnus.damm@gmail.com> wrote:

> Hi Andrew,
> 
> Thanks for picking up my patches.
> 
> On Sat, Jul 12, 2008 at 4:18 AM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > On Wed, 09 Jul 2008 20:55:02 +0900 Magnus Damm <magnus.damm@gmail.com> wrote:
> >
> >> This patch rearranges the values of the IORESOURCE_TYPE_BITS from
> >> one bit per type to a 4-bit counter. Also, IORESOURCE_CLK is added.
> >> Not sure if it is better to start counting from 0 instead of 1.
> >>
> >
> > I don't believe this is an adequate changelog.  It contains the "what" but
> > not the "why".
> 
> Yeah, sorry about that. I should have been more clear.
> 
> > Why did we switch from one-bit to four-bits?
> 
> The 4-bit encoding is there because I thought it was a waste of bits
> to use one bit per type. =)
> 
> I wanted to add IORESOURCE_CLK and while at it I was playing around
> with changing the code to use a 4-bit value for resource type. We may
> already have spare bits available that are more suitable for new types
> though.
> 
> > Why did we add IORESOURCE_CLK?
> 
> Currently we use struct resource with the types
> IORESOURCE_MEM/IORESOURCE_IO and IORESOUCE_IRQ to pass I/O and
> interrupt parameters to platform drivers. That works fine, but I'd
> like to extend this so we also pass clock information. Basically a
> string that tells the platform driver which clock that should be used
> with clk_get() for a certain driver instance.
> 
> I'm sure there are other ways to do this, but I'd like to have a
> generic way to pass a clock string to platform devices. Using a hard
> coded string in the device driver won't do since we may have multiple
> instances of drivers that need to use different clocks. Extending
> struct resource seems to be the easiest way to do this IMO.

umm, has there been any comment on all of this yet?

Perhaps you should just send everything again with clearer/completer
descriptions.

> If people are happy with this idea then i'd be more than happy to fix
> up and resend this patch.

We're all asleep.  Please do whatever you think is best and we'll merge
it - that'll wake 'em up.


      reply	other threads:[~2008-07-17 23:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 11:54 [PATCH 00/04] resource: type and size patches Magnus Damm
2008-07-09 11:54 ` [PATCH 01/04] resource: add resource_size() Magnus Damm
2008-07-09 11:54 ` [PATCH 02/04] resource: add resource_type() and IORESOURCE_TYPE_BITS Magnus Damm
2008-07-09 11:54 ` [PATCH 03/04] resource: use new resource type changes Magnus Damm
2008-07-09 12:11   ` Josh Boyer
2008-07-11 19:18     ` Andrew Morton
2008-07-09 11:55 ` [PATCH 04/04] resource: add new IORESOURCE_CLK type Magnus Damm
2008-07-11 19:18   ` Andrew Morton
2008-07-15  8:19     ` Magnus Damm
2008-07-17 23:20       ` Andrew Morton [this message]

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=20080717162032.f5dca88d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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