From: Mark Brown <broonie@kernel.org> To: Justin Swartz <justin.swartz@risingedge.co.za> Cc: Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH] spi: mt7621: allow GPIO chip select lines Date: Fri, 15 Mar 2024 17:47:17 +0000 [thread overview] Message-ID: <6c92fddd-f79b-40b5-bd52-61f43d6a7591@sirena.org.uk> (raw) In-Reply-To: <2dbc59c9133542f6f8bc465113d9630b@risingedge.co.za> [-- Attachment #1: Type: text/plain, Size: 1447 bytes --] On Fri, Mar 15, 2024 at 06:23:09PM +0200, Justin Swartz wrote: > On 2024-03-15 16:45, Mark Brown wrote: > > The core should handle GPIO chip selects for you? > As far as I can tell, it doesn't - at least as far the state > of spi-mt7621.c is concerned prior to the patch, plus kernel > configuration choices, device tree definition, and other > factors I might not be taking into account. > But maybe I'm doing something wrong, or perhaps have a > misconfiguration somewhere. So, if you're able to point out > something I've done incorrectly, it would be appreciated. Look at other drivers that support GPIO chip selects? > To attempt to confirm if the core will handle my desired > GPIO chip select lines without explicit state toggling, > I tried to set the value of use_gpio_descriptors to true, > without any other modifications to spi-mt7621.c as of > commit 90d35da658da8cff0d4ecbb5113f5fac9d00eb72: Please include human readable descriptions of things like commits and issues being discussed in e-mail in your mails, this makes them much easier for humans to read especially when they have no internet access. I do frequently catch up on my mail on flights or while otherwise travelling so this is even more pressing for me than just being about making things a bit easier to read. The core needs to know that the GPIO chip selects are there but once it knows that they're there things like setting the chip select should just work. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Justin Swartz <justin.swartz@risingedge.co.za> Cc: Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH] spi: mt7621: allow GPIO chip select lines Date: Fri, 15 Mar 2024 17:47:17 +0000 [thread overview] Message-ID: <6c92fddd-f79b-40b5-bd52-61f43d6a7591@sirena.org.uk> (raw) In-Reply-To: <2dbc59c9133542f6f8bc465113d9630b@risingedge.co.za> [-- Attachment #1.1: Type: text/plain, Size: 1447 bytes --] On Fri, Mar 15, 2024 at 06:23:09PM +0200, Justin Swartz wrote: > On 2024-03-15 16:45, Mark Brown wrote: > > The core should handle GPIO chip selects for you? > As far as I can tell, it doesn't - at least as far the state > of spi-mt7621.c is concerned prior to the patch, plus kernel > configuration choices, device tree definition, and other > factors I might not be taking into account. > But maybe I'm doing something wrong, or perhaps have a > misconfiguration somewhere. So, if you're able to point out > something I've done incorrectly, it would be appreciated. Look at other drivers that support GPIO chip selects? > To attempt to confirm if the core will handle my desired > GPIO chip select lines without explicit state toggling, > I tried to set the value of use_gpio_descriptors to true, > without any other modifications to spi-mt7621.c as of > commit 90d35da658da8cff0d4ecbb5113f5fac9d00eb72: Please include human readable descriptions of things like commits and issues being discussed in e-mail in your mails, this makes them much easier for humans to read especially when they have no internet access. I do frequently catch up on my mail on flights or while otherwise travelling so this is even more pressing for me than just being about making things a bit easier to read. The core needs to know that the GPIO chip selects are there but once it knows that they're there things like setting the chip select should just work. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 176 bytes --] _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-15 17:47 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-15 1:57 [PATCH] spi: mt7621: allow GPIO chip select lines Justin Swartz 2024-03-15 1:57 ` Justin Swartz 2024-03-15 14:45 ` Mark Brown 2024-03-15 14:45 ` Mark Brown 2024-03-15 16:23 ` Justin Swartz 2024-03-15 16:23 ` Justin Swartz 2024-03-15 17:47 ` Mark Brown [this message] 2024-03-15 17:47 ` Mark Brown 2024-03-15 20:21 ` Justin Swartz 2024-03-15 20:21 ` Justin Swartz 2024-03-15 20:41 ` Mark Brown 2024-03-15 20:41 ` Mark Brown 2024-03-16 1:03 ` [PATCH v2] " Justin Swartz 2024-03-16 1:03 ` Justin Swartz 2024-03-18 10:16 ` AngeloGioacchino Del Regno 2024-03-18 10:16 ` AngeloGioacchino Del Regno 2024-03-18 11:06 ` Justin Swartz 2024-03-18 11:06 ` Justin Swartz 2024-03-25 17:44 ` Mark Brown 2024-03-25 17:44 ` Mark Brown 2024-03-16 0:59 [PATCH] " Justin Swartz 2024-03-16 0:59 ` Justin Swartz 2024-03-16 1:01 ` Justin Swartz 2024-03-16 1:01 ` Justin Swartz 2024-03-16 1:11 ` Mark Brown 2024-03-16 1:11 ` Mark Brown 2024-03-16 1:15 ` Justin Swartz 2024-03-16 1:15 ` Justin Swartz
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=6c92fddd-f79b-40b5-bd52-61f43d6a7591@sirena.org.uk \ --to=broonie@kernel.org \ --cc=angelogioacchino.delregno@collabora.com \ --cc=justin.swartz@risingedge.co.za \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=linux-spi@vger.kernel.org \ --cc=matthias.bgg@gmail.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: 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.