public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	imx@lists.linux.dev, Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 2/3] ARM: dts: imx: Add devicetree for Kobo Clara 2E
Date: Tue, 22 Oct 2024 22:05:46 +0100	[thread overview]
Message-ID: <20241022-elongated-chaos-7e47ffcaf073@spud> (raw)
In-Reply-To: <20241022194221.43b9073b@akair>

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

On Tue, Oct 22, 2024 at 07:42:21PM +0200, Andreas Kemnade wrote:
> Am Tue, 22 Oct 2024 17:59:10 +0100
> schrieb Conor Dooley <conor@kernel.org>:
> > On Mon, Oct 21, 2024 at 07:36:30PM +0200, Andreas Kemnade wrote:
> > > +&i2c2 {
> > > +	/* EPD PMIC SY7636 at 0x62 */  
> > 
> > Could you explain what you're doing here, please?
> >
> I am not sure what you are really after with this question...
> So I am guessing a bit.
> I describe the hardware as good as possible. The sy7636a (apparently
> =sy7636) driver could probably be used here but the driver and its
> bindings needs to be extended to specify an input supply and some gpios.
> So at the moment I could not use a machine-readable way of fully
> describe the stuff here. But I want to put a human-readable mark here
> so if someone extends the driver, he/she might be aware that there are
> some possible users and candidates for a Tested-by here.
> For the JD9930 it is even worse. No driver in kernel. I have a pretty
> dirty one requiring some rounds with the brush before sending it.
> So the mark is good for information what is missing and for teaming up.

Your guess was accurate. Please note in the commit message why you're
doing this, so that it's obvious why you've put comments rather than
device nodes in the file. Thanks for explaining.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-10-22 21:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 17:36 [PATCH 0/3] ARM: dts: add Kobo Clara 2E Andreas Kemnade
2024-10-21 17:36 ` [PATCH 1/3] dt-bindings: arm: fsl: add compatible strings for " Andreas Kemnade
2024-10-22 16:59   ` Conor Dooley
2024-10-21 17:36 ` [PATCH 2/3] ARM: dts: imx: Add devicetree " Andreas Kemnade
2024-10-22 16:59   ` Conor Dooley
2024-10-22 17:42     ` Andreas Kemnade
2024-10-22 21:05       ` Conor Dooley [this message]
2024-10-21 17:36 ` [PATCH 3/3] ARM: imx_v6_v7_defconfig: Enable drivers " Andreas Kemnade
2024-10-24 16:33 ` [PATCH 0/3] ARM: dts: add " Rob Herring (Arm)

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=20241022-elongated-chaos-7e47ffcaf073@spud \
    --to=conor@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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