All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Stanislaw Gruszka <stf_xl@wp.pl>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:MIPS" <linux-mips@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCHv4 wireless-next 7/7] dt-bindings: net: wireless: rt2800: add
Date: Tue, 15 Jul 2025 08:28:30 +0200	[thread overview]
Message-ID: <8b2ee5da-4696-432a-bb0e-bed723192353@kernel.org> (raw)
In-Reply-To: <CAKxU2N8au-uncWoP+vGH4cHhHMOtq+VRFGNDs6rRLuHn-i1G-Q@mail.gmail.com>

On 14/07/2025 21:44, Rosen Penev wrote:
> On Mon, Jul 14, 2025 at 12:27 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Sat, Jul 12, 2025 at 02:04:48PM -0700, Rosen Penev wrote:
>>> Add device-tree bindings for the RT2800 SOC wifi device found in older
>>> Ralink/Mediatek devices.
>>
>> Your subject was cut. Probably you wanted something like add "Realtek foo adapter" etc.
> Not sure I follow.

Your subject is oddly incomplete.

>>
>>
>>>
>>> Signed-off-by: Rosen Penev <rosenp@gmail.com>
>>> ---
>>>  .../bindings/net/wireless/ralink,rt2880.yaml  | 47 +++++++++++++++++++
>>>  1 file changed, 47 insertions(+)
>>>  create mode 100644 Documentation/devicetree/bindings/net/wireless/ralink,rt2880.yaml
>>>
>>> diff --git a/Documentation/devicetree/bindings/net/wireless/ralink,rt2880.yaml b/Documentation/devicetree/bindings/net/wireless/ralink,rt2880.yaml
>>> new file mode 100644
>>> index 000000000000..a92aedf6ba01
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/net/wireless/ralink,rt2880.yaml
>>> @@ -0,0 +1,47 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/net/wireless/ralink,rt2880.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Ralink RT2880 wireless device
>>> +
>>> +maintainers:
>>> +  - Stanislaw Gruszka <stf_xl@wp.pl>
>>> +
>>> +description: |
>>> +  This node provides properties for configuring RT2880 SOC wifi devices.
>>> +  The node is expected to be specified as a root node of the device.
>>> +
>>> +allOf:
>>> +  - $ref: ieee80211.yaml#
>>> +
>>> +properties:
>>> +  compatible:
>>> +    enum:
>>> +      - ralink,rt2880-wifi
>>> +
>>> +  reg:
>>> +    maxItems: 1
>>> +
>>> +  clocks:
>>> +    maxItems: 1
>>> +
>>> +  interrupts:
>>> +    maxItems: 1
>>> +
>>> +required:
>>> +  - compatible
>>> +  - reg
>>
>> Why clocks are optional? SoC devices rarely work without a clock.
> Before this patchset the code was doing
> 
>  25         rt2x00dev->clk = clk_get(&pdev->dev, NULL);
>  24         if (IS_ERR(rt2x00dev->clk))
>  23                 rt2x00dev->clk = NULL;


That's driver. I am asking about hardware. Hardware rarely works without
clock. Just because some driver works is not a really a good proof,
because clock could be enabled by bootloader which would still prove my
point: hardware cannot work without clock.

Best regards,
Krzysztof


      reply	other threads:[~2025-07-15  6:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-12 21:04 [PATCHv4 wireless-next 0/7] wifi: rt2x00: add OF bindings + cleanup Rosen Penev
2025-07-12 21:04 ` [PATCHv4 wireless-next 1/7] wifi: rt2x00: add COMPILE_TEST Rosen Penev
2025-07-15  8:19   ` Sergio Paracuellos
2025-07-12 21:04 ` [PATCHv4 wireless-next 2/7] wifi: rt2x00: remove mod_name from platform_driver Rosen Penev
2025-07-12 21:04 ` [PATCHv4 wireless-next 3/7] wifi: rt2800soc: allow loading from OF Rosen Penev
2025-07-13  7:16   ` Stanislaw Gruszka
2025-07-12 21:04 ` [PATCHv4 wireless-next 4/7] wifi: rt2800: move 2x00soc to 2800soc Rosen Penev
2025-07-15  8:21   ` Sergio Paracuellos
2025-07-12 21:04 ` [PATCHv4 wireless-next 5/7] wifi: rt2x00: soc: modernize probe Rosen Penev
2025-07-13  7:19   ` Stanislaw Gruszka
2025-07-15  8:23   ` Sergio Paracuellos
2025-07-12 21:04 ` [PATCHv4 wireless-next 6/7] MIPS: dts: ralink: mt7620a: add wifi Rosen Penev
2025-07-15  8:22   ` Sergio Paracuellos
2025-07-12 21:04 ` [PATCHv4 wireless-next 7/7] dt-bindings: net: wireless: rt2800: add Rosen Penev
2025-07-14  7:27   ` Krzysztof Kozlowski
2025-07-14 19:44     ` Rosen Penev
2025-07-15  6:28       ` Krzysztof Kozlowski [this message]

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=8b2ee5da-4696-432a-bb0e-bed723192353@kernel.org \
    --to=krzk@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.org \
    --cc=rosenp@gmail.com \
    --cc=stf_xl@wp.pl \
    --cc=tsbogend@alpha.franken.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 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.