From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Daniel Scally <dan.scally@ideasonboard.com>,
krzysztof.kozlowski@linaro.org, shawnguo@kernel.org,
robh@kernel.org, marcel.ziswiler@toradex.com, leoyang.li@nxp.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
s.hauer@pengutronix.de, debix-tech@polyhex.net,
linux-imx@nxp.com, kernel@pengutronix.de, festevam@gmail.com
Subject: Re: [PATCH v2 0/3] Debix Model A board devicetree
Date: Wed, 12 Oct 2022 11:22:02 +0100 [thread overview]
Message-ID: <166557012258.3760285.1911550181545000867@Monstersaurus> (raw)
In-Reply-To: <20221011064316.dv6ulnmdginr7p3y@pengutronix.de>
Quoting Marc Kleine-Budde (2022-10-11 07:43:16)
> On 10.10.2022 16:57:37, Laurent Pinchart wrote:
> > > > This series adds a .dts file for the Polyhex Debix Model A board [1]
> > > > A binding for the vendor is also added.
> > >
> > > A bit off-topic, how cooperative is Polyhex when it comes to the
> > > datasheets of the board and the expansion boards?
> >
> > There is public documentation, including reduced schematics that provide
> > just the pinout of the connectors. When it comes to availability of
> > non-public documentation to selected upstream developers, I'll let
> > Polyhex answer that question. More detailed schematics would certainly
> > be useful to develop and review the upstream device tree integration for
> > the board.
>
> Thanks, I've found the "reduced" schematics. Do you have a direct
> contact to ask for more detailed schematics (e.g. for the IO board)?
There's a discord channel/server at https://discord.gg/adaHHaDkH2
and debix-tech@polyhex.net, already on Cc of this mail thread.
--
Kieran
>
> regards,
> Marc
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Embedded Linux | https://www.pengutronix.de |
> Vertretung West/Dortmund | Phone: +49-231-2826-924 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-12 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 13:31 [PATCH v2 0/3] Debix Model A board devicetree Daniel Scally
2022-10-10 13:31 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Polyhex Technology Co Daniel Scally
2022-10-10 13:31 ` [PATCH v2 2/3] dt-bindings: arm: fsl: Enumerate Debix Model A Board Daniel Scally
2022-10-10 13:56 ` Kieran Bingham
2022-10-10 13:57 ` Dan Scally
2022-10-10 14:06 ` Laurent Pinchart
2022-10-10 13:31 ` [PATCH v2 3/3] arm64: dts: Add device tree for the " Daniel Scally
2022-10-10 14:18 ` Laurent Pinchart
2022-10-10 13:49 ` [PATCH v2 0/3] Debix Model A board devicetree Marc Kleine-Budde
2022-10-10 13:57 ` Laurent Pinchart
2022-10-11 6:43 ` Marc Kleine-Budde
2022-10-12 10:22 ` Kieran Bingham [this message]
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=166557012258.3760285.1911550181545000867@Monstersaurus \
--to=kieran.bingham@ideasonboard.com \
--cc=dan.scally@ideasonboard.com \
--cc=debix-tech@polyhex.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).