From: Jan Kiszka <jan.kiszka@siemens.com>
To: Aswath Govindraju <a-govindraju@ti.com>, Nishanth Menon <nm@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Tero Kristo <kristo@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Lokesh Vutla <lokeshvutla@ti.com>, Faiz Abbas <faiz_abbas@ti.com>
Subject: Re: [PATCH v2 0/6] CAN: Add support for CAN in AM65,J721e and AM64
Date: Thu, 5 Aug 2021 14:40:07 +0200 [thread overview]
Message-ID: <35b0e2dc-0591-0a2f-8e3d-4177792a13fa@siemens.com> (raw)
In-Reply-To: <36011cee-f617-02ed-7446-c297ba65e6bf@ti.com>
On 05.08.21 14:32, Aswath Govindraju wrote:
> Hi,
>
> On 02/08/21 6:15 pm, Nishanth Menon wrote:
>> On 15:40-20210726, Aswath Govindraju wrote:
>>> The following series of patches add support for CAN in SoC's AM65, J721e
>>> and AM64.
>>>
>>> This patch series is dependent on [1] and [2] and I have requested for an
>>> immutable tag from the Marc Kleine-Budde(maintainer of net tree).
>>>
>>> [1] - https://lore.kernel.org/patchwork/patch/1423048/
>>> [2] - https://www.spinics.net/lists/linux-can/msg08108.html
>>>
>>> changes since v1 -
>>> - changed the message ram configuration to use the maximum value
>>> in each field, for better performance.
>>>
>>> Aswath Govindraju (3):
>>> arm64: dts: ti: am654-base-board: Disable mcan nodes
>>> arm64: dts: ti: k3-am64-main: Add support for MCAN
>>> arm64: dts: ti: k3-am642-evm/sk: Add support for main domain mcan
>>> nodes in EVM and disable them on SK
>>>
>>> Faiz Abbas (3):
>>> arm64: dts: ti: k3-am65-mcu: Add Support for MCAN
>>> arm64: dts: ti: k3-j721e: Add support for MCAN nodes
>>> arm64: dts: ti: k3-j721e-common-proc-board: Add support for mcu_mcan
>>> nodes
>>
>> I noticed in my checkup: https://pastebin.ubuntu.com/p/zSk39M943N/
>> warnings with dtbs_check, I think the bindings need a little more help
>> here (please also notice the iot platform warnings getting introduced).
>>
>
> Jan,
>
> Can you please point me to the schematics for iot platform? Also, is CAN
> subsystem brought out on the iot platform boards?
Schematics aren't publicly available. If you have specific questions, I
may help, though.
CAN is not in use yet (not connected AFAIK).
Jan
>
>> Since we are still working on the bindings[1], lets clean that up
>> before we consider the dts addition. I suspect we need to cook this
>> more towards the next cycle.
>>
>> [1] https://lore.kernel.org/patchwork/patch/1470806/
>>
>
> Nishanth,
>
> Sorry for not taking of this earlier. I'll try to get everything ready
> for next release.
>
> Thanks,
> Aswath
>
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-08-05 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 10:10 Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 1/6] arm64: dts: ti: k3-am65-mcu: Add Support for MCAN Aswath Govindraju
2021-08-02 12:59 ` Marc Kleine-Budde
2021-07-26 10:10 ` [PATCH v2 2/6] arm64: dts: ti: am654-base-board: Disable mcan nodes Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 3/6] arm64: dts: ti: k3-j721e: Add support for MCAN nodes Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 4/6] arm64: dts: ti: k3-j721e-common-proc-board: Add support for mcu_mcan nodes Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 5/6] arm64: dts: ti: k3-am64-main: Add support for MCAN Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 6/6] arm64: dts: ti: k3-am642-evm/sk: Add support for main domain mcan nodes in EVM and disable them on SK Aswath Govindraju
2021-07-28 5:19 ` [PATCH v2 0/6] CAN: Add support for CAN in AM65,J721e and AM64 Aswath Govindraju
2021-07-28 7:26 ` Marc Kleine-Budde
2021-08-02 12:45 ` Nishanth Menon
2021-08-05 12:32 ` Aswath Govindraju
2021-08-05 12:40 ` Jan Kiszka [this message]
2021-08-05 12:44 ` Aswath Govindraju
2021-08-05 12:49 ` Jan Kiszka
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=35b0e2dc-0591-0a2f-8e3d-4177792a13fa@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mkl@pengutronix.de \
--cc=nm@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®