From: Viresh Kumar <viresh.kumar@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
linux-gpio@vger.kernel.org, "Kent Gibson" <warthog618@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
stratos-dev@op-lists.linaro.org,
"Gerard Ryan" <g.m0n3y.2503@gmail.com>
Subject: Re: [PATCH V6 3/8] libgpiod: Add rust wrapper crate
Date: Fri, 14 Oct 2022 15:27:24 +0530 [thread overview]
Message-ID: <20221014095724.ajajkp3ysdfxd2f2@vireshk-i7> (raw)
In-Reply-To: <CAMRc=MfNjCARhhG1yGDKU0HYUmsHkN_MihWy-+pg+SY0T9WERg@mail.gmail.com>
On 14-10-22, 11:45, Bartosz Golaszewski wrote:
> Maybe also add chained mutators everywhere? To be able to do
> settings.set_direction().set_edge() etc.?
Based on Kent's suggestion earlier, what I have implemented is
set_prop(), to which one can pass all settings and it will apply them
in a loop.
pub fn set_prop(&mut self, values: &[SettingVal]) -> Result<()> {
for value in values {
match value {
SettingVal::Direction(val) => self.set_direction(*val)?,
SettingVal::EdgeDetection(val) => self.set_edge_detection(*val)?,
SettingVal::Bias(val) => self.set_bias(*val)?,
SettingVal::Drive(val) => self.set_drive(*val)?,
SettingVal::ActiveLow(val) => self.set_active_low(*val),
SettingVal::DebouncePeriod(val) => self.set_debounce_period(*val),
SettingVal::EventClock(val) => self.set_event_clock(*val)?,
SettingVal::OutputValue(val) => self.set_output_value(*val)?,
}
}
Ok(())
}
I think that replaces the need of nested ones ? And if we want to add
those later, we can always come back and add them. But I am not sure
it would be required.
> And I would still love a thorough API review from someone who actually
> knows rust too. :(
Well, Kent did a very good job earlier. I am not sure if he has extra
cycles to review this once again, though not a lot has changed since
last time.
> But I will play some more with v7 so do send it.
Great.
--
viresh
next prev parent reply other threads:[~2022-10-14 9:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 11:08 [PATCH V6 0/8] libgpiod: Add Rust bindings Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 1/8] libgpiod: Add libgpiod-sys rust crate Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 2/8] libgpiod-sys: Add pre generated rust bindings Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 3/8] libgpiod: Add rust wrapper crate Viresh Kumar
2022-09-26 13:29 ` Bartosz Golaszewski
2022-09-26 15:26 ` Viresh Kumar
2022-09-27 13:18 ` Bartosz Golaszewski
2022-09-27 13:57 ` Viresh Kumar
2022-09-27 15:25 ` Bartosz Golaszewski
2022-09-28 11:10 ` Viresh Kumar
2022-09-28 12:20 ` Bartosz Golaszewski
2022-09-28 15:17 ` Viresh Kumar
2022-09-28 17:54 ` Bartosz Golaszewski
2022-09-29 6:54 ` Viresh Kumar
2022-09-29 7:37 ` Bartosz Golaszewski
2022-09-29 8:58 ` Viresh Kumar
2022-09-29 11:16 ` Bartosz Golaszewski
2022-09-29 11:43 ` Kent Gibson
2022-09-29 13:55 ` Miguel Ojeda
2022-10-11 4:16 ` Viresh Kumar
2022-10-11 4:25 ` Kent Gibson
2022-10-11 4:37 ` Viresh Kumar
2022-10-11 4:46 ` Viresh Kumar
2022-10-13 6:12 ` Viresh Kumar
2022-10-14 9:45 ` Bartosz Golaszewski
2022-10-14 9:57 ` Viresh Kumar [this message]
2022-10-14 14:25 ` Bartosz Golaszewski
2022-10-14 16:06 ` Kent Gibson
2022-10-17 11:26 ` Viresh Kumar
2022-10-17 11:34 ` Kent Gibson
2022-10-17 11:37 ` Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 4/8] libgpiod: Add rust examples Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 5/8] libgpiod: Add gpiosim rust crate Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 6/8] gpiosim: Add pre generated rust bindings Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 7/8] libgpiod: Add rust tests Viresh Kumar
2022-09-26 11:08 ` [PATCH V6 8/8] libgpiod: Integrate building of rust bindings with make Viresh Kumar
2022-09-26 15:57 ` [PATCH V6 0/8] libgpiod: Add Rust bindings Viresh Kumar
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=20221014095724.ajajkp3ysdfxd2f2@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=brgl@bgdev.pl \
--cc=g.m0n3y.2503@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=warthog618@gmail.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).