All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Hollis Blanchard
	<hollis_blanchard-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
Cc: Meador Inge <meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>,
	Wood Scott-B07421
	<B07421-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	"openmcapi-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
	<openmcapi-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	"linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [PATCH 2/2] powerpc: add support for MPIC message register API
Date: Tue, 3 May 2011 10:19:21 -0500	[thread overview]
Message-ID: <20110503101921.45f31d34@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <4DBED5E9.2070201-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>

On Mon, 2 May 2011 09:03:53 -0700
Hollis Blanchard <hollis_blanchard-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org> wrote:

> On 05/01/2011 08:41 PM, Kushwaha Prabhakar-B32579 wrote:
> >> Perhaps an allocator could be added in the same patchset that adds such a
> >> user.
> > Yaa. It can be done. Otherwise module has to query each message unit for its availability.
> 
> No, instead the system designer should pick one. If it doesn't matter 
> which one, then the designer is free to pick any.

We should avoid resorting to the notion of a "system designer" if possible
-- it's hard to avoid it when dealing with partitioning, but it shouldn't
be needed for unpartitioned basic driver operation.

> An allocator can't work if you're going to mix drivers. For example, 
> driver A needs MSRG0, and driver B doesn't care. Driver B loads first, 
> the allocator selects MSGR0; driver A loads and fails. Having an 
> allocator at all will create this conflict.

In the absence of partitioning, no driver should need a specific one.  With
partitioning, let the system designer mark those resources as reserved so
they don't get allocated. :-)

-Scott

WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Hollis Blanchard <hollis_blanchard@mentor.com>
Cc: Meador Inge <meador_inge@mentor.com>,
	Wood Scott-B07421 <B07421@freescale.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	Kushwaha Prabhakar-B32579 <B32579@freescale.com>,
	"openmcapi-dev@googlegroups.com" <openmcapi-dev@googlegroups.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] powerpc: add support for MPIC message register API
Date: Tue, 3 May 2011 10:19:21 -0500	[thread overview]
Message-ID: <20110503101921.45f31d34@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <4DBED5E9.2070201@mentor.com>

On Mon, 2 May 2011 09:03:53 -0700
Hollis Blanchard <hollis_blanchard@mentor.com> wrote:

> On 05/01/2011 08:41 PM, Kushwaha Prabhakar-B32579 wrote:
> >> Perhaps an allocator could be added in the same patchset that adds such a
> >> user.
> > Yaa. It can be done. Otherwise module has to query each message unit for its availability.
> 
> No, instead the system designer should pick one. If it doesn't matter 
> which one, then the designer is free to pick any.

We should avoid resorting to the notion of a "system designer" if possible
-- it's hard to avoid it when dealing with partitioning, but it shouldn't
be needed for unpartitioned basic driver operation.

> An allocator can't work if you're going to mix drivers. For example, 
> driver A needs MSRG0, and driver B doesn't care. Driver B loads first, 
> the allocator selects MSGR0; driver A loads and fails. Having an 
> allocator at all will create this conflict.

In the absence of partitioning, no driver should need a specific one.  With
partitioning, let the system designer mark those resources as reserved so
they don't get allocated. :-)

-Scott

  parent reply	other threads:[~2011-05-03 15:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 16:59 [PATCH 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-04-19 16:59 ` Meador Inge
     [not found] ` <1303232375-25014-1-git-send-email-meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2011-04-19 16:59   ` [PATCH 1/2] powerpc: document the FSL MPIC message register binding Meador Inge
2011-04-19 16:59     ` Meador Inge
     [not found]     ` <1303232375-25014-2-git-send-email-meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2011-04-19 17:52       ` Scott Wood
2011-04-19 17:52         ` Scott Wood
2011-04-19 18:26         ` Meador Inge
2011-04-19 18:33           ` Scott Wood
     [not found]             ` <20110419133336.46d8566f-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2011-04-21 19:26               ` Meador Inge
2011-04-21 19:26                 ` Meador Inge
     [not found]                 ` <4DB084F6.4060103-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2011-04-21 19:35                   ` Scott Wood
2011-04-21 19:35                     ` Scott Wood
2011-04-19 16:59   ` [PATCH 2/2] powerpc: add support for MPIC message register API Meador Inge
2011-04-19 16:59     ` Meador Inge
     [not found]     ` <1303232375-25014-3-git-send-email-meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2011-04-29  5:00       ` Kushwaha Prabhakar-B32579
2011-04-29  5:00         ` Kushwaha Prabhakar-B32579
2011-04-29 16:54         ` Hollis Blanchard
2011-04-29 17:27           ` Kushwaha Prabhakar-B32579
2011-04-29 17:27             ` Kushwaha Prabhakar-B32579
     [not found]             ` <071A08F2C6A57E4E94D980ECA553F8741967EC-TcFNo7jSaXM0vywKSws3iq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2011-04-29 17:30               ` Scott Wood
2011-04-29 17:30                 ` Scott Wood
     [not found]                 ` <20110429123051.4ed1ca01-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2011-05-02  3:41                   ` Kushwaha Prabhakar-B32579
2011-05-02  3:41                     ` Kushwaha Prabhakar-B32579
2011-05-02 16:03                     ` Hollis Blanchard
     [not found]                       ` <4DBED5E9.2070201-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2011-05-03 15:19                         ` Scott Wood [this message]
2011-05-03 15:19                           ` Scott Wood
2011-05-05 21:41                           ` Meador Inge
2011-05-06 19:29                             ` Scott Wood
     [not found]                               ` <20110506142937.77e7a10f-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2011-05-06 23:51                                 ` Meador Inge
2011-05-06 23:51                                   ` Meador Inge
2012-02-17  2:49 [PATCH 1/2] powerpc: document the FSL MPIC message register binding Jia Hongtao
2012-02-17  2:49 ` [PATCH 2/2] powerpc: add support for MPIC message register API Jia Hongtao
2012-03-21 17:21   ` Kumar Gala

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=20110503101921.45f31d34@schlenkerla.am.freescale.net \
    --to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
    --cc=B07421-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=hollis_blanchard-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org \
    --cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org \
    --cc=openmcapi-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.