mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: "Lars-Peter Clausen" <lars@metafoo.de>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	drivers@analog.com, stable@kernel.org
Subject: Re: [PATCH 4/8] firmware: Sigma: Mark firmware strutcs packed
Date: Fri, 25 Nov 2011 15:07:09 -0500	[thread overview]
Message-ID: <201111251507.11404.vapier@gentoo.org> (raw)
In-Reply-To: <4ECF7274.2020502@metafoo.de>

[-- Attachment #1: Type: Text/Plain, Size: 1413 bytes --]

On Friday 25 November 2011 05:48:20 Lars-Peter Clausen wrote:
> On 11/24/2011 06:19 PM, Mike Frysinger wrote:
> > On Thursday 24 November 2011 07:48:23 Lars-Peter Clausen wrote:
> >> Mark structs which are embedded into the firmware as packed to avoid
> >> alignment issues.
> > 
> > while in general this makes sense, i designed the struct layout
> > specifically to work on any sane system.  that means 8bits align on
> > 8bits, 16bits align on 16bits, and 32bits align on 32bits.
> > 
> > do you see any place where this is not the case ?  otherwise, using
> > __packed by itself doesn't make much sense unless you also change all
> > the loads from the struct to the get_unaligned variety which would add
> > useless overhead to many embedded parts.
> > 
> > all in all, i'd omit the __packed markings since they're unnecessary.
> 
> While you are right I think it's generally a good idea to mark anything as
> packed, where we don't have direct influence on the alignment, to avoid
> unpleasant suppresses.

don't we though ?  the ADI peeps writing the driver code work directly with 
the ADI sigmadsp peeps for the firmware needs.  so as long as we make sure the 
layout stays sane, then it stays sane ... otherwise, we need to be vigilant to 
make sure people don't go slipping in useless get_unaligned calls to the code.  
if they see "__packed", they think it's correct.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-11-25 20:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 12:48 [PATCH 1/8] firmware: Sigma: Prevent out of bounds memory access Lars-Peter Clausen
2011-11-24 12:48 ` [PATCH 2/8] firmware: Sigma: Skip header during CRC generation Lars-Peter Clausen
2011-11-24 17:21   ` Mike Frysinger
2011-11-25  8:55     ` Lars-Peter Clausen
2011-11-25 20:00       ` Mike Frysinger
2011-11-28  7:56         ` Lars-Peter Clausen
2011-11-29  5:11           ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 3/8] firmware: Sigma: Fix endianess issues Lars-Peter Clausen
2011-11-24 17:20   ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 4/8] firmware: Sigma: Mark firmware strutcs packed Lars-Peter Clausen
2011-11-24 17:19   ` Mike Frysinger
2011-11-25 10:48     ` Lars-Peter Clausen
2011-11-25 20:07       ` Mike Frysinger [this message]
2011-11-24 12:48 ` [PATCH 5/8] ASoC: Move SigmaDSP firmware loader to ASoC Lars-Peter Clausen
2011-11-24 13:15   ` [PATCH v2 " Lars-Peter Clausen
2011-11-24 17:31     ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 6/8] ASoC: SigmaDSP: Provide diagnostic error messages Lars-Peter Clausen
2011-11-24 17:32   ` Mike Frysinger
2011-11-25  8:59     ` Lars-Peter Clausen
2011-11-25 20:02       ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 7/8] ASoC: SigmaDSP: Move private structs and functions to c file Lars-Peter Clausen
2011-11-24 17:31   ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 8/8] ASoC: SigmaDSP: Add regmap support Lars-Peter Clausen
2011-11-24 17:30   ` Mike Frysinger
2011-11-25  9:00     ` Lars-Peter Clausen
2011-11-24 17:26 ` [PATCH 1/8] firmware: Sigma: Prevent out of bounds memory access Mike Frysinger

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=201111251507.11404.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=drivers@analog.com \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=stable@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome