| /openbmc/linux/drivers/pinctrl/intel/ |
| H A D | pinctrl-intel.c | 112 struct intel_community *community; in intel_get_community() local
116 community = &pctrl->communities[i]; in intel_get_community()
117 if (pin >= community->pin_base && in intel_get_community()
118 pin < community->pin_base + community->npins) in intel_get_community()
119 return community; in intel_get_community()
128 intel_community_get_padgroup(const struct intel_community *community, in intel_community_get_padgroup() argument
133 for (i = 0; i < community->ngpps; i++) { in intel_community_get_padgroup()
134 const struct intel_padgroup *padgrp = &community->gpps[i]; in intel_community_get_padgroup()
146 const struct intel_community *community; in intel_get_padcfg() local
150 community = intel_get_community(pctrl, pin); in intel_get_padcfg()
[all …]
|
| H A D | pinctrl-cherryview.c | 573 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_readl() local
575 return readl(community->regs + offset); in chv_pctrl_readl()
580 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_writel() local
581 void __iomem *reg = community->regs + offset; in chv_pctrl_writel()
591 const struct intel_community *community = &pctrl->communities[0]; in chv_padreg() local
597 return community->pad_regs + offset + reg; in chv_padreg()
1303 const struct intel_community *community = &pctrl->communities[0]; in chv_gpio_set_intr_line() local
1336 for (i = community->nirqs - 1; i >= 0; i--) { in chv_gpio_set_intr_line()
1429 const struct intel_community *community = &pctrl->communities[0]; in chv_gpio_irq_handler() local
1442 for_each_set_bit(intr_line, &pending, community->nirqs) { in chv_gpio_irq_handler()
[all …]
|
| /openbmc/docs/ |
| H A D | discord-rules.md | 3 1. This community works together to build an Open Source BMC firmware. It's a
4 community expectation that you will provide access to your code in the course
6 your code. The community is not a substitute for a support contract.
8 2. OpenBMC community members are volunteering their time to answer your
12 private messages to other community members. Private requests for help place
14 others in the community cannot help if they cannot see the question.
20 5. Reflect on whether your standing in the community is appropriate for the help
21 you are requesting. If you are new to the community, you will likely have the
|
| H A D | community-membership.md | 18 [New contributors] should be welcomed to the community by existing members,
22 ## Established community members
24 Established community members are expected to demonstrate their adherence to the
32 Members are continuously active contributors in the community. They can have
35 are expected to remain active contributors to the community.
41 - Have made multiple contributions to the project or community. Contribution may
45 - Contributing to design review, subproject, or community discussions (e.g.
90 - Expected to be responsive to review requests as per [community expectations]
128 - Providing results and insight to the community on platform-specific issues.
129 - Expected to be responsive to review requests as per [community expectations]
[all …]
|
| H A D | meta-layer-guidelines.md | 7 if there's a question, and the community agrees, these guidelines can be
19 Also, in general, the maintainer is there to ensure that the greater community,
27 Discuss with the project maintainers and the community about whether or not the
42 the Yocto community is as responsive (sometimes much faster) than the OpenBMC
43 community in regards to pull requests.
104 community has looked through your design, a repo will be created for code to be
106 community through the mailing list or discord whether or not the OpenBMC
107 community would be willing to adopt support and maintenance of said project.
137 Discuss the code you'd like to write with the community using the mailing list
|
| H A D | SECURITY.md | 29 - Privately engage community members to understand and address the problem.
35 - Coordinate workarounds and fixes with you and the community.
47 - Join the OpenBMC community and fix the problem yourself.
|
| /openbmc/u-boot/arch/x86/cpu/braswell/ |
| H A D | early_uart.c | 34 static inline uint32_t gpio_pconf0(int community, int family, int pad) in gpio_pconf0() argument
36 return IO_BASE_ADDRESS + community * 0x8000 + 0x4400 + in gpio_pconf0()
40 static void gpio_select_func(int community, int family, int pad, int func) in gpio_select_func() argument
42 uint32_t pconf0_addr = gpio_pconf0(community, family, pad); in gpio_select_func()
|
| /openbmc/qemu/docs/devel/ |
| H A D | code-of-conduct.rst | 6 The QEMU community is made up of a mixture of professionals and
18 social and technical, happen all the time and the QEMU community is no
21 QEMU community should be respectful when dealing with other contributors as
22 well as with people outside the QEMU community and with users of QEMU.
24 Harassment and other exclusionary behavior are not acceptable. A community
44 This includes IRC, the mailing lists, the issue tracker, community
46 community uses for communication. This code of conduct also applies
48 member of the project or its community.
|
| H A D | maintainers.rst | 19 excellent community collaborators.
77 demonstrated to the community, usually via contributions and code
98 members of the QEMU community, you should make arrangements to attend
102 community member **in person**\ [#2020]_ so please make appropriate
|
| /openbmc/linux/Documentation/process/ |
| H A D | researcher-guidelines.rst | 8 The Linux kernel community welcomes transparent research on the Linux
13 The community greatly appreciates if researchers can share preliminary
17 sharing open access copies of the published research with the community
20 This document seeks to clarify what the Linux kernel community considers
31 The Linux kernel community expects that everyone interacting with the
34 code) produced by the Linux kernel community is welcome, though research
51 contributors. As a general rule, though, the kernel community derives
56 themselves or to the kernel community as a whole. For this reason, this
59 Kernel community members already receive far too much email and are likely
61 such requests deprives the community of valuable contributor time and is
[all …]
|
| H A D | code-of-conduct.rst | 11 our community a harassment-free experience for everyone, regardless of age, body
25 * Focusing on what is best for the community
26 * Showing empathy towards other community members
58 when an individual is representing the project or its community. Examples of
59 representing a project or community include using an official project e-mail
86 kernel community will be interpreting this document.
|
| H A D | code-of-conduct-interpretation.rst | 7 provide a set of rules for almost any open source community. Every
8 open-source community is unique and the Linux kernel is no exception.
10 community will interpret it. We also do not expect this interpretation
28 kernel community, a "maintainer" is anyone who is responsible for a
41 That being said, our community is vast and broad, and there is no new
43 behave in the parts of the community where they are active. That
49 others in the community when needed. Do not be afraid to reach out to
83 the Code of Conduct. The kernel community is aware of that and provides
89 The Linux kernel community primarily interacts on a set of public email
98 Conduct. The Linux kernel community does not have an "official" project
[all …]
|
| H A D | contribution-maturity-model.rst | 15 part of the Linux Kernel community need to allow engineers to be
24 expectations for upstream community engagement aim to increase the
35 upstream community.
70 * A Software Engineer’s community contributions will be considered in
98 * Organizations will consider community member feedback in official
106 * Organizations will actively seek out community member feedback as a
|
| H A D | index.rst | 9 Working with the kernel development community
14 to learn about how our community works. Reading these documents will make
46 Other guides to the community that are of interest to most developers are:
|
| H A D | kernel-enforcement-statement.rst | 9 sustainability of our software and community.
12 contributions made to our community, we share an interest in ensuring that
14 community and do not have an unintended negative impact on the health and
17 community to undertake the following commitment to users of the Linux kernel
21 it is in the best interests of our development community to adopt the
45 as a last resort, to be initiated only when other community efforts have
|
| H A D | development-process.rst | 22 work with the development community with a minimum of frustration. It is
23 an attempt to document how this community works in a way which is
|
| H A D | 1.Intro.rst | 13 availability to users, community support in many forms, and the ability to
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
81 Working with the kernel development community is not especially hard. But,
83 difficulties when trying to do kernel work. The kernel community has
93 community's ways (or, worse, who tries to flout or circumvent them) will
94 have a frustrating experience in store. The development community, while
101 community is always in need of developers who will help to make the kernel
103 join our community.
121 learning how to work with the kernel community and get their code into the
[all …]
|
| H A D | 3.Early-stage.rst | 31 immediate problem. To the wider kernel community, though, it was seen as a
38 The audio community, however, could not see past the particular solution
55 - and to discuss it with the development community before investing in the
75 discussions with the community before launching into implementation. Early
95 Years of experience with the kernel development community have taught a
98 released into the community. Sometimes these problems are severe,
100 the kernel community's standards. Some examples include:
173 provide can help the development community provide useful input on the
189 community informed as you go.
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team.md | 16 1. A community member reports a problem privately to the security response team
23 4. The responders privately engage community members to create workarounds and
32 web page explains how OpenBMC community members can report a security
43 contain collected wisdom for the response team and community members who are
|
| H A D | how-to-report-a-security-vulnerability.md | 44 - Privately engage community members to understand and address the problem.
49 - Coordinate workarounds and fixes with you and the community.
62 - Join the OpenBMC community and fix the problem yourself.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/ttf-fonts/ |
| H A D | ttf-takao_003.03.01.bb | 3 SUMMARY = "Takao Fonts are a community developed derivatives of IPA Fonts."
4 DESCRIPTION = "Takao Fonts are a community developed derivatives of IPA Fonts."
|
| /openbmc/docs/process/ |
| H A D | subproject-maintainership.md | 45 OpenBMC community also maintains many integrated projects that are specific to
49 as board and platform design. The shape of the project's community reflects the
53 support enters the project. As a consequence the community tends to be dominated
56 capabilities. The motivation for contribution by those in the community tends to
63 A consequence of this latter point is that engagement in the community can vary
70 by the OpenBMC community.
100 introduce maintainers to subprojects to ensure the community can make forward
144 Further, the community of maintainers inside the project [isn't broad enough to
151 from community members without their consent is likely counter-productive,
183 build the community's trust in their decision making.
[all …]
|
| /openbmc/docs/tof/ |
| H A D | membership-and-voting.md | 67 Membership in the OpenBMC development community is determined by development
79 There are two tiers of membership in the development community: normal and
81 determining community and tier membership. The normal membership tier is
84 12.5% (1/8) and 20% (1/5) of the community. (Whenever the highly-productive tier
110 Determination of membership in the community is made by a point system for
|
| /openbmc/webui-vue/docs/guide/ |
| H A D | readme.md | 12 1. Act as a collection of community agreed-upon standards
37 community agreed-upon decisions on color, motion, and typography within the
|
| /openbmc/ipmitool/contrib/ |
| H A D | bmc-snmp-proxy.sysconf | 8 # SNMP community string and the OID of the Service Processor's SNMP agent.
21 # Description: Set community string of the Service Processor (BMC)'s
|