From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Poduval, Karthik" <kpoduval@lab126.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"Xiong, Jason" <jyxiong@amazon.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Anish Kumar, FNU" <anishkmr@amazon.com>,
"miguel.lopes@synopsys.com" <miguel.lopes@synopsys.com>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"kishon@kernel.org" <kishon@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>
Subject: Re: [PATCH v2 2/2] phy: dw-dphy-rx: Add dt bindings for Synopsys MIPI D-PHY RX
Date: Fri, 11 Jul 2025 09:09:25 +0200 [thread overview]
Message-ID: <1a4f27e3-49e7-4499-acad-c33d5cfec7a8@kernel.org> (raw)
In-Reply-To: <1c135aa4989f7a49cc58a092986e27712210d662.camel@lab126.com>
On 10/07/2025 23:24, Poduval, Karthik wrote:
>>> +maintainers:
>>> + - Karthik Poduval <kpoduval@lab126.com>
>>> + - Jason Xiong <jyxiong@amazon.com>
>>> + - Miguel Lopes <miguel.lopes@synopsys.com
>>> +
>>> +description: |
>>> + These are the bindings for Synopsys Designware MIPI DPHY RX phy
>>> driver.
>>> + Currently only supported phy version is v1.2.
>>> +
>>> +properties:
>>> + compatible:
>>> + const: snps,dw-dphy-1p2
>>
>> You should rather use SoC compatibles.
> If similar Synopsys D-PHY is used in multiple SoCs with slight
> variations, should each SoC have its own D-PHY driver or is it better
Your incorrect subject probably mislead you, but this is not a driver
patch. These are DT bindings.
SoC specific compatibles are almost always preferred.
> to have a common one that works for all SoCs like arm,smmu-v3 or like
> the EEPROM driver below ?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/misc/eeprom/eeprom_93xx46.c?h=v6.16-rc5#n391
> where driver specific driver_data could support multiple versions or
> SoC variations.
> Our team thought of the common driver approach however looking for
> general guidance from PHY subsystem maintainers and contributors.
We don't discuss here driver.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-11 7:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 2:42 [PATCH v2 0/2] Synopsys DW DPHY Driver Karthik Poduval
2025-07-10 2:42 ` [PATCH v2 1/2] phy: dw-dphy-rx: Add Synopsys DesignWare D-PHY RX Karthik Poduval
2025-07-10 4:08 ` Frank Li
2025-07-10 5:12 ` Poduval, Karthik
2025-07-10 19:48 ` Frank Li
2025-07-10 4:14 ` Frank Li
2025-07-10 5:15 ` Poduval, Karthik
2025-07-10 7:26 ` Krzysztof Kozlowski
2025-07-10 22:13 ` kernel test robot
2025-07-11 7:13 ` kernel test robot
2025-07-10 2:42 ` [PATCH v2 2/2] phy: dw-dphy-rx: Add dt bindings for Synopsys MIPI " Karthik Poduval
2025-07-10 3:32 ` Rob Herring (Arm)
2025-07-10 4:02 ` Frank Li
2025-07-10 7:24 ` Krzysztof Kozlowski
2025-07-10 21:24 ` Poduval, Karthik
2025-07-11 7:09 ` Krzysztof Kozlowski [this message]
2025-07-10 7:27 ` Krzysztof Kozlowski
2025-07-10 3:56 ` [PATCH v2 0/2] Synopsys DW DPHY Driver Frank Li
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=1a4f27e3-49e7-4499-acad-c33d5cfec7a8@kernel.org \
--to=krzk@kernel.org \
--cc=anishkmr@amazon.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jyxiong@amazon.com \
--cc=kishon@kernel.org \
--cc=kpoduval@lab126.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=miguel.lopes@synopsys.com \
--cc=robh@kernel.org \
--cc=vkoul@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).