From: Andriy Tryshnivskyy <andriy.tryshnivskyy@opensynergy.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: jbhayana@google.com, lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, Vasyl.Vavrychuk@opensynergy.com,
andy.shevchenko@gmail.com
Subject: Re: [PATCH v7 1/2] iio: core: Introduce IIO_VAL_INT_64.
Date: Sun, 24 Oct 2021 19:58:52 +0300 [thread overview]
Message-ID: <20912d4e-8417-73d6-a42f-ceaada6e3cf3@opensynergy.com> (raw)
In-Reply-To: <20211024171015.3b6b46e5@jic23-huawei>
On 24.10.21 19:10, Jonathan Cameron wrote:
> CAUTION: This email originated from outside of the organization.
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On Sun, 24 Oct 2021 12:16:26 +0300
> Andriy Tryshnivskyy <andriy.tryshnivskyy@opensynergy.com> wrote:
>
>> Introduce IIO_VAL_INT_64 to read 64-bit value for
>> channel attribute. Val is used as lower 32 bits.
>>
>> Signed-off-by: Andriy Tryshnivskyy <andriy.tryshnivskyy@opensynergy.com>
>> ---
>> drivers/iio/industrialio-core.c | 3 +++
>> include/linux/iio/types.h | 1 +
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
>> index 6d2175eb7af2..49e42d04ea16 100644
>> --- a/drivers/iio/industrialio-core.c
>> +++ b/drivers/iio/industrialio-core.c
>> @@ -702,6 +702,9 @@ static ssize_t __iio_format_value(char *buf, size_t offset, unsigned int type,
>> }
>> case IIO_VAL_CHAR:
>> return sysfs_emit_at(buf, offset, "%c", (char)vals[0]);
>> + case IIO_VAL_INT_64:
>> + tmp2 = (s64)((((u64)vals[1]) << 32) | (u32)vals[0]);
>> + return sysfs_emit_at(buf, offset, "%lld", tmp2);
>> default:
>> return 0;
>> }
>> diff --git a/include/linux/iio/types.h b/include/linux/iio/types.h
>> index 84b3f8175cc6..bb6578a5ee28 100644
>> --- a/include/linux/iio/types.h
>> +++ b/include/linux/iio/types.h
>> @@ -24,6 +24,7 @@ enum iio_event_info {
>> #define IIO_VAL_INT_PLUS_NANO 3
>> #define IIO_VAL_INT_PLUS_MICRO_DB 4
>> #define IIO_VAL_INT_MULTIPLE 5
>> +#define IIO_VAL_INT_64 6 /* 64-bit data, val is lower 32 bits) */
> I'm guessing the closing bracket is left over of some editing?
>
> Otherwise fine and I can tidy that up whilst applying.
Yes, it's a typo. Please remove it while applying. Thanks!
> Note that this is almost certainly too late for this cycle (we are
> about a week away from merge window subject to whatever Linus says
> for rc7 and new stuff needs some time to soak in next), but I'll
> plan to get it queued up early in the next one.
>
Noted. Thanks a lot!
>> #define IIO_VAL_FRACTIONAL 10
>> #define IIO_VAL_FRACTIONAL_LOG2 11
>> #define IIO_VAL_CHAR 12
Best regards,
Andriy.
next prev parent reply other threads:[~2021-10-24 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 9:16 [PATCH v7 0/2] iio/scmi: Add reading "raw" attribute Andriy Tryshnivskyy
2021-10-24 9:16 ` [PATCH v7 1/2] iio: core: Introduce IIO_VAL_INT_64 Andriy Tryshnivskyy
2021-10-24 16:10 ` Jonathan Cameron
2021-10-24 16:58 ` Andriy Tryshnivskyy [this message]
2021-10-30 14:47 ` Jonathan Cameron
2021-11-01 7:28 ` Andriy Tryshnivskyy
2021-11-01 13:54 ` Andriy Tryshnivskyy
2021-11-01 14:23 ` Andy Shevchenko
2021-11-02 7:33 ` [PATCH v7 3/3] iio: test: Add test for IIO_VAL_INT_64 Andriy Tryshnivskyy
2021-11-02 8:11 ` Andy Shevchenko
2021-11-05 8:45 ` Andriy Tryshnivskyy
2021-11-05 8:50 ` Lars-Peter Clausen
2021-11-05 8:55 ` Andriy Tryshnivskyy
2021-11-05 9:04 ` Lars-Peter Clausen
2021-10-24 9:16 ` [PATCH v7 2/2] iio/scmi: Add reading "raw" attribute Andriy Tryshnivskyy
2021-10-28 14:08 ` Jonathan Cameron
2021-10-28 18:52 ` Jyoti Bhayana
2021-10-30 14:49 ` [PATCH v7 0/2] " Jonathan Cameron
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=20912d4e-8417-73d6-a42f-ceaada6e3cf3@opensynergy.com \
--to=andriy.tryshnivskyy@opensynergy.com \
--cc=Vasyl.Vavrychuk@opensynergy.com \
--cc=andy.shevchenko@gmail.com \
--cc=jbhayana@google.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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