public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Juha Yrjölä" <juha.yrjola@solidboot.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: Add minimal OMAP2430 support
Date: Sun, 11 Jun 2006 16:54:23 +0300	[thread overview]
Message-ID: <448C208F.4020102@solidboot.com> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A506200337@dlee02.ent.ti.com>

Woodruff, Richard wrote:

> Along with my other biases I rationalized it this way... I like
> having  a private driver incompatible method to access the PRCM. It forces
> drivers to use API access functions and not directly access its
> registers. The PRCM has more and more things to manage and having some
> xyz driver mess up its state behind my back will break everything.

Exactly.  That's why I keep my read_reg/write_reg functions static. 
Usually I put even the register definitions to the .c file, since other 
drivers shouldn't have any business modifying them directly anyway.

Cheers,
Juha

  reply	other threads:[~2006-06-11 13:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11 13:22 [PATCH] ARM: OMAP: Add minimal OMAP2430 support Woodruff, Richard
2006-06-11 13:54 ` Juha Yrjölä [this message]
2006-06-12  6:43   ` Komal Shah
2006-06-12 16:07     ` Tony Lindgren
2006-06-12 16:35       ` Komal Shah
  -- strict thread matches above, loose matches on Subject: below --
2006-06-11 13:09 Woodruff, Richard
2006-06-11 12:15 Woodruff, Richard
2006-06-11 12:50 ` Juha Yrjölä
2006-05-21 13:50 Woodruff, Richard
2006-05-18 12:30 Woodruff, Richard
2006-05-21 12:23 ` Komal Shah
2006-05-18 11:44 Komal Shah
2006-06-05 16:54 ` Tony Lindgren
2006-06-06  3:08   ` Komal Shah
2006-06-06 17:58     ` Tony Lindgren
2006-06-11  8:37       ` Komal Shah
2006-06-11 10:08         ` Juha Yrjölä
2006-05-17 10:50 Komal Shah

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=448C208F.4020102@solidboot.com \
    --to=juha.yrjola@solidboot.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=r-woodruff2@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox