From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> To: Olivier MOYSAN <olivier.moysan-qxv4g6HH51o@public.gmane.org> Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, "lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, "perex-/Fr2/VpizcU@public.gmane.org" <perex-/Fr2/VpizcU@public.gmane.org>, "tiwai-IBi9RG/b67k@public.gmane.org" <tiwai-IBi9RG/b67k@public.gmane.org>, "mcoquelin.stm32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <mcoquelin.stm32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Alexandre TORGUE <alexandre.torgue-qxv4g6HH51o@public.gmane.org>, "alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org" <alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org>, "mark.rutland-5wv7dgnIgG8@public.gmane.org" <mark.rutland-5wv7dgnIgG8@public.gmane.org>, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>, Arnaud POULIQUEN <arnaud.pouliquen-qxv4g6HH51o@public.gmane.org>, Benjamin GAIGNARD <benjamin.gaignard-qxv4g6HH51o@public.gmane.org> Subject: Re: [PATCH 1/2] dt-bindings: Document STM32 I2S bindings Date: Wed, 12 Apr 2017 12:32:51 +0100 [thread overview] Message-ID: <20170412113251.nfyk5sw6c5pnpmwr@sirena.org.uk> (raw) In-Reply-To: <86a179ad-7961-18f7-8050-25e0e584c77d-qxv4g6HH51o@public.gmane.org> [-- Attachment #1: Type: text/plain, Size: 930 bytes --] On Wed, Apr 12, 2017 at 08:30:31AM +0000, Olivier MOYSAN wrote: > On 04/11/2017 11:10 PM, Mark Brown wrote: > > That sounds wrong, I'd expect this wiring to be done statically as part > > of the .dtsi for the SoC (or just grabbed as needed at runtime if > > things are flexbile enough) rather than being a configuration thing done > > per board... I had thought that this was configuration reflecting > > different ways of taping out the IP with different feature sets, is that > > not the case? > This configuration is board dependent. The IP may be used as rx, tx or > fd depending on board. So I think it can make sense to have a DMA > configuration linked to board, and to set IP mode accordingly. It is totally normal to just not use one direction in a given system, we don't normally need to do anything special to handle things. I'm a bit confused as to what's different here and needs configuring? [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/2] dt-bindings: Document STM32 I2S bindings Date: Wed, 12 Apr 2017 12:32:51 +0100 [thread overview] Message-ID: <20170412113251.nfyk5sw6c5pnpmwr@sirena.org.uk> (raw) In-Reply-To: <86a179ad-7961-18f7-8050-25e0e584c77d@st.com> On Wed, Apr 12, 2017 at 08:30:31AM +0000, Olivier MOYSAN wrote: > On 04/11/2017 11:10 PM, Mark Brown wrote: > > That sounds wrong, I'd expect this wiring to be done statically as part > > of the .dtsi for the SoC (or just grabbed as needed at runtime if > > things are flexbile enough) rather than being a configuration thing done > > per board... I had thought that this was configuration reflecting > > different ways of taping out the IP with different feature sets, is that > > not the case? > This configuration is board dependent. The IP may be used as rx, tx or > fd depending on board. So I think it can make sense to have a DMA > configuration linked to board, and to set IP mode accordingly. It is totally normal to just not use one direction in a given system, we don't normally need to do anything special to handle things. I'm a bit confused as to what's different here and needs configuring? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170412/7caea188/attachment.sig>
next prev parent reply other threads:[~2017-04-12 11:32 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-06 15:40 [PATCH 0/2] ASoC: stm32: Add I2S driver olivier moysan 2017-04-06 15:40 ` olivier moysan 2017-04-06 15:40 ` [PATCH 1/2] dt-bindings: Document STM32 I2S bindings olivier moysan 2017-04-06 15:40 ` olivier moysan 2017-04-10 19:48 ` Rob Herring 2017-04-10 19:48 ` Rob Herring 2017-04-11 14:32 ` Mark Brown 2017-04-11 14:32 ` Mark Brown 2017-04-11 15:44 ` Olivier MOYSAN 2017-04-11 15:44 ` Olivier MOYSAN 2017-04-11 21:10 ` Mark Brown 2017-04-11 21:10 ` Mark Brown 2017-04-12 8:30 ` Olivier MOYSAN 2017-04-12 8:30 ` Olivier MOYSAN [not found] ` <86a179ad-7961-18f7-8050-25e0e584c77d-qxv4g6HH51o@public.gmane.org> 2017-04-12 11:32 ` Mark Brown [this message] 2017-04-12 11:32 ` Mark Brown 2017-04-12 12:58 ` Olivier MOYSAN 2017-04-12 12:58 ` Olivier MOYSAN [not found] ` <d886a9c7-ca46-f37a-0e82-6ed8d7a4e052-qxv4g6HH51o@public.gmane.org> 2017-04-12 15:38 ` Mark Brown 2017-04-12 15:38 ` Mark Brown 2017-04-13 8:01 ` Olivier MOYSAN 2017-04-13 8:01 ` Olivier MOYSAN 2017-04-26 16:15 ` Mark Brown 2017-04-26 16:15 ` Mark Brown 2017-04-27 15:57 ` Olivier MOYSAN 2017-04-27 15:57 ` Olivier MOYSAN [not found] ` <20170411143250.3r7ys3rjshtxgaee-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> 2017-04-11 16:02 ` Rob Herring 2017-04-11 16:02 ` Rob Herring 2017-04-11 20:19 ` Mark Brown 2017-04-11 20:19 ` Mark Brown [not found] ` <1491493236-2574-1-git-send-email-olivier.moysan-qxv4g6HH51o@public.gmane.org> 2017-04-06 15:40 ` [PATCH 2/2] ASoC: stm32: Add I2S driver olivier moysan 2017-04-06 15:40 ` olivier moysan
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=20170412113251.nfyk5sw6c5pnpmwr@sirena.org.uk \ --to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \ --cc=alexandre.torgue-qxv4g6HH51o@public.gmane.org \ --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \ --cc=arnaud.pouliquen-qxv4g6HH51o@public.gmane.org \ --cc=benjamin.gaignard-qxv4g6HH51o@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \ --cc=mcoquelin.stm32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=olivier.moysan-qxv4g6HH51o@public.gmane.org \ --cc=perex-/Fr2/VpizcU@public.gmane.org \ --cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=tiwai-IBi9RG/b67k@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: linkBe 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.