From: Adam Belay <ambx1@neo.rr.com>
To: Greg KH <greg@kroah.com>, Matthew Gilbert <mgilbert@mvista.com>
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: [PATCH] Custom IORESOURCE Class
Date: Mon, 8 Aug 2005 23:17:14 +0000 [thread overview]
Message-ID: <20050808231714.GB7276@neo.rr.com> (raw)
In-Reply-To: <20050808160021.GB7481@kroah.com>
On Mon, Aug 08, 2005 at 09:00:21AM -0700, Greg KH wrote:
> On Mon, Aug 08, 2005 at 11:11:45AM -0700, Matthew Gilbert wrote:
> > Below is a patch that adds an additional resource class to the platform
> > resource types. This is to support additional resources that need to be passed
> > to drivers without overloading the existing specific types. In my case, I need
> > to send clock information to the driver to enable power management.
> >
> > Signed-off-by: Matthew Gilbert <mgilbert@mvista.com>
>
> Hm, you do realize that Pat's no longer the driver core maintainer? :)
>
> Anyway, Russell and Adam, any objections to this patch?
I'm not sure if I agree with this patch. "struct resource" is used primarily for
I/O resource assignment. Although I agree we may need to add new IORESOURCE types,
I'm not sure if clock data belongs here. I don't think "start" and "end" would be
useful for most platform data. Could you provide more information about this
specific issue and resource type? Maybe we could create a new sysfs attribute?
Thanks,
Adam
next prev parent reply other threads:[~2005-08-09 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 18:11 [PATCH] Custom IORESOURCE Class Matthew Gilbert
2005-08-08 16:00 ` Greg KH
2005-08-08 23:17 ` Adam Belay [this message]
2005-08-09 4:23 ` Kumar Gala
2005-08-09 23:24 ` Matthew Gilbert
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=20050808231714.GB7276@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgilbert@mvista.com \
--cc=mochel@digitalimplant.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.