From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP: omap_device: Add omap_device_{alloc, delete, register}_ss
Date: Mon, 10 Oct 2011 10:25:01 -0700 [thread overview]
Message-ID: <87hb3giwsy.fsf@ti.com> (raw)
In-Reply-To: <CAK=WgbbqG4qFAafJ49jdYwf19whxBGhtywTWVTnsejZ0F_ekog@mail.gmail.com> (Ohad Ben-Cohen's message of "Mon, 10 Oct 2011 09:37:08 +0200")
Ohad Ben-Cohen <ohad@wizery•com> writes:
> Hi Kevin,
>
> On Wed, Oct 5, 2011 at 6:54 PM, Ohad Ben-Cohen <ohad@wizery•com> wrote:
>> Split omap_device_build_ss() into two smaller functions:
> ...
>> This patch is considered an interim solution until DT fully materializes
>> for omap; at that point, this functionality will be removed.
>
> Good news: we might not need this after all.
Great.
> I need the remoteproc devices to exists at ->reserve() time, so I can
> assign them a private CMA pool, which means I can't wait for
> omap_device_build_ss() and must create the devices beforehand.
>
> ... which makes Benoit's alloc/delete methods perfect for me.
>
> So please hold this one off for now. I'd just need a s/static// patch
> that will allow me to use Benoit's methods outside of omap_device.c,
> but I'll wait for things to settle down a bit before sending it, to
> minimize this kind of churn.
OK. Sounds good.
Thanks,
Kevin
> Thanks and sorry for the noise,
> Ohad.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-10-10 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 16:54 [PATCH] ARM: OMAP: omap_device: Add omap_device_{alloc, delete, register}_ss Ohad Ben-Cohen
2011-10-10 7:37 ` Ohad Ben-Cohen
2011-10-10 17:25 ` Kevin Hilman [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=87hb3giwsy.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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