From: Adrian Fiergolski <adrian.fiergolski@fastree3d.com>
To: Mark Brown <broonie@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Lukas Wunner <lukas@wunner.de>, Rob Herring <robh+dt@kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: Add documentation for SPI daisy chain driver.
Date: Tue, 7 Jul 2020 11:55:48 +0200 [thread overview]
Message-ID: <853fa4a4-ce2f-0503-2fe7-7b34b352b6e2@fastree3d.com> (raw)
In-Reply-To: <20200706162246.GC6176@sirena.org.uk>
Hi Geert and Mark,
Thank you for your comments. I will try to address them in the next replies.
On 06.07.2020 18:22, Mark Brown wrote:
> On Mon, Jul 06, 2020 at 05:32:51PM +0200, Geert Uytterhoeven wrote:
>
>> However, that information would need to be added to each driver only once.
>> With your proposal, it has to be added to all affected nodes of all DTSes
>> of all users.
> Right, these are fixed properties of the silicon which we know simply
> from knowing which device we have - there is no need to put them in DT
> at all.
I see. I agree with you. My concern was just the lack of compatibility
with the existing drivers. I will try to add daisy_chain information to
spi_driver struct in version v3 of the patch.
next prev parent reply other threads:[~2020-07-07 9:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 14:12 [PATCH 1/2] spi: Add the SPI daisy chain support Adrian Fiergolski
2020-07-03 14:12 ` [PATCH 2/2] dt-bindings: Add documentation for SPI daisy chain driver Adrian Fiergolski
2020-07-03 22:32 ` [PATCH 1/2] spi: Add the SPI daisy chain support kernel test robot
2020-07-03 22:32 ` kernel test robot
2020-07-04 0:18 ` kernel test robot
2020-07-04 0:18 ` kernel test robot
2020-07-06 9:22 ` [PATCH v2 " Adrian Fiergolski
2020-07-06 9:22 ` [PATCH v2 2/2] dt-bindings: Add documentation for SPI daisy chain driver Adrian Fiergolski
2020-07-06 15:10 ` Geert Uytterhoeven
2020-07-06 15:19 ` Adrian Fiergolski
2020-07-06 15:32 ` Geert Uytterhoeven
2020-07-06 16:22 ` Mark Brown
2020-07-07 9:55 ` Adrian Fiergolski [this message]
2020-07-06 16:18 ` [PATCH v2 1/2] spi: Add the SPI daisy chain support Mark Brown
2020-07-06 19:57 ` Geert Uytterhoeven
2020-07-07 10:25 ` Mark Brown
2020-07-07 11:06 ` Adrian Fiergolski
2020-07-07 10:53 ` Adrian Fiergolski
2020-07-07 11:21 ` Mark Brown
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=853fa4a4-ce2f-0503-2fe7-7b34b352b6e2@fastree3d.com \
--to=adrian.fiergolski@fastree3d.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=robh+dt@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 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.