All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
	Andreas Kemnade <andreas@kemnade.info>,
	Rob Herring <robh+dt@kernel.org>,
	linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2] dt-bindings: i2c: Move i2c-omap.txt to YAML format
Date: Wed, 26 May 2021 09:52:30 +0300	[thread overview]
Message-ID: <YK3wLgJSy0sVUn51@atomide.com> (raw)
In-Reply-To: <e4fbdf7b-6556-eeba-c1b8-9d48f718437a@ti.com>

* Vignesh Raghavendra <vigneshr@ti.com> [210510 11:06]:
> What do you prefer here? Removing dmas from schema would mean I would
> have to delete dmas property from omap2/3 dtsi files that list dmas
> property today? Note that driver does not support DMA mode today.

If the dma channels are not used by the driver, and not in the binding,
it's unlikely they will ever get used. Sure the dma channels describe
the hardware, and there's a slim chance some other OS needs them, but I
doubt it.

It seems weird we stop describing hardware in the devicetree to avoid
binding check warnings though. Up to you to figure out what you want
to do as far as I'm concerned.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
	Andreas Kemnade <andreas@kemnade.info>,
	Rob Herring <robh+dt@kernel.org>,
	linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2] dt-bindings: i2c: Move i2c-omap.txt to YAML format
Date: Wed, 26 May 2021 09:52:30 +0300	[thread overview]
Message-ID: <YK3wLgJSy0sVUn51@atomide.com> (raw)
In-Reply-To: <e4fbdf7b-6556-eeba-c1b8-9d48f718437a@ti.com>

* Vignesh Raghavendra <vigneshr@ti.com> [210510 11:06]:
> What do you prefer here? Removing dmas from schema would mean I would
> have to delete dmas property from omap2/3 dtsi files that list dmas
> property today? Note that driver does not support DMA mode today.

If the dma channels are not used by the driver, and not in the binding,
it's unlikely they will ever get used. Sure the dma channels describe
the hardware, and there's a slim chance some other OS needs them, but I
doubt it.

It seems weird we stop describing hardware in the devicetree to avoid
binding check warnings though. Up to you to figure out what you want
to do as far as I'm concerned.

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-26  6:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 14:00 [PATCH v2] dt-bindings: i2c: Move i2c-omap.txt to YAML format Vignesh Raghavendra
2021-05-06 14:00 ` Vignesh Raghavendra
2021-05-06 18:55 ` Nishanth Menon
2021-05-06 18:55   ` Nishanth Menon
2021-05-07  6:54 ` Grygorii Strashko
2021-05-07  6:54   ` Grygorii Strashko
2021-05-07 14:15   ` Vignesh Raghavendra
2021-05-07 14:15     ` Vignesh Raghavendra
2021-05-07 14:36     ` Andreas Kemnade
2021-05-07 14:36       ` Andreas Kemnade
2021-05-07 17:24       ` Grygorii Strashko
2021-05-07 17:24         ` Grygorii Strashko
2021-05-07 21:43         ` Rob Herring
2021-05-07 21:43           ` Rob Herring
2021-05-07 22:02           ` Wolfram Sang
2021-05-07 22:02             ` Wolfram Sang
2021-05-10 11:06         ` Vignesh Raghavendra
2021-05-10 11:06           ` Vignesh Raghavendra
2021-05-26  6:52           ` Tony Lindgren [this message]
2021-05-26  6:52             ` Tony Lindgren
2021-05-07 21:19 ` Rob Herring
2021-05-07 21:19   ` Rob Herring

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=YK3wLgJSy0sVUn51@atomide.com \
    --to=tony@atomide.com \
    --cc=andreas@kemnade.info \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --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 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.