From: Nicolin Chen <Guangyu.Chen@freescale•com>
To: Mark Rutland <mark.rutland@arm•com>
Cc: "devicetree@vger•kernel.org" <devicetree@vger•kernel.org>,
"alsa-devel@alsa-project•org" <alsa-devel@alsa-project•org>,
"b42378@freescale•com" <b42378@freescale•com>,
"timur@tabi•org" <timur@tabi•org>,
Pawel Moll <Pawel.Moll@arm•com>,
"ijc+devicetree@hellion•org.uk" <ijc+devicetree@hellion•org.uk>,
"tiwai@suse•de" <tiwai@suse•de>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"rdunlap@infradead•org" <rdunlap@infradead•org>,
"b02247@freescale•com" <b02247@freescale•com>,
"lgirdwood@gmail•com" <lgirdwood@gmail•com>,
"robh+dt@kernel•org" <robh+dt@kernel•org>,
"perex@perex•cz" <perex@perex•cz>,
Nicolin Chen <nicoleotsuka@gmail•com>,
"broonie@kernel•org" <broonie@kernel•org>,
"galak@codeaurora•org" <galak@codeaurora•org>,
"grant.likely@linaro•org" <grant.likely@linaro•org>,
"tklauser@distanz•ch" <tklauser@distanz•ch>,
"shawn.guo@linaro•org" <shawn.guo@linaro•org>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH v3 2/2] ASoC: fsl_asrc: Add ASRC ASoC CPU DAI and platform drivers
Date: Tue, 29 Jul 2014 18:13:24 +0800 [thread overview]
Message-ID: <20140729101322.GA5495@MrMyself> (raw)
In-Reply-To: <20140729094613.GK2576@leverpostej>
On Tue, Jul 29, 2014 at 10:46:13AM +0100, Mark Rutland wrote:
> > + - big-endian : If this property is absent, the native endian mode will
> > + be in use as default, or the big endian mode will be in use
> > + for all the device registers.
>
> Native endian is meaningless. If a CPU supports both BE and LE, there is
> no native endianness. The endianness of the kernel is dynamic while the
> endianness of registers in HW is fixed.
>
> Just choose an endianness to assume by default (presumably little). That
> way this describes the HW and always works with a kernel of arbitrary
> endianness.
Thank you for the comments.
I just revised it by using 'little endian as default' and sent the patch v6.
Please take a look at the new version.
Thanks again,
Nicolin
prev parent reply other threads:[~2014-07-29 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 4:03 [PATCH v3 0/2] Add Freescale ASRC driver Nicolin Chen
2014-07-25 4:03 ` [PATCH v3 1/2] ARM: imx: Add the secondary request into the structure for imx-sdma Nicolin Chen
2014-07-25 4:03 ` [PATCH v3 2/2] ASoC: fsl_asrc: Add ASRC ASoC CPU DAI and platform drivers Nicolin Chen
2014-07-25 4:24 ` Varka Bhadram
2014-07-25 5:30 ` Nicolin Chen
2014-07-25 5:54 ` Nicolin Chen
2014-07-25 6:17 ` Varka Bhadram
2014-07-25 6:09 ` Nicolin Chen
2014-07-29 9:46 ` Mark Rutland
2014-07-29 10:13 ` Nicolin Chen [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=20140729101322.GA5495@MrMyself \
--to=guangyu.chen@freescale$(echo .)com \
--cc=Pawel.Moll@arm$(echo .)com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=b02247@freescale$(echo .)com \
--cc=b42378@freescale$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=galak@codeaurora$(echo .)org \
--cc=grant.likely@linaro$(echo .)org \
--cc=ijc+devicetree@hellion$(echo .)org.uk \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=nicoleotsuka@gmail$(echo .)com \
--cc=perex@perex$(echo .)cz \
--cc=rdunlap@infradead$(echo .)org \
--cc=robh+dt@kernel$(echo .)org \
--cc=shawn.guo@linaro$(echo .)org \
--cc=timur@tabi$(echo .)org \
--cc=tiwai@suse$(echo .)de \
--cc=tklauser@distanz$(echo .)ch \
/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