linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wujek dev <dev_public@wujek.eu>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: si5341: Add sysfs property to check selected input
Date: Thu, 09 Dec 2021 12:04:48 +0000	[thread overview]
Message-ID: <XedF_WXH1abo9n2bzY4gaRIjq-R1O6ha5QedK8e1W9-R_1p_zo90aAgaKSSfDYMW3WUaMdY0pjONnKWj4zNMh5TbHlbZbAVAe4KG_Zq8Vvk=@wujek.eu> (raw)
In-Reply-To: <20211208043054.CEFD6C00446@smtp.kernel.org>



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Wednesday, December 8th, 2021 at 05:30, Stephen Boyd <sboyd@kernel.org> wrote:

> Quoting wujek dev (2021-12-06 15:08:03)
>
> > Other sysfs properties used by this driver are not documented so I didn't add for this one. Even more not a single property from clk subsystem is described. Shall I the add description of this single property?
>
> Please don't top post. sysfs properties are supposed to be single value
>
> and for machine consumption. Is this a debugfs property?
No, I think this is rather sysfs than debugfs. The type of information is similar to other reported by this driver. The values in the added property are the same, this is just a different representation (input selected as an int, as string based on manual and as string as described in the DTB).

  reply	other threads:[~2021-12-09 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 14:15 [PATCH] clk: si5341: Add sysfs property to check selected input Adam Wujek
2021-12-06 22:53 ` Stephen Boyd
2021-12-06 23:08   ` wujek dev
2021-12-08  4:30     ` Stephen Boyd
2021-12-09 12:04       ` wujek dev [this message]
2021-12-16  6:32         ` Stephen Boyd
2021-12-16 14:25           ` wujek dev
2021-12-17  1:47             ` Stephen Boyd

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='XedF_WXH1abo9n2bzY4gaRIjq-R1O6ha5QedK8e1W9-R_1p_zo90aAgaKSSfDYMW3WUaMdY0pjONnKWj4zNMh5TbHlbZbAVAe4KG_Zq8Vvk=@wujek.eu' \
    --to=dev_public@wujek.eu \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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).