From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.3 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 995AAC43603 for ; Tue, 10 Dec 2019 15:03:36 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 644B82077B for ; Tue, 10 Dec 2019 15:03:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="c0D1tPpy" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 644B82077B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1ieh2T-0005rL-34; Tue, 10 Dec 2019 10:03:01 -0500 Received: from mail-ot1-x32c.google.com ([2607:f8b0:4864:20::32c]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1ieh2K-0005r5-R2 for kernelnewbies@kernelnewbies.org; Tue, 10 Dec 2019 10:02:52 -0500 Received: by mail-ot1-x32c.google.com with SMTP id 59so15718221otp.12 for ; Tue, 10 Dec 2019 07:02:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=WJ9x8MI5MEEv2SWeM3yFxGbTEc8+mCg5p5/QUcA8L4M=; b=c0D1tPpyE/Zs3uaTpm+usSpGKrdqYurT1oXnwUQL5KGZyt2RG9O/nUqY2clHbMvc9J EOwbS18P0/pnCq+AmX6MUZ6adVdKyKuzjqNz2aWY2SxX8ctGtjE9SQ+jpfrztqwnOFze 4Q+10m0GxPXn0q6Aky1do5f9BTWPCjP62j5DKV7X43ZnpiZPeJImPAc5milBeIQl0Pln QoLq/ngtNTT1KcZ8/4XqLz4jrnUxjjG5aR65jXWQYrT2i1C+Fyc5k54ifpsnlW31a56T IpvOMeMg9uRRgclOJmWfZIgQc/r72EltkyFRy2hFpFYxtSCSFEEnbsRMw+txU/OQfsPh hT6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WJ9x8MI5MEEv2SWeM3yFxGbTEc8+mCg5p5/QUcA8L4M=; b=IZBI1CeCaFzzwyHdzPTownKYYnmdqMXlJYQhyqKj4glO5QFTtWPo10qdZMfCF0MA7q NMpxFII2FUB0LN66vsSk8xNDHb2ttDivcTzrMat4qCtV1eicWlABgFKdvWb6n/9HKl0X i8uOJKkxUTCdQj5z0IfbzzDOa/2EjXQyi9pk49bfwEH/DLcKoBeIFmO1pljkWN4RHQwB wF2cFdVw8opHof5sRCTzF8n1dMwugt+sEv0/NBZzWwRvzZjHWz/ZIfrLLgrczYAy89LG PbzBBUfLnuacgNhKQOIgoSkC4TFrgUTn8Zi12dGobZvwKeV5K4e7JRRPsxjNqPcawdoL gXBQ== X-Gm-Message-State: APjAAAVMqAcGbW5jggTCAzcyTNQ5WlbTOk/rQjke5C+WclunTNAse9iB eMv6grurphXAWF5z945e3UfIx3Nxn0zteoQSAwqw/0z6 X-Google-Smtp-Source: APXvYqxpZ4yW6Gq4yjkqKVGyDgEVvNae/wpzksJsHW9PL/bgZfEkpAK3WXjEhPlbOxvbebJAXU1faEvYyBPDnD5dbWs= X-Received: by 2002:a9d:7147:: with SMTP id y7mr25059264otj.353.1575990109880; Tue, 10 Dec 2019 07:01:49 -0800 (PST) MIME-Version: 1.0 From: Tomek Domek Date: Tue, 10 Dec 2019 16:01:38 +0100 Message-ID: Subject: the difference between /drivers/spi and /drivers/mtd To: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0077280199261211505==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============0077280199261211505== Content-Type: multipart/alternative; boundary="000000000000ab43c705995acada" --000000000000ab43c705995acada Content-Type: text/plain; charset="UTF-8" Hi I have in device tree node: qspi: somename@0 { compatible = "nameOfDriverFrom/drivers/spi"; reg = ; clocks = ; clock-names = "some names"; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; and then I have such thing: &qspi { pinctrl-names="default"; pinctrl-0 = <&reference to some pin controller>; status = "okay"; spi-max-frequency = <11000000>; flash@0 { compatible = "spi-flash (this is driver from /drivers/mtd/)"; #address-cells = <1>; #size-cells = <1>; reg = <0x0>; spi-max-frequency = <22000000>; }; }; Why just one node isn't enough? And what frequency driver have at all - 11MHz or 22MHz? What is the difference between drivers defined in /drivers/spi and /drivers/mtd? Does it mean that driver in /drivers/mtd can use somehow driver or the code from /drivers/spi? Or maybe it works in opposite direction? --000000000000ab43c705995acada Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi
I have in device tree node:

qspi: somename@0 {
=C2=A0 =C2=A0 compatible =3D "nameOfDriverFrom= /drivers/spi";
=C2=A0 =C2=A0 reg =3D <someAddr size>;
=C2= =A0 =C2=A0 clocks =3D <reference to clock>;
=C2=A0 =C2=A0 clock-na= mes =3D "some names";
=C2=A0 =C2=A0 #address-cells =3D <1&g= t;;
=C2=A0 =C2=A0 #size-cells =3D <0>;
=C2=A0 =C2=A0 status =3D= "disabled";
};

and then I have= such thing:
&qspi {
=C2=A0 =C2=A0 pinctrl-names=3D"d= efault";
=C2=A0 =C2=A0 pinctrl-0 =3D <&reference to some pin= controller>;
=C2=A0 =C2=A0 status =3D "okay";
=C2=A0 = =C2=A0 spi-max-frequency =3D <11000000>;

=C2=A0 =C2=A0 flash@0= {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 compatible =3D "spi-flash (this is d= river from /drivers/mtd/)";
=C2=A0 =C2=A0 =C2=A0 =C2=A0 #address-ce= lls =3D <1>;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 #size-cells =3D <1>= ;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 reg =3D <0x0>;
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 spi-max-frequency =3D <22000000>;
=C2=A0 =C2=A0 =C2=A0}= ;
};

Why just one node isn't enough? An= d what frequency driver have at all - 11MHz or 22MHz?
What is the= difference between drivers defined in /drivers/spi and /drivers/mtd?
=
Does it mean that driver in /drivers/mtd can use somehow driver or the= code from /drivers/spi?
Or maybe it works in opposite direction?=
--000000000000ab43c705995acada-- --===============0077280199261211505== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============0077280199261211505==--