From: <Dharma.B@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <robh@kernel.org>
Cc: <conor@kernel.org>, <krzk@kernel.org>,
<Manikandan.M@microchip.com>, <andrzej.hajda@intel.com>,
<neil.armstrong@linaro.org>, <rfoss@kernel.org>,
<Laurent.pinchart@ideasonboard.com>, <jonas@kwiboo.se>,
<jernej.skrabec@gmail.com>, <airlied@gmail.com>,
<daniel@ffwll.ch>, <maarten.lankhorst@linux.intel.com>,
<mripard@kernel.org>, <tzimmermann@suse.de>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Linux4Microchip@microchip.com>
Subject: Re: [PATCH 1/3] dt-bindings: display: bridge: add sam9x7-lvds compatible
Date: Thu, 1 Feb 2024 08:56:45 +0000 [thread overview]
Message-ID: <5047d939-7831-4414-b4f4-94cec78a0446@microchip.com> (raw)
In-Reply-To: <32fd4622-1bc1-48f7-85f0-e04fcb6c0f88@linaro.org>
On 01/02/24 1:09 pm, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 01/02/2024 05:10, Dharma.B@microchip.com wrote:
>> On 31/01/24 12:42 am, Rob Herring wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>> On Tue, Jan 23, 2024 at 03:39:13AM +0000, Dharma.B@microchip.com wrote:
>>>> Hi Conor,
>>>>
>>>> On 22/01/24 10:07 pm, Conor Dooley wrote:
>>>>> On Mon, Jan 22, 2024 at 04:51:16PM +0100, Krzysztof Kozlowski wrote:
>>>>>> On 22/01/2024 09:29, Dharma Balasubiramani wrote:
>>>>>>> Add the 'sam9x7-lvds' compatible binding, which describes the
>>>>>>> Low Voltage Differential Signaling (LVDS) Controller found on Microchip's
>>>>>>> sam9x7 series System-on-Chip (SoC) devices. This binding will be used to
>>>>>>> define the properties and configuration for the LVDS Controller in DT.
>>>>>>>
>>>>>>> Signed-off-by: Dharma Balasubiramani<dharma.b@microchip.com>
>>>>>>> ---
>>>>>>> .../display/bridge/microchip,sam9x7-lvds.yaml | 59 +++++++++++++++++++
>>>>>>> 1 file changed, 59 insertions(+)
>>>>>>> create mode 100644 Documentation/devicetree/bindings/display/bridge/microchip,sam9x7-lvds.yaml
>>>>>>>
>>>>>>> diff --git a/Documentation/devicetree/bindings/display/bridge/microchip,sam9x7-lvds.yaml b/Documentation/devicetree/bindings/display/bridge/microchip,sam9x7-lvds.yaml
>>>>>>> new file mode 100644
>>>>>>> index 000000000000..8c2c5b858c85
>>>>>>> --- /dev/null
>>>>>>> +++ b/Documentation/devicetree/bindings/display/bridge/microchip,sam9x7-lvds.yaml
>>>>>>> @@ -0,0 +1,59 @@
>>>>>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>>>>>> +%YAML 1.2
>>>>>>> +---
>>>>>>> +$id:http://devicetree.org/schemas/display/bridge/microchip,sam9x7-lvds.yaml#
>>>>>>> +$schema:http://devicetree.org/meta-schemas/core.yaml#
>>>>>>> +
>>>>>>> +title: Microchip SAM9X7 LVDS Controller
>>>>>> What is the "X"?
>>>>>>
>>>>>>> +
>>>>>>> +maintainers:
>>>>>>> + - Dharma Balasubiramani<dharma.b@microchip.com>
>>>>>>> +
>>>>>>> +description: |
>>>>>> Do not need '|' unless you need to preserve formatting.
>>>>>>
>>>>>>> + The Low Voltage Differential Signaling Controller (LVDSC) manages data
>>>>>>> + format conversion from the LCD Controller internal DPI bus to OpenLDI
>>>>>>> + LVDS output signals. LVDSC functions include bit mapping, balanced mode
>>>>>>> + management, and serializer.
>>>>>>> +
>>>>>>> +properties:
>>>>>>> + compatible:
>>>>>>> + const: microchip,sam9x7-lvds
>>>>>> What is "x"? Wildcard? Then no, don't use it and instead use proper SoC
>>>>>> version number.
>>>>> These SoCs actually do have an x in their name. However, and I do always
>>>>> get confused here, the sam9x7 is a series of SoCs (the cover letter does
>>>>> say this) rather than a specific device.
>>>>> I think the series current consists of a sam9x70 sam9x72 and a sam9x75.
>>>>> The devices are largely similar, but I am not sure if the sam9x70
>>>>> supports LVDS at all. Having a compatible for the series does not seem
>>>>> correct to me.
>>>> Yes, you are correct. Only sam9x72 and sam9x75 have LVDS support, while
>>>> sam9x70 does not. I will revise the compatibility to include both
>>>> sam9x72 and sam9x75, as outlined below:
>>>>
>>>> properties:
>>>> compatible:
>>>> enum:
>>>> - microchip,sam9x72-lvds
>>>> - microchip,sam9x75-lvds
>>>
>>> I would presume these 2 are the same, but the above implies they
>>> aren't. I think what you had is fine assuming these are all
>>> fundamentally the same part with just packaging or fused off h/w
>>> differences.
>>
>> Yes, so is it okay to have compatible for a series? Shall I go ahead with
>> "
>> compatible:
>> const: microchip,sam9x7-lvds
>
> You said 9x70, which would match such 9x7 "series", is different, so I
> still think series should not be used. I don't know much about Microchip
> naming scheme, so this x is always confusing. However if these are the
> same, maybe just use sam9x72?
sam9x75 is the first board to be available publicly; hence, I shall use
the "microchip,sam9x75-lvds" compatible and reuse the same in other
boards that (features same IP) will come later.
>
> Best regards,
> Krzysztof
>
--
With Best Regards,
Dharma B.
next prev parent reply other threads:[~2024-02-01 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 8:29 [PATCH 0/3] LVDS Controller Support for SAM9X7 SoC Dharma Balasubiramani
2024-01-22 8:29 ` [PATCH 1/3] dt-bindings: display: bridge: add sam9x7-lvds compatible Dharma Balasubiramani
2024-01-22 15:51 ` Krzysztof Kozlowski
2024-01-22 16:37 ` Conor Dooley
2024-01-23 3:39 ` Dharma.B
2024-01-30 19:12 ` Rob Herring
2024-02-01 4:10 ` Dharma.B
2024-02-01 7:39 ` Krzysztof Kozlowski
2024-02-01 8:56 ` Dharma.B [this message]
2024-01-23 3:30 ` Dharma.B
2024-01-22 8:29 ` [PATCH 2/3] drm/bridge: add lvds controller support for sam9x7 Dharma Balasubiramani
2024-01-22 15:49 ` Krzysztof Kozlowski
2024-01-23 8:26 ` Dharma.B
2024-02-03 14:20 ` kernel test robot
2024-01-22 8:29 ` [PATCH 3/3] MAINTAINERS: add SAM9X7 SoC's LVDS controller Dharma Balasubiramani
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=5047d939-7831-4414-b4f4-94cec78a0446@microchip.com \
--to=dharma.b@microchip.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Linux4Microchip@microchip.com \
--cc=Manikandan.M@microchip.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®