linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	William Zhang <william.zhang@broadcom.com>,
	Anand Gore <anand.gore@broadcom.com>,
	Kursad Oney <kursad.oney@broadcom.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Alexandre TORGUE" <alexandre.torgue@st.com>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	bcm-kernel-feedback-list@broadcom.com,
	"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V2 1/2] dt-bindings: serial: add Broadcom's BCMBCA family High Speed UART
Date: Wed, 22 Nov 2023 16:52:17 +0100	[thread overview]
Message-ID: <03ad42c0-1648-43e1-bbd0-9ed02bdf4073@gmail.com> (raw)
In-Reply-To: <141deca9-6017-4e3f-a237-8dacc67662de@linaro.org>

On 22.11.2023 16:50, Krzysztof Kozlowski wrote:
> On 22/11/2023 16:49, Rafał Miłecki wrote:
>>>> For example a year ago I added binding for BCMBCA SoC timer without
>>>> actual driver, see e112f2de151b ("dt-bindings: timer: Add Broadcom's
>>>> BCMBCA timers").
>>>>
>>>> I'm not sure if we're going to agree on this, but personally I like
>>>> describing hardware as much as I can. So it's well documented /
>>>> understood and people may eventually write drivers for it. Maybe it's
>>>> partially because I come from Broadcom's world that isn't well known
>>>> for upstream efforts in general.
>>>
>>> The problem is that "brcm,bcmbca-hs-uart" is not describing hardware. It
>>> is saying that all these devices have similar (compatible) programming
>>> model, so the OS can use just one compatible. This goes away from pure
>>> hardware description into interpretation.
>>>
>>> Rob already commented on such non-SoC compatibles multiple times. I do
>>> not see any reason here to not use specific compatible as fallback.
>>
>> Do I get it right we should rather have some base specific compatible
>> like: "brcm,bcm63138-hs-uart" and then if anything use fallback to it
>> like: "brcm,bcm4908-hs-uart", "brcm,bcm63138-hs-uart"; ?
> 
> Yes, or the other way around, depends which is probably the oldest.

Thank you for helping me on that!

  reply	other threads:[~2023-11-22 15:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 14:42 [PATCH V2 1/2] dt-bindings: serial: add Broadcom's BCMBCA family High Speed UART Rafał Miłecki
2023-11-22 14:42 ` [PATCH V2 2/2] ARM: dts: broadcom: Add BCM63138's high speed UART Rafał Miłecki
2023-12-05 22:44   ` Florian Fainelli
2023-11-22 14:46 ` [PATCH V2 1/2] dt-bindings: serial: add Broadcom's BCMBCA family High Speed UART Krzysztof Kozlowski
2023-11-22 14:52   ` Rafał Miłecki
2023-11-22 15:00     ` Krzysztof Kozlowski
2023-11-22 15:32       ` Rafał Miłecki
2023-11-22 15:37         ` Krzysztof Kozlowski
2023-11-22 15:49           ` Rafał Miłecki
2023-11-22 15:50             ` Krzysztof Kozlowski
2023-11-22 15:52               ` Rafał Miłecki [this message]
2023-11-22 18:39                 ` William Zhang
2023-11-22 18:46                   ` Krzysztof Kozlowski
2023-11-22 18:56                     ` Krzysztof Kozlowski
2023-11-22 19:28                       ` Florian Fainelli
2023-11-22 19:01                     ` William Zhang

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=03ad42c0-1648-43e1-bbd0-9ed02bdf4073@gmail.com \
    --to=zajec5@gmail.com \
    --cc=alexandre.torgue@st.com \
    --cc=anand.gore@broadcom.com \
    --cc=andre.przywara@arm.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --cc=william.zhang@broadcom.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 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).