All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Joern Engel <joern@lazybastard.org>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Sagi Grimberg <sagi@grimberg.me>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 2/6] nvme: assign of_node to nvme device
Date: Tue, 6 Aug 2024 15:09:38 +0200	[thread overview]
Message-ID: <20240806130938.GA12231@lst.de> (raw)
In-Reply-To: <66b21f20.5d0a0220.200175.4b9b@mx.google.com>

On Tue, Aug 06, 2024 at 03:03:24PM +0200, Christian Marangi wrote:
> Well on embedded pure PCIe card most of the time are not a thing...
> Unless it's an enterprise product, everything is integrated in the pcb
> and not detachable for cost saving measure or also if the thing use PCIe
> protocol but it tighlty coupled with the SoC.

Yes, PCIe has a bunch of form factors, including just soldered on BGA
devices, but none of that matters at all for the logical protocol.

> This implementation is already very common for all kind of pcie devices
> like wireless card, gpio expander that are integrated in the PCB and
> require property in DT like calibration data, quirks or GPIO pin
> definitions, i2c...

Do you have a document on that/


WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Joern Engel <joern@lazybastard.org>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Sagi Grimberg <sagi@grimberg.me>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 2/6] nvme: assign of_node to nvme device
Date: Tue, 6 Aug 2024 15:09:38 +0200	[thread overview]
Message-ID: <20240806130938.GA12231@lst.de> (raw)
In-Reply-To: <66b21f20.5d0a0220.200175.4b9b@mx.google.com>

On Tue, Aug 06, 2024 at 03:03:24PM +0200, Christian Marangi wrote:
> Well on embedded pure PCIe card most of the time are not a thing...
> Unless it's an enterprise product, everything is integrated in the pcb
> and not detachable for cost saving measure or also if the thing use PCIe
> protocol but it tighlty coupled with the SoC.

Yes, PCIe has a bunch of form factors, including just soldered on BGA
devices, but none of that matters at all for the logical protocol.

> This implementation is already very common for all kind of pcie devices
> like wireless card, gpio expander that are integrated in the PCB and
> require property in DT like calibration data, quirks or GPIO pin
> definitions, i2c...

Do you have a document on that/


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2024-08-06 13:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 11:41 [PATCH v3 0/6] mtd: improve block2mtd + airoha parser Christian Marangi
2024-08-06 11:41 ` Christian Marangi
2024-08-06 11:41 ` [PATCH v3 1/6] dt-bindings: nvme: Document nvme-card compatible Christian Marangi
2024-08-06 11:41   ` Christian Marangi
2024-08-06 12:42   ` Christoph Hellwig
2024-08-06 12:42     ` Christoph Hellwig
2024-08-06 12:55     ` Christian Marangi
2024-08-06 12:55       ` Christian Marangi
2024-08-06 13:00       ` Christoph Hellwig
2024-08-06 13:00         ` Christoph Hellwig
2024-08-06 13:17         ` Christian Marangi
2024-08-06 13:17           ` Christian Marangi
2024-08-06 11:41 ` [PATCH v3 2/6] nvme: assign of_node to nvme device Christian Marangi
2024-08-06 11:41   ` Christian Marangi
2024-08-06 12:43   ` Christoph Hellwig
2024-08-06 12:43     ` Christoph Hellwig
2024-08-06 13:03     ` Christian Marangi
2024-08-06 13:03       ` Christian Marangi
2024-08-06 13:09       ` Christoph Hellwig [this message]
2024-08-06 13:09         ` Christoph Hellwig
2024-08-06 13:26         ` Christian Marangi
2024-08-06 13:26           ` Christian Marangi
2024-08-06 15:39       ` Dragan Simic
2024-08-06 15:39         ` Dragan Simic
2024-08-06 11:41 ` [PATCH v3 3/6] dt-bindings: mmc: add property for partitions node in mmc-card node Christian Marangi
2024-08-06 11:41   ` Christian Marangi
2024-08-06 11:41 ` [PATCH v3 4/6] block2mtd: attach device OF node to MTD device Christian Marangi
2024-08-06 11:41   ` Christian Marangi
2024-08-06 11:41 ` [PATCH v3 5/6] dt-bindings: mtd: Add Documentation for Airoha fixed-partitions Christian Marangi
2024-08-06 11:41   ` Christian Marangi
2024-08-06 11:41 ` [PATCH v3 6/6] mtd: parser: add support for Airoha parser Christian Marangi
2024-08-06 11:41   ` Christian Marangi
2024-08-07 21:27   ` kernel test robot
2024-08-07 21:27     ` kernel test robot

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=20240806130938.GA12231@lst.de \
    --to=hch@lst.de \
    --cc=ansuelsmth@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=joern@lazybastard.org \
    --cc=kbusch@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=sagi@grimberg.me \
    --cc=tsbogend@alpha.franken.de \
    --cc=ulf.hansson@linaro.org \
    --cc=vigneshr@ti.com \
    --cc=wsa+renesas@sang-engineering.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.