From: Tony Lindgren <tony@atomide.com>
To: "Enric Balletbò i Serra" <eballetbo@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-arm@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@nokia.com>
Subject: Re: [RFC] About ARM expansion boards and others things
Date: Wed, 4 May 2011 02:27:08 -0700 [thread overview]
Message-ID: <20110504092708.GX2092@atomide.com> (raw)
In-Reply-To: <BANLkTimjWtqLsWA1Gthix6RZYMzNRdC7rg@mail.gmail.com>
* Enric Balletbò i Serra <eballetbo@gmail.com> [110503 10:21]:
>
> Basically I wonder if it's possible add another omap_dss_device from
> kernel module to the omap DSS driver (something like
> omap_dss_register_new_device). Is a good or bad idea ? Why ? Is any
> reason to not export the MUX functionality to be used for other
> drivers ?
Sounds all doable. For DSS, I think the memblock needs to be reserved
early.
With the mux framework, we have a Linux generic mux framework coming
up, that should allow you to access the pins from the driver module
too.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-04 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 17:25 [RFC] About ARM expansion boards and others things Enric Balletbò i Serra
2011-05-04 9:27 ` Tony Lindgren [this message]
2011-05-04 10:28 ` Vladimir Pantelic
2011-05-04 10:46 ` Enric Balletbò i Serra
2011-05-04 11:44 ` Koen Kooi
2011-05-04 10:53 ` Igor Grinberg
2011-05-04 11:20 ` Igor Grinberg
2011-05-04 11:20 ` Igor Grinberg
2011-05-04 12:28 ` Enric Balletbò i Serra
2011-05-04 13:17 ` Igor Grinberg
2011-05-04 13:17 ` Igor Grinberg
2011-05-04 11:50 ` Tomi Valkeinen
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=20110504092708.GX2092@atomide.com \
--to=tony@atomide.com \
--cc=eballetbo@gmail.com \
--cc=linux-arm@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.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 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.