From: Nishanth Menon <nm@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Le Jin <le.jin@siemens.com>,
Bao Cheng Su <baocheng.su@siemens.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v4 3/3] arm64: dts: ti: Add support for Siemens IOT2050 boards
Date: Thu, 11 Mar 2021 08:21:51 -0600 [thread overview]
Message-ID: <20210311142151.5o54k7kmrnatufcw@target> (raw)
In-Reply-To: <519ae6b7-35db-1fdd-de1e-e0155e0ca82a@siemens.com>
On 15:14-20210311, Jan Kiszka wrote:
[...]
> >
> > See [1] compare the compatibles against
> > Documentation/devicetree/bindings -> I think you should describe what
> > your hardware really is though.
>
> This SPI bus is routed to an Arduino connector. By default, userspace
> (e.g. mraa) takes ownership and adds the desired logic for what is being
> connected. We have no idea what shield or other extension the user adds,
> though.
overlays look like the right approach for variable systems like these.
It is not exactly plug and play.. but it does provide a level of
flexibility that is helpful.
[..]
> The problem here is not simple txt->yml conversion: There is no official
> binding for spidev yet, just existing users and the driver waiting for them.
>
I think we should discuss in the spidev list to get it resolved.
> > Thanks.. While it might help me personally to get some on my internal
> > farm, it might be good to get them on kernelci as well on the longer
> > run.
> >
>
> Will keep that on the radar. I definitely want to get it into the CIP
> LAVA lab which is testing LTS as well.
Cool.
> Are we talking about spidev here? Then let's drop that node, but I do
> need to know how to describe spidev properly
yes - the spidev is my problem. can you drop the node and repost? i cant
locally modify and hope it works.
>
> Or is it about those other warnings coming from your dtsi files, now
> being surfaced? If you can tell me how to resolve them, I can write patches.
I will look at the warnings later today.. I dont think they are
triggered by the board dts.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2021-03-11 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 9:37 [PATCH v4 0/3] arm64: Add TI AM65x-based IOT2050 boards Jan Kiszka
2021-03-10 9:37 ` [PATCH v4 1/3] dt-bindings: Add Siemens vendor prefix Jan Kiszka
2021-03-10 9:37 ` [PATCH v4 2/3] dt-bindings: arm: ti: Add bindings for Siemens IOT2050 boards Jan Kiszka
2021-03-10 9:37 ` [PATCH v4 3/3] arm64: dts: ti: Add support " Jan Kiszka
2021-03-11 13:17 ` Nishanth Menon
2021-03-11 13:44 ` Jan Kiszka
2021-03-11 14:00 ` Nishanth Menon
2021-03-11 14:14 ` Jan Kiszka
2021-03-11 14:21 ` Nishanth Menon [this message]
2021-03-11 14:36 ` Jan Kiszka
2021-03-11 17:56 ` Nishanth Menon
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=20210311142151.5o54k7kmrnatufcw@target \
--to=nm@ti.com \
--cc=baocheng.su@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=le.jin@siemens.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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: 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;
as well as URLs for NNTP newsgroup(s).