All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [RFC 0/2] Proposal for enabling CMEM
Date: Thu, 14 May 2015 18:21:51 -0400	[thread overview]
Message-ID: <20150514222151.GJ30969@edge> (raw)
In-Reply-To: <55436D5E.8000900@ti.com>

On Fri, May 01, 2015 at 08:11:10AM -0400, Jacob Stiffler wrote:
> 
> 
> On 4/23/2015 4:15 PM, Denys Dmytriyenko wrote:
> >On Thu, Apr 23, 2015 at 07:42:09AM -0400, Jacob Stiffler wrote:
> >>This is a proposal for adding a CMEM region in the device tree.
> >>
> >>I wanted to get comments on the following:
> >>
> >>* implementation of using an inc file to enable this.
> >>* Whether the actual configuration belongs in the kernel recipe, or if
> >>   this is something that should be handled at the distro or branding
> >>   level. (RFC sets the configuration in kernel recipe).
> >>     - I have verified that this configuration may also be set in the
> >>        branding file using, for example,
> >>
> >>          CMEM_BASE_pn-linux-ti-staging_omap-a15 = "a0000000"
> >>          CMEM_SIZE_pn-linux-ti-staging_omap-a15 = "20000000"
> >Hmm, on one hand I don't like this change being so invasive. But on the other
> >hand, I'm not sure there's a better cleaner way to do a dts injection like
> >that. Let me think about it...
> 
> Any thoughts on this yet?

Jake,

After discussing this matter internally, since cmem is something that LCPD 
currently doesn't support being an out-of-tree module and so on, I can accept 
the patchset, but it will be disabled by default and not tested by us. All the 
testing will be on you to make sure it's not broken by future changes in the 
kernel. Will that be sufficient?

-- 
Denys


> >>Jacob Stiffler (2):
> >>   linux/cmem.inc: Support reserving memory for CMEM.
> >>   linux-ti-staging_3.14: Add CMEM region for omap-a15.
> >>
> >>  recipes-kernel/linux/cmem.inc                 |   22 ++++++++++++++++++++++
> >>  recipes-kernel/linux/linux-ti-staging_3.14.bb |    6 +++++-
> >>  recipes-kernel/linux/linux/cmem.dtsi          |   24 ++++++++++++++++++++++++
> >>  3 files changed, 51 insertions(+), 1 deletion(-)
> >>  create mode 100644 recipes-kernel/linux/cmem.inc
> >>  create mode 100644 recipes-kernel/linux/linux/cmem.dtsi
> >>
> >>-- 
> >>1.7.9.5
> >>
> >>-- 
> >>_______________________________________________
> >>meta-ti mailing list
> >>meta-ti@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/meta-ti
> 


  reply	other threads:[~2015-05-14 22:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 11:42 [RFC 0/2] Proposal for enabling CMEM Jacob Stiffler
2015-04-23 11:42 ` [RFC 1/2] linux/cmem.inc: Support reserving memory for CMEM Jacob Stiffler
2015-04-23 11:42 ` [RFC 2/2] linux-ti-staging_3.14: Add CMEM region for omap-a15 Jacob Stiffler
2015-04-23 20:15 ` [RFC 0/2] Proposal for enabling CMEM Denys Dmytriyenko
2015-05-01 12:11   ` Jacob Stiffler
2015-05-14 22:21     ` Denys Dmytriyenko [this message]
2015-05-15 18:16       ` Jacob Stiffler
2015-05-15 18:33         ` Denys Dmytriyenko
2015-05-15 18:47           ` Jacob Stiffler

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=20150514222151.GJ30969@edge \
    --to=denys@ti.com \
    --cc=j-stiffler@ti.com \
    --cc=meta-ti@yoctoproject.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 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.